Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.7K 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
- 317 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 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.6K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Compiling RDL Layout with Visual Studio Code
Lilithyan
Member Posts: 32
Hello,
mayhap I'm overlooking the obvious, but then so are all of my colleagues. I've developed an new report for a customer in Visual Studio Code with an rdl layout. In the old development enviroment you could compile the report (what is now the AL part) and it would also compile you the layout an tell you if (for example) a hidden expression didn't work. With Business Central (especially if it is Clous-based) the only way I have found to do this is to actually upload the Extension into a sandbox and try to print the report. Or rather, use "Send E-Mail" as only then I am acutally given the error message as before and not just "Report could not be printed due to Layout-Error".
Does anyone know a better way to find out if something is wrong in your layout?
Ciao,
Lils
mayhap I'm overlooking the obvious, but then so are all of my colleagues. I've developed an new report for a customer in Visual Studio Code with an rdl layout. In the old development enviroment you could compile the report (what is now the AL part) and it would also compile you the layout an tell you if (for example) a hidden expression didn't work. With Business Central (especially if it is Clous-based) the only way I have found to do this is to actually upload the Extension into a sandbox and try to print the report. Or rather, use "Send E-Mail" as only then I am acutally given the error message as before and not just "Report could not be printed due to Layout-Error".
Does anyone know a better way to find out if something is wrong in your layout?
Ciao,
Lils
0
Answers
Unfortunately I have not found a solution to this, currently I am using a codeunit to say report.run(xxxxx,rec) and run it as a startup run F5 is used.
It does not fixe the issue by it speeds up my proces