Skip to content

ArcherPoint Microsoft Dynamics NAV Developer Digest - vol 6

The ArcherPoint technical staff—made up of developers, project managers, and consultants – is constantly communicating internally, with the goal of sharing helpful information with one another.

ArcherPoint’s technical staff pose questions, find answers, and share new discorveries about Microsoft Dynamics NAVAs they run into issues and questions, find the answers, and make new discoveries, they post them companywide on Yammer for everyone’s 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 group—so we thought, wouldn’t it be great to share them with the rest of the Microsoft Dynamics NAV Community? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from the ArcherPoint staff. We hope these insights will benefit you, too.

Jon Long on Import Tables FOB's result in compile errors:

This has popped up a few times in 2013R2 Rollup7 when importing a FOB containing several tables, where some are new objects and some are modified base NAV: It will not import due to compile errors involving missing objects. At least, that's what the error says. The object is actually in the import, but, when a preceding object has a dependency on a later object, then it crashes with the error. This behavior is new to 2013R2.

I opened a ticket with Microsoft and will report back here with their answer.

By the way, the workaround is to import in chunks. But, this is tedious, time consuming, and may still not work. For instance, I had two tables that each depended on each other. I was not able to import. So, I'm hoping for a solution from Microsoft.

Dan Sass added:

The work around is to open the database with rollup 5 and that does the trick. We then should be able to open the database with the latest rollup after the merge is done.

Jon Long followed up with:

Microsoft replied with the same workaround, i.e., import using the platform that was used to export (although, in some cases, it will work with certain builds). Then, convert the database using the platform of your choice (Rollup 7 for instance).

I've noticed it with Rollup 5, 6 and 7. Microsoft says that they can't guarantee FOB compatibility between builds. To quote, "The compiler rules have tightened up in Microsoft Dynamics NAV 2013 R2 so we have seen some newer issues like this when dealing with older objects."

Also, keep in mind that it's only a random issue with only certain objects. For instance, for one ISV’s product, I followed Microsoft's proposed workaround of importing in chunks, and ended up with only three objects that had dependencies. Once I figured the order to import those 3, I was able to import them as well.

Alan Campbell shared this blog about one person’s experience in taking the Project Management Institute - Professional in Business Analysis (PMI-PBA) certification exam:

I Took the PMI-PBA Exam!

Blog Tags: 
Read ArcherPoint's Blog Follow us on Twitter Follow us on Facebook Follow us on LinkedIn Link to our RSS feed Join us on Google+ Watch us on YouTube