cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
jickes Regular Visitor
Regular Visitor

Error: Value Encoding failure - Data ID range is too large.

Receiving this error when refreshing a dataset. The query worked just prior to this, but for a smaller amount of order history. I'm not sure what this error means? Any help translating would be appreciated!

 

4 REPLIES 4
jickes Regular Visitor
Regular Visitor

Error: Value Encoding failure - Data ID range is too large.

I'm receiving this error when trying to refresh a report. I'm not sure what it means?

 

Moderator v-qiuyu-msft
Moderator

Re: Error: Value Encoding failure - Data ID range is too large.

Hi @jickes,

 

In my opinion, the error indicates there is something wrong with the underlying data. In your scenario, which dataset did you use do connect to? Can you apply a filter to retrieve less data? If you have original .PBIX file, please refresh it in Power BI desktop to see if the same issue occurs. Also open Query Editor to check if any error displays.

 

Best Regards,
Qiuyun Yu

 

 

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
jickes Regular Visitor
Regular Visitor

Re: Error: Value Encoding failure - Data ID range is too large.

This is in PowerBI Desktop. The dataset is 4 SQL queries from seperate systems that get combined using Table.Combine() to make my source. The query successfully refreshes if I limit each query to less data, and the queries work if i run each 1 of the 4 seperately without limiting them. I can successfully refresh the query in preview mode with no limit on the queries and using all 4 with Table.Combine(), if I select "Keep Errors" no rows are returned. But when I click Close & Apply, the query runs for a while, then I receive the error. 

JohanvdBrink Frequent Visitor
Frequent Visitor

Re: Error: Value Encoding failure - Data ID range is too large.

Hi @jickes did you resolve the issue?

And @v-qiuyu-msft you didn't reply anymore when Jickes explained a bit more about his issue.

 

Johan