Small and medium business | Business Central, N...

Unable to unable to run report

(0) Share

Report

Posted on by Bryma

Hello everyone,

I am currently unable to run a report after building it from the AL environment. The report is 7321 - Inventory Movement (RDLC). The reason for building the report was to add Document No field which wasn't in the source code. The report was published successfully, and I could run it on the built ID: 50102. However, when I import this into the custom base application for 7321 (not the built-in), I get a textbox error message for the modified field.

Find below attached screenshot for error message.

Thank you so much

Bryma

Screenshot_5F00_20230404_2D00_111409_5F00_Microsoft-365-_2800_Office_2900_.jpg

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Hasnain Ali 134 on at

Like (0)

Report

Hi,

column "DocumentNoFieldCaption" may be removed or renamed from/in the dataset.

Try creating this column in the dataset and run the report again.

Was this reply helpful? Yes No
Suggested answer

Bryma 4 on at

Like (0)

Report

I was able to write a code using Code unit to substitute the base application report with the built one so that the system recognizes the built report.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,307 Super User 2025 Season 2 on at

Like (0)

Report

Hi, If you're just adding a field, I don't see the need to create a new report, you can do it with the Report Extension. The reason for this error should be that you did not add this field in the 7321 report.

More details: https://yzhums.com/10723/

Hope this helps.

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Shathika Karunaratne on at

Like (0)

Report

First of all, you do not need to create a new report for this. instead, you can create a report extension where you will be able to extend a standard report and you can add your document no field there.

In here the error is coming because "DocumentNoFieldCaption" field is not in the dataset. you might create it as a Label or text constant. But you need to put it under the main data item set. then you will be able to overcome from this aforementioned error

Was this reply helpful? Yes No