Importing a NAV Object File (.fob)

4309 Hacienda Drive, Suite 435

Pleasanton, CA 94588

(510) 747-1970

(800) 456-8474 Toll Free

(510) 747-1977 Fax

info@beckconsulting.com

www.beckconsulting.com

Table of Contents

Overview ....................................................................................................................................................... 1

Preliminary Steps .......................................................................................................................................... 1

Importing the Object File .............................................................................................................................. 2

Compile the Imported Objects ...................................................................................................................... 6

Restart Services (all versions through 2009 R2) ........................................................................................... 9

Post-Import Activities ................................................................................................................................. 10

PORTIONS OF THIS DOCUMENT HAVE BEEN EXCERPTED FROM MICROSOFT DOCUMENTATION. ALL RIGHTS ARE RESERVED BY BECK

CONSULTING/BCG MANAGEMENT RESOURCES, INC. (Rev. 3/2016)

1

Overview

A NAV object file (often referred to as a “.fob” due its file extension) contains the NAV database objects that have been modified as part of a release. In order to implement the changes that have been made to these objects, it is necessary to import the .fob into your NAV environment. The steps that should be followed to import this file are explained in this document. The process for importing a .fob into Dynamics NAV is generally the same regardless of which NAV version is being used. There, are however, subtle differences from version to version. As you review the instructions in this document, please be on the lookout for version-specific notes that may be applicable to the processes you need to perform.

Preliminary Steps

Prior to importing an object file into NAV, you should perform the following activities: 1. Save the object release. Your object will be sent to you as an e-mail attachment. Typically, this

attachment will take the form of a .zip file, which contains both the release itself and release notes that describe the changes that are incorporated in the release, as well as any special importing/setup instructions. You can identify the object release file by its .fob file extension:

Extract the object release to a folder on your computer or on a network location that will be accessible from the NAV Classic Client (all versions through 2009 R2) or NAV Development Environment (versions 2013 and forward) later on in this process.

PORTIONS OF THIS DOCUMENT HAVE BEEN EXCERPTED FROM MICROSOFT DOCUMENTATION. ALL RIGHTS ARE RESERVED BY BECK

CONSULTING/BCG MANAGEMENT RESOURCES, INC. (Rev. 3/2016)

2

2. Ensure users are logged out of NAV (optional). It is recommended that all users besides you are logged out of NAV while you import the object release. This is most easily accomplished by importing object releases before or after normal business hours, when the chances of other users being logged in are low. We understand that this is not always practical, especially for companies with a global presence, or a 24 hour work day. Please be aware that users who are working within NAV while an object file is being imported may be inadvertently forced to close a page, or the entire application itself. While inconvenient, this is not a critical issue, as the user can simply re-open the page/application and continue work as usual.

At any time, you can view a list of currently-logged in sessions. The manner in which you perform this activity is version dependent:

All versions though 2009 R2: Log into the Classic Client and select File, Database, Information from the menu bar. When the Database Information window is open, select the Sessions tab. The Current Sessions field should have a value of 1, since you should be the only user logged into NAV. If the Current Sessions value is greater than 1, click the drill-down next to the value to view a list of the currently-logged in accounts:

Versions 2013 and forward only: Log into the RoleTailored Client, and type "Sessions" in the Search bar to open the Session List, which lists the currently-logged in accounts:

Importing the Object File

Before to importing the object file, review the release notes that are included in the .zip file through which the released was delivered for any special import instructions. In some cases, certain steps must be performed prior to importing the .fob file. NOTE: If an object file’s release notes contain any adjustments to the import steps are that defined in this document, the release file’s instructions should take priority over the standard procedure.

PORTIONS OF THIS DOCUMENT HAVE BEEN EXCERPTED FROM MICROSOFT DOCUMENTATION. ALL RIGHTS ARE RESERVED BY BECK

CONSULTING/BCG MANAGEMENT RESOURCES, INC. (Rev. 3/2016)

3

Once you have saved the .fob to an accessible location, reviewed the release notes, and ensured all users are logged out of NAV (if desired), you can import the object file by performing the following steps: 1. Log into NAV. Object file imports are performed through the Object Designer, which is not

accessible through the RoleTailored Client. Accordingly, you must log into the Classic Client (all versions through 2009 R2) or NAV Development Environment (versions 2013 and forward). Please note that the user who performs the object import activities must be set up as a superuser within NAV and the appropriate SQL roles to modify the database (this can either be the “sysadmin” role for the entire server or a “db_owner” role for the specific database). For more information on setting up NAV security, please contact your Beck Consulting representative.

2. Open the Object Designer (all versions through 2009 R2). If you have logged into the NAV Classic

Client, you must manually open the Object Designer. From the menu bar, select Tools, Object Designer:

This is not necessary for users who access NAV via the more recent Development Environment, as the Object Designer will automatically open upon login.

3. Locate and open the .fob. With the Object Designer open, select File, Import from the menu bar:

PORTIONS OF THIS DOCUMENT HAVE BEEN EXCERPTED FROM MICROSOFT DOCUMENTATION. ALL RIGHTS ARE RESERVED BY BECK

CONSULTING/BCG MANAGEMENT RESOURCES, INC. (Rev. 3/2016)

4

This opens a dialog box that allows you to select a file. Navigate to the folder in which you saved the .fob file (see Preliminary Steps above). You can either double-click on the .fob file or click it once and then click the Open button in the dialog box.

4. Import the .fob. After you open the object file, you should receive the following message:

Click Yes to import the objects.

NOTE: If you get a message about conflicting versions, click Cancel and contact Beck Consulting. DO NOT CONTINUE THE IMPORT PROCESS.

Version 2015 forward: If the object file contains table objects, you will receive the following message:

