Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Vanchy_Liao
Advocate II
Advocate II

Preview.Error: The current preview value is too complex to display when using WebAPI

Hi,

    I am trying to use Web API to deliver Data to end user.

 

    My Developing environment is:

    1. windows server 2019: to develop Power BI

    2. windows server 2019: to develop Web API 2 and hosting IIS

    3. Using Power BI Desktop RS

 

    I create a DB view and use a Web API returning the data in JSON format

    The view contains 20 columns and returns about 32,000 rows.

   

    When I put the url on Edge and IE, it works differently. (The JSON file is 14.42 MB)

    1. Edge takes approximately 1.3 minutes.

    2. IE takes in 3 sceonds.

    

    And when I use "Web" connector in Power BI, it will take a long long time and show the error "Preview.Error: The current preview value is too complex to display".

 

    Is there any server settings I can change?

    Or I just have to change  my view into many small parts?

    Or it just Power BI issue?

    

 

1 ACCEPTED SOLUTION
Vanchy_Liao
Advocate II
Advocate II

I overcome this issue myself.

 

First, the difference between Edge and IE might caused by the browser security settings I guess.

 

Second, the bottleneck is not on the Web Connector and it's on the JSON Connector.

Because I save the JSON as file and import it into Power BI using JSON Connector, then it shows me the same message:

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

 

Finally I edit my Web API making it return in XML format.

My report just come alive again!!!!

I sacrifice the file size and choose XML Connector.

View solution in original post

2 REPLIES 2
Vanchy_Liao
Advocate II
Advocate II

I overcome this issue myself.

 

First, the difference between Edge and IE might caused by the browser security settings I guess.

 

Second, the bottleneck is not on the Web Connector and it's on the JSON Connector.

Because I save the JSON as file and import it into Power BI using JSON Connector, then it shows me the same message:

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

 

Finally I edit my Web API making it return in XML format.

My report just come alive again!!!!

I sacrifice the file size and choose XML Connector.

Adel
Helper III
Helper III

Hey, it might be a Power bi issue, if you don't mind me asking this data you are trying to pull is from which platform? 

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.