In this article, we will review the case when an error: Data source error "We cannot convert the value null to type Record." occurs on attempting to refresh data for Power BI reports for Planner and how to solve this issue:
Data source error: {"error":{"code":"ModelRefresh_ShortMessage_ProcessingError","pbi.error":{"code":"ModelRefresh_ShortMessage_ProcessingError","parameters":{},"details":[{"code":"Message","detail":{"type":1,"value":"We cannot convert the value null to type Record."}}],"exceptionCulprit":1}}} Table: CustomCalendar.If there is no required data in the EPM Pulse OData feeds (for example, Planner Plans), Power BI will fail to refresh data in reports.
When data synchronization is launched, the data from Planner is synchronized by EPM Pulse firts which is used as a middle-ware and if there are no tasks in the Planner Plan selected for synchronization, it will be recorded in the EPM Pulse log file.
Info 44b11bb3-3d56-4121-1e13-ae4f00e55ba3 Task Records count: 0
Also, to have more data for synchronization, please make sure that your synchronization account meets the following requirements:
- It should have access to all Planner Groups, all Planner Users, and be a member of all the Plans needed to be synchronized from Planner.
- If Extend Plans Sync option is not enabled, this account should open all plans that need to be synchronized.
For data synchronization to be completed successfully, please make sure that there are some tasks created in the selected Planner Plan:
- Create some tasks in the Planner Plan selected for synchronization.
- Add the sync account as a member to all the Plans which you would like to see in your Power BI reports.
- Check the checkbox 'Extend Plans Sync' in Data Management of your EPM Pulse tenan to avoid opening all the necessary Plans that need to be synchronized in Planner.
- Run an on-demand data synchronization in your EPM Pulse tenant.
- Once the data synchronization is completed in EPM Pulse, run an on-demand data refresh in Power BI Service.