Unless stated otherwise in the Release notes, make sure "Now - with validation" is selected as the Synchronize Schema option, and click OK.

PORTIONS OF THIS DOCUMENT HAVE BEEN EXCERPTED FROM MICROSOFT DOCUMENTATION. ALL RIGHTS ARE RESERVED BY BECK

CONSULTING/BCG MANAGEMENT RESOURCES, INC. (Rev. 3/2016)

5

i. A message will be presented stating that "Microsoft Dynamics NAV server is going to

perform validation of all table changes..." Select Yes to continue. If the window does not automatically close after the synchronization reaches 100%, click the Close button.

ii. NOTE: If you get an OperationalWithSyncFailure message noting that "Changes

were found that may delete data...", check the release notes for alternate instructions on importing the objects. If none exist, please contact Beck Consulting.

5. Review the object import. Once the objects contained in the .fob have been imported into your

database, NAV will present a confirmation message notifying you how many of these objects were created, replaced, merged, etc.:

NOTE: Unless stated otherwise in the release documentation, the total number of merged and skipped objects should always be ZERO. If this is not the case, contact Beck Consulting. Select OK to acknowledge the successful object import.

PORTIONS OF THIS DOCUMENT HAVE BEEN EXCERPTED FROM MICROSOFT DOCUMENTATION. ALL RIGHTS ARE RESERVED BY BECK

CONSULTING/BCG MANAGEMENT RESOURCES, INC. (Rev. 3/2016)

6

Compile the Imported Objects

Following the object import, it is recommended that you compile the new objects. 1. Set a filter for the imported objects. In the Object Designer, 1) select the All option on the left, then

2) select any field in the Version List column.

Press F7. The Field Filter window opens. Enter an asterisk, followed by the release you just imported, followed by a second asterisk. For example, if you imported release ABC01.00, you would enter *ABC01.00* as your filter:

Select OK. The Object Designer should now list only those objects that were just imported.

PORTIONS OF THIS DOCUMENT HAVE BEEN EXCERPTED FROM MICROSOFT DOCUMENTATION. ALL RIGHTS ARE RESERVED BY BECK

CONSULTING/BCG MANAGEMENT RESOURCES, INC. (Rev. 3/2016)

7

2. Compile the objects. Select/highlight all the objects displayed in the Object Designer, then select Tools, Compile from the menu bar:

NAV will ask you if you want to compile the selected objects. Click Yes to do so.

Version 2015 forward: If you are attempting to compile any table objects, you will receive the following message:

Unless stated otherwise in the Release notes, make sure "Now - with validation" is selected as the Synchronize Schema option, and click OK.

NOTE: If any errors result from the compilation, contact Beck Consulting.

PORTIONS OF THIS DOCUMENT HAVE BEEN EXCERPTED FROM MICROSOFT DOCUMENTATION. ALL RIGHTS ARE RESERVED BY BECK

CONSULTING/BCG MANAGEMENT RESOURCES, INC. (Rev. 3/2016)

8

3. Compile MenuSuite objects. If an object import contains changes to any MenuSuite objects, you must also compile all MenuSuite objects following the initial compile process. In the Object Designer, press Shift+Ctrl+F7 to clear any filters that were set in the previous steps, then select the MenuSuite option on the left and select/highlight all displayed objects.

Select Tools, Compile from the menu bar. NAV will ask you if you want to compile the selected objects. Click Yes to do so.

PORTIONS OF THIS DOCUMENT HAVE BEEN EXCERPTED FROM MICROSOFT DOCUMENTATION. ALL RIGHTS ARE RESERVED BY BECK

CONSULTING/BCG MANAGEMENT RESOURCES, INC. (Rev. 3/2016)

9

Restart Services (all versions through 2009 R2)

If you are working with NAV versions up to and including 2009 R2, you must restart any related services. Please note that restarting the services will automatically log out any users who are working within NAV. 1. Open the Services window. From the server that hosts the NAV service tier, log out of NAV, then

open the Services window. You can either search for "Services" in Windows Explorer, or open Control Panel, System and Security, Administrative Tools:

2. Restart the NAV Service Tier. In the Services window, locate and select the “Microsoft Dynamics NAV Server” (this may be named differently in your environment) service:

Restart the service by clicking the Restart option to the left (alternatively, you can right-click the service and select the Restart option from the context menu that appears).

PORTIONS OF THIS DOCUMENT HAVE BEEN EXCERPTED FROM MICROSOFT DOCUMENTATION. ALL RIGHTS ARE RESERVED BY BECK

CONSULTING/BCG MANAGEMENT RESOURCES, INC. (Rev. 3/2016)

10

3. Restart NAS (optional). If you are using the NAV Application Server (NAS) to automate processes, you should restart this as well by locating and selecting the Application Server for Microsoft Dynamics NAV (this may be named differently in your environment) service:

Restart the service by clicking the Restart option to the left (alternatively, you can right-click the service and select the Restart option from the context menu that appears).

Post-Import Activities

Following the successful import, compiling, and restarting of services (if necessary), you can perform the following activities: 1. Allow users back into NAV. If users were required to log out of NAV prior to the object import (see

Preliminary Steps above), or automatically logged out as a result of the services restart, they should be informed that they can now log back into the application.

2. Update version control documentation. It is recommended that you maintain a history of your

object import activities. Once a .fob has been successfully imported, you should add the object release, database, and installation date to this documentation. Contact your Beck Consulting representative for a template that can be used to manage releases.

3. Notify Beck Consulting. Please send an e-mail to your Beck Consulting representative noting that

the release has been imported. As part of this notification, be sure to indicate the database (Production (Live) / Dev (Test/Play/Sandbox)) in which this took place.