When dealing with Number Series where the Intercompany Documents are created automatically using the code, using standard number series generation Codeunits cause problems. In this blog, I’ll be explaining why this issue is caused and how to resolve such issues.
Customers who want to consume Dynamics NAV data with OData in Microsoft Excel and have company names such as CRONUS A/G or CRONUS Danmark A/S may find it difficult or result in an error. When connecting to an OData feed from Excel, this does not work unless you don’t specify a Company Name in the connection string and set the company as a “Services Default Company” on the Dynamics NAV Server instance.
There are some very good reasons why you would want to have a test company setup for Dynamics NAV, including new employee training, exploring process changes, or before adding new, or updating existing, functionality. Having a test company allows you to examine the cause and effect of making changes to your master data (customers, items, vendors, etc.) without impacting your production data.