none
In Project Server 2016 / PWA, are "Enterprise" things truly enterprise, or are they site collection scoped? RRS feed

  • Question

  • In the environment that I am working on, our server is set up so that the Project Web App I have to mess around in and test things in is at the URL:

    https://servername/pwa/my-pwa

    where the "/pwa/" is essentially a managed path, similar to SharePoint "/sites/", and the "/my-pwa" is similar to the root of a SharePoint Site Collection.

    I am experienced with SharePoint, and based on my knowledge of how SharePoint Site Collections work, I am assuming that any projects uploaded and/or published to

    https://servername/pwa/my-pwa

    will not be visible in another site collection (Project Web App?) at

    https://servername/pwa/another-pwa

    Is that assumption correct?  And what about "Enterprise" calendars and custom fields?  Are they truly "Enterprise" in the sense that any enterprise calendars would be visible to all site collections?  Or are they more site collection scoped, and an enterprise calendar in

    https://servername/pwa/my-pwa

    would not be visible in

    https://servername/pwa/another-pwa

    ??

    Wednesday, September 27, 2017 8:12 PM

Answers

  • Hi Dylan,

    Indeed, any enterprise objects (calendar, custom field, resource, project, PDP...) created in a PWA instance are instance related and not site collection. You could have N PWAs (site collections) such as test, demo, training, QA, production, any objects are specific to one unique instance and not visible in the other instances.

    Note that some tools exist to duplicate (save and backup) enterprise objects from 1 PWA to another.


    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller

    • Marked as answer by DylanCristy Wednesday, September 27, 2017 10:17 PM
    Wednesday, September 27, 2017 9:33 PM
    Moderator