Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Validating RDL for extension report in Business Central?
borealis
Member Posts: 35
I am doing a report in BC CU4 on-prem and have generated the extension object and the RDL file for that object, but I'm getting issues rendering the report which I believe is due to an error in my RDL. In the 2018 and prior versions the compiler would nicely flag any RDL errors, however I have noticed that the BC compiler seems to take it as a given that the RDL is correct.
I know for a fact that my original version of the RDL did have errors that were not reported but which I subsequently found, but I've been over the RDL again a few times and haven't been able to spot any further issues that jump out at me.
The precise error when the report is printed is "An error occurred while trying to display the report." in the preview window.
My question is whether there is some other method of validating the RDL? I am using the SQL Server 2016 Report Builder to generate the RDL, and doing limited verification using notepad++ to try to spot issues in the 4840 line RDL file. Somebody somewhere has to have built a tool for this haven't they? Worth noting this is my first attempt to build a non-processing report via extension, so it's possible I'm doing something fundamentally wrong.
I know for a fact that my original version of the RDL did have errors that were not reported but which I subsequently found, but I've been over the RDL again a few times and haven't been able to spot any further issues that jump out at me.
The precise error when the report is printed is "An error occurred while trying to display the report." in the preview window.
My question is whether there is some other method of validating the RDL? I am using the SQL Server 2016 Report Builder to generate the RDL, and doing limited verification using notepad++ to try to spot issues in the 4840 line RDL file. Somebody somewhere has to have built a tool for this haven't they? Worth noting this is my first attempt to build a non-processing report via extension, so it's possible I'm doing something fundamentally wrong.
0
Best Answers
-
Optionsborealis
Member Posts: 35
FYI, for anybody else searching for this, it doesn't seem like there are currently built in tools to validate the RDL. My recommendation if you do get this error is to make a backup copy of your RDL file, and then delete elements of your layout until the report works. That way you'll at least have a general idea of what area your problem lies in, and can selectively delete elements until you find the control that has the issue.
It's a crap way to validate RDL but it works, albeit a lot slower than having a compiler tell you exactly where it is.0 -
Options
ShaiHulud
Member Posts: 228
Visual Studio 2017 (don't know about other versions at the moment) has such a feature: select Build->Build Solution.
Errors, if any, will be shown at the bottom (on default layout), on the Output window:
5
Answers
It's a crap way to validate RDL but it works, albeit a lot slower than having a compiler tell you exactly where it is.
Errors, if any, will be shown at the bottom (on default layout), on the Output window: