Here are challenges we ran into while moving from an On-Premise CRM 2015 and NAV 2015 systems to using Dynamics 365 and Business Central in the Cloud.


Solutions and Points to consider

Cannot access SQL directly with the Cloud systems. Use OData connection to D365 and BC.
OData for BC has to be externalized for automatic refreshes. Externalize OData for BC to avoid using a PBI Gateway.
Table structure has changed in BC. Learn new table structure in BC and adjust your reports accordingly.
Power BI does not use native D365 or BC Row-Level Security. If Row-Level Security is of concern, implement Security inside PBI.
For complex PBI Reports, DAX language is required. Learn DAX language for complex queries.
We had about 100 SQL Views developed, which we used in Excel BI Cubes. Those cannot be used anymore. Substitute SQL Views with OData queries or migrate database to SQL Azure.
We used to have several SQL-based SSRS Reports for CRM, they cannot be used in the Cloud. Change SQL queries to Fetch-XML for CRM reports but Fetch-XML has limited capabilities.
We used to update NAV Reports in Visual Studio. Get up to speed how to develop BC Reports in Visual Studio.
Labels for D365 picklists do not show in PBI Reports. Import a custom solution for D365 picklist options to show in PBI reports, or create a reference table in Excel.

Blog post by Emilia Arkadyev – Solutions Architect, Development Manager

Emilia has been with Vox ISM for over 11 years. Her current role with Vox ISM is focused on solution architecture, business intelligence, integrations and data management. With more than 25 years of experience and the successful completion of hundreds of projects, Emma has the ability to work effectively with your staff, listen to their ideas and help implement the changes necessary for successful completion of your project.