In an effort to conquer and banish those dreaded RDLC Brain Cramp (a.k.a. RBC) pains in my head from working with Microsoft Dynamics NAV 2013 RDLC reports, I have first decided not to beat my head against the wall when I can’t resolve the report issue. That has helped. Secondly, I have found solutions to… Continue reading Microsoft Dynamics NAV 2013 RDLC Reporting RBC Attacks: Part 2 of 10
Category: Developer
Microsoft Dynamics NAV 2013 RDLC Reporting RBC Attacks: Part 1 of 10
Ask any NAV developer and they can tell you exactly what an RDLC brain cramp feels like. It is a pain behind the eyes that causes you to want to stare into space for hours, and bite the heads off innocent gummy bears. This intense pain is preceded by hours wasted searching one forum after… Continue reading Microsoft Dynamics NAV 2013 RDLC Reporting RBC Attacks: Part 1 of 10
Avoiding Hard Coding and Creating Setup Reports for Projects
Part 1: I try not to hard-code things The other day, I was writing an import for a customer where they needed to take a file from their payroll processor, pull it into their system, and consolidate data from different fields in the file by department into a multitude of G/L accounts in a General… Continue reading Avoiding Hard Coding and Creating Setup Reports for Projects
Spicing Up Your NAV 2013 Pages
Editor’s note: The following blog was originally posted on January 3, 2014. Two of the graphics were incorrect. The blog is being reposted with the correct graphics. We apologize for any inconvenience. If you have any questions, please contact ArcherPoint at emartin@archerpoint.com. I recently had to make a lot of chili. I mean, I made… Continue reading Spicing Up Your NAV 2013 Pages
Beware the Third Parameter of MODIFYALL
The C/AL keyword MODIFYALL is tempting to use when a certain value must be changed for every record matching the current filtered recordset. One may or may not be aware of the third optional parameter for this keyword: TRUE/FALSE. FALSE is the default. If set to TRUE, the OnModify() trigger is executed when the record… Continue reading Beware the Third Parameter of MODIFYALL
TableData 2000000001 does not exist.
This NAV 2013 error may result if the user is attempting to connect to a NAV database using the Developer Client and the SQL permission dbowner has not been granted for the user at the database level. This resource reports the SQL permission dbowner is required in order for a user to manage NAV… Continue reading TableData 2000000001 does not exist.
NAV Web Services – Pages vs. XMLports
There are two major methods for publishing complex NAV functionality as a web service: publishing a Page object, and publishing a Codeunit object with a function that uses an XMLport as a parameter. Which one should you use? Like Obi-Wan Kenobi and Captain America here, Pages and XMLports are both awesome, but they should be… Continue reading NAV Web Services – Pages vs. XMLports