Dynamics NAV Development for Non-Developers: Part 4 – Moving Object Changes

by | Updated August 15, 2016 | Development, Dynamics NAV

In Microsoft Dynamics NAV development you will always want to make changes in a non-Production database first. You will need to understand the mechanics of moving those changes to Production, once tested and approved. This entry in the series will walk through the process of moving object changes.

Considerations for Moving Object Changes

Backup the Production database (optional)

If you are moving table changes, a SQL backup of the Production database is recommended. If you are moving other objects (pages, reports, etc…), a backup is not necessarily needed. If a non-table object was inadvertently overwritten or corrupted, it would be relatively straight-forward to pull the “old” version back from a recent nightly backup. Table object moves aren’t quite as simple, so it is possible you would want/need to restore the entire backup.

Verify the object to be moved contains all of the logic already in Production.

Before making changes to an object in a non-Production database, you should always double-check that the date and time stamps on the object are consistent between the Production database and the one in which you will be working. On the chance that this step may have been skipped, you will want to consider the date and time stamps on the production object to determine if it has been modified since the Test/Dev database was last refreshed (i.e. you did start with an exact copy of the Production object before making your changes).

Dynamics NAV Development








If you are moving table changes, verify that users are out of the system

Depending on the nature of the changes, data loss can occur when moving table changes. While this is rare, it can happen. Reasons include inadvertently removing a field that contained data, changing the definition of an existing field, the specific build of NAV, and current schema synch status with the server. As mentioned above, you should take a backup first. Directly related, all other users should be out of the application when making table moves.

Process of Moving Object Changes

Select objects to be moved (from test/development database)

If you have a single object to move, simply select that line in the development environment (object designer). If you have multiple lines, you can filter the objects by Date, Version List, through the use of toggle marking, or by using Ctrl+mouse click to select lines (like Excel). Then select/highlight all objects to be moved.

Dynamics NAV Development








Export objects

With the objects highlighted, select File – Export from the toolbar. Select a location and provide a name for your exported object file. An example might be “ObjectsForProd_20160131.fob”. The file extension should always be .fob. Save the file to close the window.

Import objects

Open the target database (Production) from the development environment (object designer) and select File – Import from the toolbar. Select the location/file you exported in step 2 and then the “Open“ button. You should receive a message asking whether or not to open the Import Worksheet. You should always select the option that opens the Import Worksheet. NAV will then return a list of the objects to potentially apply to Production.

Import Objects in Dynamics NAV








Process the Import Worksheet

As a matter of habit, always select the “Replace All” button. This will ensure that the objects imported will overwrite the existing objects – or set them to the ‘Create’ Action when they are new. Other Actions include Skip and Merge, but these should not be needed unless you are working with more complicated object movement scenarios. Note the “Existing” and “New” date and time stamp columns (you may need to show them in the worksheet). These help provide a quick view to ensure you are not potentially overwriting a recent change in Production. When comfortable with the actions, select OK.

Synchronize Schema (if tables)

If tables are included in the import, select the ‘Now – with validation’ option to “Synchronize Schema” – when presented. This ensures that the server validates the changes and recognizes the same table definitions as are in SQL. If you are dropping/deleting a field for any reason, you would need to instead select the ‘Force’ option here. This option should only be used if you are 100% certain that the field you are dropping is not needed. Select OK when ready. You will be also be presented a final warning about tables. Select ‘Yes’ to this as well – which should return a Synchronize Schema Changes “State” of ‘Operational’.

Import Fob in Dynamics NAV










Review the confirmation message

This message provides a summary of the changes applied. Select OK to close the window.

Import Completed in Dynamics NAV










The process to move objects in Dynamics NAV is actually very efficient once you understand and have been through these steps a couple times.

For more on Dynamics NAV Development for Non-Developers, check out the rest of the series.


Related Posts


Submit a Comment

Your email address will not be published. Required fields are marked *

Upcoming Events


02sep10:00 am10:30 amThe Modern Manufacturer - Cycle Count Management

02sep12:00 pm12:30 pmBest Practices for Work Order Planning and Routing for Field Service Companies

09sep10:00 am11:00 amWhat is Levridge? An Overview of the Ultimate Ag Solution

09sep12:00 pm12:30 pmOverview of Microsoft Promotion for NAV and GP Clients

10sep11:00 am12:00 pmConfab with Stoneridge - Livestream - Field Service Comparisons

16sep10:00 am10:30 amThe Modern Manufacturer - Product Lifecycle Management

16sep12:00 pm12:30 pmHow to Upgrade to Dynamics 365 Finance and Operations: Examining Custom Code and ISV Implications

16sep2:00 pm2:30 pmScheduling and Dispatching for the Modern Field Service Company

23sep12:00 pm1:00 pmDynamics 365 Business Central Wave 2 Release Preview - An Overview of the Most Exciting New Features Coming in October

24sep11:00 am12:00 pmConfab with Stoneridge - Livestream - The Modern Workplace: Teams, Sharepoint, Outlook, Office, and AI Integration

30sep10:00 am10:30 amThe Modern Manufacturer - Return Management

30sep12:00 pm12:30 pmEmpowering Your Field Service Technicians with a Mobile Solution


07oct12:00 pm1:00 pmThe Three Paths to Business Central from Dynamics GP

08oct11:00 am12:00 pmConfab with Stoneridge - Livestream - The Vision and Strategy of Microsoft Business Systems

14oct10:00 am10:30 amThe Modern Manufacturer - Complex Cost Modeling

14oct12:00 pm12:30 pmGenerating Custom Inspection or Process Forms

19octAll Day22Stoneridge Connect Fall 2020

22oct11:00 am12:00 pmConfab with Stoneridge - Livestream - Stoneridge Connect Recap

28oct10:00 am10:30 amThe Modern Manufacturer - Engineering Change Orders

About Stoneridge
Stoneridge Software is a unique Microsoft Gold Partner, with emphasis on partner. With specialties in Microsoft Dynamics 365, Microsoft Dynamics AX, Microsoft Dynamics NAV, Microsoft Dynamics GP and Microsoft Dynamics CRM, we focus on attracting the most knowledgeable experts in the field to our team, and prioritize delivering stellar solutions with maximum impact for your business. At Stoneridge, we are deeply committed to your results. Each engagement is met with a dedicated team, ready to provide thorough, tailored, and expert service. Based in Minnesota, we intentionally “step into your shoes,” wherever you are. We focus on what you care about, and develop trusting, long-term relationships with our clients.

Subscribe To Our Blog

Sign up to get periodic updates on the latest posts.

Thank you for subscribing!