ArcherPoint Dynamics NAV Developer Digest – vol 58

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.

As 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.

Crystal Hill on accessing various companies in a NAV 2013 Development Environment:

Yesterday I was asked to find out why a user could not access other companies in a NAV 2013 Development environment. In most cases, if you open the RTC environment and then try to open the table from the development environment, your table will open in the company you are running in RTC. In some cases, however, this is not happening and the company defaults to the same company every time, opening in a new window.

Here is the fix:
Go to Tools-Options in the development environment under the user login having this problem, then Delete the company name from the Company Name Field.

Michael Heydasch on “Transaction does not exist” error:

If you get this error: "Transaction does not exist", then delete the so-called "zombie" records according to filters:

"STO Trans ID".RESET;
"STO Trans ID".SETFILTER("STO Document Source", '=%1', 0);
"STO Trans ID".SETFILTER("STO Document Type", '=%1', 0);
"STO Trans ID".SETFILTER("STO Document No.", '=%1', '');
"STO Trans ID".SETFILTER("STO Entity", '=%1', entity);
"STO Trans ID".SETFILTER("STO Division", '=%1', division);
"STO Trans ID".SETFILTER("STO Is Positive", '=%1', positive);

The above code is found in Codeunit 14083209. This error typically occurs when a NAV Production database is restored to a NAV Test database, and the STO database does not accompany this effort. Basically, the transaction IDs are out-of-sync.

Dara Daly shared an article on Controlling Search Engine Crawlers for better indexing:

Deciding when (and how) you should disallow a page from be indexed by search engines can be confusing! Should you exclude the page using robots.txt? Or use meta robots tags in a page header? Or perhaps you should use nofollow in links. In this video, Rand Fishkin of Moz.com walks through the various scenarios and when to apply the appropriate strategy.

View the video: Controlling Search Engine Crawlers for Better Indexation and Rankings

If you are interested in NAV development, check out our collection of NAV Development Blogs.

For step-by-step instructions on how to perform specific tasks in Microsoft Dynamics NAV, see our collection of How-To blogs.

If you found this post useful, you might also be interested to read through our archive of the Dynamics NAV Developer Digest.