Virtual Entities Data Events for Dynamics 365 FO with Power Platform - By Rakesh Darge

Powered By D365 Champs

[@aamirahmed8362]

I have configured virtual entity for fno for viewing salesorder in ce but is it possible that ce user can able to see fno data without having fno license ???

[@Mahmoudalgindy]

Yes, using virtual entities in Dynamics 365 Customer Engagement (CE) to view data from Dynamics 365 Finance and Operations (FNO) is possible without requiring CE users to have an FNO license. Virtual entities provide a way to integrate and display data in real-time from external systems, like FNO, directly in CE without storing the data in CE's database. This setup allows CE users to view FNO data through the configured virtual entities, but there are important considerations: 1. **Licensing**: While CE users can view FNO data via virtual entities without an FNO license, they cannot interact with the FNO system directly or use any FNO-specific functionality. It's critical to ensure that this setup complies with Microsoft's licensing policies, as they can sometimes change or have specific stipulations. 2. **Permissions and Security**: You'll need to manage permissions carefully to ensure that data visibility through virtual entities is controlled and conforms to your organization's security policies. 3. **Performance**: Since virtual entities fetch data in real-time from FNO, there might be implications on performance, particularly if large volumes of data are accessed frequently. It’s important to monitor and optimize the performance to ensure a smooth user experience. 4. **Functionality Limitations**: Virtual entities are primarily for viewing data. If users need to perform actions on the data, such as creating or updating records, additional integration methods like custom APIs or data synchronization might be necessary. This setup allows organizations to leverage their existing CE environment to provide enhanced visibility into FNO data, enhancing user productivity without the need for additional FNO licenses. However, always verify current licensing requirements and technical capabilities with Microsoft or a licensed Microsoft partner to ensure compliance and feasibility.