Project for the Web to Power App

[Anils1603]

Fellow Users, I just joined the community and am quite amazed by the level of collaboration and information sharing in this space. Thanks very much for your contributions. I have a use case to help in building a process whereby people can enter time easily into an allocated task from Project for the web Project. I am trying to get my head around how all these fits into the picture. Ideally I need to be able to create the project and allocate the task (PMO, PMs) to a resource, who gets it to their Outlook/Microsoft To Do. I need to be able to build a Power App connecting to this Project for the Web project and enter (or Start/Stop Timer) time worked on one of the tasks allocated with, which then rolls back up and updates the Effort Completed field of the Project. When I try to connect to the Project Tasks from the Power App, it comes up with the error message that I need license for Project Service Automation. What I need is a bit of direction to get my head around the Licensing - either what am I missing in this picture.

[v-siky-msft · Accepted solution]

Hi @Anils1603 ,

You have to purchase Project Service Automation or Dynamics 365 Customer Engagement plan or Dynamics 365 plan License.

Project Task entity is the restricted entity tied to the functionality of Dynamics 365 applications that require app users to have the corresponding license for that application if they want to create, update, or delete records within the entities, so Dynamics 365 for Project Service Automation or Dynamics 365 Customer Engagement plan or Dynamics 365 plan License is required.

Reference: Restricted entities requiring Dynamics 365 licenses 

For more information on License: Licensing overview for Power Platform 

Hope this helps.

Sik

[Anils1603]

Thanks very much Sik for answering my query with such short turn around.

The only other thing that comes to my mind is how it impacts all the users who consume the App. If they only need the Single or Multiple user licensing for the Power App platform, then it is fine. If it needs the users to also have the Project Service Automation or any of the Dynamics 365 licenses (we might get to some of these licensing like Office 365 and specific Dynamics 365 potentially) then I am fine.

[v-siky-msft]

Hi @Anils1603 ,

Yes, it also impacts the users who consume the app.

Apps and flows that use these entities require the app and flow user to be licensed appropriately-not the maker or developer of the app or flow. Reference: https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/data-platform-entity-licenses 

Please check the example, you are facing the case of App2.

Sik

[joshbooker]

The documentation is out of date at this point.   Its my understanding licensed users of Project Online (P1-5), get the Project PowerApp and Universal Resource Scheduling App installed as a part of the new-ish 'Project for the Web' (P4W) service.  These apps provision the msdyn_ProjectTask and related entities in the dataverse environment and no addition Dyn365 Project Operations FS, CS, etc license is required.  That said, I would like more details on the limitations in URS included in the P4W offering compared to D365PO.  Specifically:

https://powerusers.microsoft.com/t5/Power-Platform-and-Dynamics-365/Universal-Resource-Scheduling-in...

HTH,

Josh