ArcherPoint Dynamics NAV Developer Digest - vol 135
The NAV community, including the ArcherPoint technical staff, is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of sharing helpful information with one another to help customers be more successful.
As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media...so everyone can benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share this great information with everyone who might not have the time to check out the multitude of resources out there? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV experts and devotees around the world. We hope these insights will benefit you, too.
A Crazy Uncommon Dynamics NAV Error
Tom Hunt reports, “I ran into a crazy NAV 2017 error today that needs to be broadcast. I was calling COUNT on a record variable, and I got an error message saying, ‘The [table name] already exists. Identification fields and values: [primary key fields].’ (Specific table names are unimportant, as this could happen with any table.) Matt Traxinger explained to me that this was happening because I had an INSERT operation try to insert a record that already existed, but I didn't get the error on the INSERT because the INSERT didn't get sent to SQL until I tried to do a COUNT on the same table and the NAV server had to go talk to SQL. The moral of the story is to keep in mind that in NAV 2017, the NAV server waits to do SQL operations until absolutely necessary, so keep that in mind while you're coding. (Thanks, Matt!)”
Matt replied, “Slight correction, this has been around for a long time. I want to say since 5.0, but maybe 2009. It just isn't something that you run into all that often.”
Another Interesting Dynamics NAV Error
Gwen Cain shares her experience with the error “Page # contains several Actions with the same ID - #. Redesign the page to remove duplicate Action IDs.” This error was thrown from page 254 when the user clicked the Post action. The error did not occur when the user’s User Personalization Profile ID was blank, but when she was assigned a User Personalization Profile ID. The error occurred on the Post action. When Gwen checked page 254, duplicate Action IDs did not exist. She did some searching and found a solution on the Microsoft Dynamics NAV Users forum that helped resolve the issue. She had to delete the offending record in the User Metadata table to remedy this issue. She’s not sure why the record was created in the first place, but now you know how to fix it should you run into this error.
Power BI Latest Improvements
Jason Taylor shares the latest update to Power BI, noting that the new matrix is pretty cool, as is the report theming.
I also recommend that you check out the custom visuals for Power BI in the Microsoft Office store.
Here’s some things to think about:
HBR’s article, Pressure Doesn’t Have to Turn into Stress and Fast Company’s Beyond the 80/20 Rule: This Formula May Make You Rethink Time Management.
Stay abreast of what is new in the Microsoft Dynamics NAV community and at ArcherPoint by subscribing to our monthly newsletter, Better Business, by completing the form in our Resource Center.
And, if you are interested in NAV development, be sure to see our collection of NAV Development Blogs.