Issue with Getting data from Dynamic 365 Dataverse

[SeethalakshmiG]

Data source is CRM
I am importing  contact & account entities from dynamic 365 dataverse to Power BI using import mode . However,i am encourting an error "type of the current preview value is too complex to display."Table is loading but appears to be a navigation issue.
Eventhough no of columns are high ,no of rows are very minimal (approximately 29 rows)
attached screenshot ,please someone help me on this quickly how to fix it.
Moreover, i am facing this issue for the last 3 days only .I was able to connect it 

[v-pnaroju-msft]

Thankyou, @Nasif_Azam, for your response.

Hi SeethalakshmiG,

We sincerely appreciate your inquiry posted on the Microsoft Fabric Community Forum.

Based on my understanding, the error message, “The type of the current preview value is too complex to display,” arises due to complex column types in Dataverse tables—such as lookup fields, polymorphic relationships, or multi-option sets—which Power Query is unable to render in the preview pane. This is especially common if there have been recent schema changes in your environment. Although the number of rows may be small, a large number of columns or newly introduced complex fields can produce this issue. Please note that this error affects only the preview; in most cases, the data still loads correctly.

Kindly follow the steps mentioned below, which may help resolve the issue:

1. Use OData Query with $select to load only specific columns, thereby bypassing problematic columns through OData filtering. You can use Get Data > OData Feed in Power BI to load only the required columns while avoiding the expansion of navigation tables. For example:
   https://<org>.crm.dynamics.com/api/data/v9.2/contacts?$select=fullname,emailaddress1,telephone1

2. If you are using the Dataverse connector and have reached the Navigation pane, click the gear icon next to the Navigation step. Deselect lookup or system fields such as _ownerid_value, _createdby_value.

3. Verify recent schema changes with your CRM administrator to check whether any new fields have been added in the past few days or if any field type has been changed to lookup, composite, or multi-option set. Such recent changes can unexpectedly cause the preview to break.

4. If the issue persists specifically with the Dataverse connector, try using the OData Feed instead. This will help isolate the problem and give you more control over the columns being loaded.

Additionally, please refer to the following link for further guidance:
Use OData to query data - Power Apps | Microsoft Learn

If you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will assist other community members who may face similar issues. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.

[Nasif_Azam]

Hey @SeethalakshmiG ,

The issue you're facing while importing data from Dynamics 365 Dataverse into Power BI. I understand that you're encountering an error message: "The type of the current preview value is too complex to display." Based on your description and the attached screenshot, it seems like the issue could be related to navigation properties or complex data types in your Dataverse tables. Few steps I recommend trying to resolve the issue:

1. Check for Navigation Properties:
   Ensure there are no navigation properties (e.g., lookup fields) that might be causing the error. You can try expanding these fields in Power Query to pull in the related data.

2. Switch to DirectQuery Mode:
   If the data size or complexity is causing issues in Import mode, try switching to DirectQuery mode, which sends queries directly to Dataverse rather than importing the data into Power BI.

3. Limit the Number of Columns/Rows:
   Although the number of rows is minimal, sometimes the number of columns can still cause problems. Try importing a subset of columns or filtering the data before importing it into Power BI.

4. Clear Cache and Refresh Data:
   Sometimes, Power BI's cache can cause issues. You can try clearing the cache and refreshing the data by going to Options > Data Load > Clear Cache.

5. Check for Unusual Data Types in Dataverse:
   Inspect the columns for any unusual data types (such as multi-value fields or complex custom columns). If any are found, either remove or transform them before importing.

For Detailed Information:

Check for Navigation Properties in Power BI

Switching to DirectQuery Mode in Power BI

Limit the Number of Columns or Rows in Power BI

Clear Cache and Refresh Data in Power BI

Check for Unusual Data Types in Dataverse

If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.

Best Regards,
Nasif Azam