Preview.Error : The type of current preview value is too complex to display

[vkartik]

Hi,

I tried connecting to Dataverse system user table and "Preview.Error : The type of current preview value is too complex to display" is getting displayed.

I noticed that about 200 rows gets loaded and after that this message is displayed.

This issue is happening in new environment to which system user table I am trying to connect but the same is working for old environment.

Kindly let me know what can be the cause of this issue and possible fix for this.

Thanks

[mlacatus]

Hi! 

I just encountered the same issue, with the same systemuser table. 

What worked in my case, was to add a "Removed other columns" step manually. I was interested in just two columns so I knew what I needed. Preview worked fine after adding this step. 

Also, in my case data load worked even if preview threw an error. So I was able to see the columns and to see what columns I need and what can be removed.

Best regards

[C_Jorgensen]

Hi! I've gotten this error message myself from time to time and never understood why - sometimes it happened when loading just a small dimension table from dataverse of maybe <100 rows and 50 columns. Didn't seem too complex to display.

Today I made it work for me though, I unchecked the box to include relationships columns
  

Hope that helps you as well.

[v-yalanwu-msft]

Hi, @vkartik ;

Firstly, for the limitations, please refer: https://docs.microsoft.com/en-us/power-bi/service-get-data#considerations-and-limitations.

For all data sources used in the Power BI service, consider the following limitations. There are other limitations that apply to specific features, but the following list applies to the full Power BI service:

• Dataset size limit - There's a 1-GB limit for datasets stored in Shared capacities in the Power BI service. If you need larger datasets, you can use Power BI Premium.

• Distinct values in a column - When caching data in a Power BI dataset (sometimes called 'Import' mode), there is a 1,999,999,997 limit on the number of distinct values that can be stored in a column.

• Row limit - When using DirectQuery, Power BI imposes a limit on the query results that are sent to your underlying data source. If the query sent to the data source returns more than one million rows, you see an error and the query fails. Your underlying data can still contain more than one million rows. You're unlikely to run into this limit as most reports aggregate the data into smaller sets of results.

• Column limit - The maximum number of columns allowed in a dataset, across all tables in the dataset, is 16,000 columns. This limit applies to the Power BI service and to datasets used in Power BI Desktop. Power BI tracks the number of columns and tables in the dataset in this way, which means the maximum number of columns is 16,000 minus one for each table in the dataset.

Here is a similar thread for your reference. Please check if the suggestion mentioned in it work for your scenario.

Best Regards,
Community Support Team _ Yalan Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[vkartik]

Hi,

I explored more on this and I believe this can be data issue in Systemuser Table.

Also , the following error  is displayed to me when I tried to "Close and Apply"

"Column territoryidname in systemusertable contains blank values and this is not allowed for columns on the one side of many-to-one relationship or for columns that are used as primary key of table".

Kindly let me know what can cause this blank value and why I am getting this on one environment and not others.

Thanks

[vkartik]

Hi,

Thanks for the information.

I don't think any of the above mentioned limitation can be the cause of this issue.

As I checked systemuser table have 132 columns and near by 2000 records.

One thing which I noticed is , I have 3 environments , I am able to connect to systemuser table for 2 environments (****.crm4.dynamics.com) and unable to connect to 1 environment (***.crm3.dynamics.com).

Can this be the access or permission issue with ****.crm3.dynamics.com ?

Do we have any information on this.

Also , I am using PowerBI trial version and DirectQuery for connecting to dynamics.

One more information , this Power BI dashboard is a part of model app which I recetly moved from environment (****.crm4.dynamics.com) to environment (***.crm3.dynamics.com) using Azure Devops pipeline.

Regards

Kartik

[Madhatter]

Did you ever resolve this as I am getting the same error.

Thanks