mibuso.com
Home› NAV Three Tier
Options

Individual Database for each Customer-company - Best practice for maintaining objects globally

pn7pn7 Member Posts: 17
in NAV Three Tier
Hi

We have individual databases for each of our customer-company.

What would be a best practice to manage objects or parts of objects globally?

Example:

We have to add an XML-tag to a certain report. We have this exactly same object (or partially same with some customizations) now in multiple different databases.

Is the only way to update this object in every database following procedure:
- Open each Instance of NAV
- Copy and paste the additional line of code to the each instance's object?


Comments

  • Options
    kylehardinkylehardin Member Posts: 257
    In 2015 and 2016, you would have multiple tenants, one for each company, but those tenants would share an object database. Anything older than 2015, you just have to be disciplined with your release procedure. Once users have tested a change, you export the changed objects to a FOB file, and then make sure to load that same FOB file into every customer database.
    Kyle Hardin - ArcherPoint
  • Options
    DenSterDenSter Member Posts: 8,304
    You would never do the actual development in each instance, you would deploy the change in an object file, like Kyle is saying.

    Whether you go the tenant route, or separate databases, you could also use Powershell to write scripts to deploy those object files. That way you don't have to open any of the databases manually.
    Daniel Rimmelzwaan
    RIS Plus, LLC
    MVP - Business Apps
Sign In or Register to comment.