Hello Chris R Tilley,
I would recommend to evaluate which Microsoft Dynamics 365 Project Operations deployment type is really needed before the implementation starts. A switch of the deployment type during an implementation is from Solution Design sight not really sensible. The deployment type has several impacts on e.g. licensing and cost, administration, technical behaviors and functional processes of the application.
I will give you a choice of differences up from the application-by-design below:
Administrative Differences: Microsoft Dynamics 365 Project Operations -Lite Deployment is from administrative site only Power Platform deployed. Microsoft Dynamics 365 Project Operations -Resource/Non-Stocked based Scenario Deployment is from administrative sight this time Power Platform deployed and Lifecycle Services deployed as it is integrated with Microsoft Dynamics 365 Finance and Operations Apps (be informed, that Microsoft has started to move the Dynamics 365 Finance and Operations Apps into the Power Platform, too - in my opinion it's only a question of time when the Dynamics 365 Finance and Operations Apps are even Power Platform based only). This differences will mainly have impact into the licensing process such as the Build Operations.
Technical Differences: As described above, within the Microsoft Dynamics 365 Project Operations -Lite Deployment a Power Platform only-based application is used. For the Build Operations counts, that this kind of Dynamics 365 applications are model-driven based and at first glance structured as Low-code-No-Code applications. The development is done via the (new) Microsoft Power Apps Designer, but can be extended. Within the Microsoft Dynamics 365 Project Operations -Resource/Non-Stocked based Scenario Deployment it's the same as explained above with the addition of a Microsoft Dynamics 365 Finance and Operations apps deployment via Lifecycle Services and all related components whereas the development is done via Visual Studio and X++ by default, but what is even expandable.
Functional Differences: Functional differences occur when using the by-design-processes. The Lite-Deployment is used for Project Sales and Project Management functions and the work is done via the Power Platform based User Interface. The Resource/Non-Stocked based Scenario Deployment contains Project Sales, Project Management and Accounting functions and the work is done via the Power Platform based User Interface and the Lifecycle Services deployed User Interface of the Finance and Operations Apps. For data exchange in general counts by default a leading Dynamics 365 Finance and Operations App.
Within the lite-deployed solution you will have Power Platform based Entities/Tables available within this specific license. Additional Microsoft Dynamics 365 Apps can be installed, too.
Within the Resource/Non-Stocked based Scenario deployed solution you will have Power Platform based and Lifecycle Services based Entities/Tables available within the specific license. The data integration is handled by Dual Write. Additional Microsoft Dynamics 365 Apps can be installed, too.
In general counts, that Entities/Tables will be added into an environment automatically, when a new license is added and/or when a new application is installed. If you e.g. upgrade a license you will not lose any data and just get additions and old objects will stay in the environment. If you downgrade a license you will lose access to the related objects.
Rg,
Alexander
*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)
*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.
References:
- Microsoft Licensing Guide
- Microsoft Doc`s/Learn
Share
Report
339
All responses (
Answers (
