Number of calculated fields in query exceeded maximum limit of 10

(0) Share

Report

Posted on by RV1

Hi,

We have build a number of reports in PowerBi using D365 tables. The link was working fine for last many months, Suddenly, in the last 2 weeks, we have started getting the following error.

OData: Request failed: The remote server returned an error: (400) Bad Request. (Number of calculated fields in query exceeded maximum limit of 10.)

The D365 tables have more than 10 calculated fields each. In PowerBi, we first load the table and then select relevant columns. However, the error is getting generated in step 1 itself. We tried to create a fresh file with a single table upload, but the problem persists.

The issue is that the reporting model was working perfectly until now. The only change has been that we are using a gateway to schedule data refresh.

What could have caused this issue and how can we resolve this? We are unable to refresh our data because of this problem.

Any insight would be helpful. Thanks

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Adrian Begovich 1,027 Moderator on at

Like (1)

Report

Hi RV1,

Saved queries, charts, and visualisations can have a maximum of 10 unique calculated fields. This is a limitation of calculated fields. The only solution is to use less than 10 unique calculated fields in your queries, charts, and visualisations.

Was this reply helpful? Yes No
RV1 on at

Like (0)

Report

Hello Adrian,

Thanks for the response. We are reading the tables directly into Power Bi (without fetch XML). The solution was working until now. Is this a new restriction? If yes, then it is not a practical one.

Alternatively, please suggest how we can work around this. We had tried to use Advanced Find to limit the number of columns to those relevant. Then we used Fetch XML to load the data into Power Bi. Unfortunately, Fetch XML has a limitation of 5000 records. Our tables are much larger. We don't really need more than 10 calculated fields in our queries.

Please also note, that along with this problem, our second level lookups also stopped working. Let me confirm that they were all working fine until mid-Jan.

Regards

RV1

Was this reply helpful? Yes No
Barbara Forsman 608 on at

Like (0)

Report

Were you able to find a solution for this, or is this a limitation on the Gateway? I'm trying to set up a Gateway but I get this same error and I'm wondering if there is any way around it or if I just have to refresh manually every day.

Was this reply helpful? Yes No