topic power Bi Subscription Error : There is no data for the field at position x in Report Server

power Bi Subscription Error : There is no data for the field at position x

Msaeed90 — Tue, 08 Feb 2022 12:00:34 GMT

we have run a power bi subscription to generate Visualisations report in pdf format we have get many errors like this There is no data for the field at position x

the problem is we searched many times about it we found that it may occured due to missing data in dataset

but we have about 30 datasets with a query to oracle database we cannot figure out which is the missing data and eent he log does not mention which report get the error

Is there a way to figure out which field is missing?

Is there a way to enrich the reports error log to give us which report failed?

the exact error is :

processing!ReportServer_0-8!1e18!02/07/2022-09:56:36:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 29.;

Re: power Bi Subscription Error : There is no data for the field at position x

Anonymous — Fri, 11 Feb 2022 09:13:37 GMT

Hi Msaeed90 ,

This error message is usually caused by a missing field in the dataset (it is defined in the dataset, but the query does not return it). It is OK if you don't use the field in your report. But if you do, then you'd get a "#error" in the textbox, or the report fails if it's used in a group/sort/filter expression.

I have found two articles I hope they are helpful in solving your problem：

All You Need To Know About Different Types Of Missing Data Values And How To Handle It

How to Deal with Missing Values in Your Dataset

Hope it helps,

Community Support Team _ Caitlyn

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

Re: power Bi Subscription Error : There is no data for the field at position x

Msaeed90 — Mon, 14 Feb 2022 09:08:43 GMT

Dear v-caitlyn-mst,thanks for your replay the links are helpfull

however,Dears

I found a solution help me. I will share it.

The error is due to missing data, not missing values, which means the column name defined in the data set field has been changed in the database.

note:

When make the value equals null it will not give the same error; even if it is used in the report it will give a different error.

about how to detect ?

Simply install report builder in machine has connection to this database and open this report with report builder and make verify fields, it will give detailed error with the name of dataset fields not found so we tracked it in database we found it has been changed so fix it in either dataset or column name in database it fix the issue.

New challenge we are going to handle it either column name exist or changed to e, never get error and give empty report better as there is some database the report will connect may not have the same column names so it should give empty part of report instead of error.

thanks BR,