Object Manager

Installation

Owned by idyn | Support team
Feb 13, 2024
5 min read

This chapter explains how to install Object Manager Advanced (OMA). This chapter also explains how to remove Object Manager Advanced with all its data from the database.

 

Installing Object Manager Advanced

Perform the following steps to install Object Manager Advanced:

Import Object Manager Advanced .fob file from the installation distributive using the development environment of Microsoft Dynamics NAV:

  1. Run Object Designer in Microsoft Dynamics NAV Development Environment.

  2. Click File > Import… and choose the .fob file from the installation distributive.

  3. A custom MenuSuite can be imported.

Adding SQL Triggers

You need to add certain SQL triggers to the Object table of the database in order to use the corresponding features of Object Manager Advanced:

  • The Trace Modification Trigger enables tracing modifications in database objects.

  • The Ask SQL Trigger speeds up certain tasks of the Object Manager.

  • The Block Database Conversion Trigger prevents the database will be converted to a newer version of NAV when opened with the wrong client. This trigger is optional.

Perform the following steps in Microsoft Dynamics NAV to add the necessary triggers:

  1. Go to Departments > Object Manager > Administration and then click Administration Tasks.

  2. In the Administration Tasks window, select the task that corresponds to the trigger that you want to add (steps 2-4 should be repeated for each trigger):

 

  • Add Trace Modification trigger

  • Add Ask SQL trigger

  • Add Block Database Conversion trigger

  1. Click Execute in the ribbon.

  1. Confirm the action in the dialog that appears.

After the trigger is added, the respective messages will be displayed.

You can remove the triggers using the appropriately named administration tasks.

Add Object View

The Object Explorer shows a combined view of C/Side objects and extension objects. The Objects Manager Advanced uses an object view to do this.

Perform the following steps in Microsoft Dynamics NAV to add the necessary triggers:

  1. Go to Departments > Object Manager > Administration and then click Administration Tasks.

  2. In the Administration Tasks window, select the task Add Object View.

  3. Click Execute in the ribbon.

  4. After the view is added, the respective messages will be displayed.

 

 

You can remove the Object View using the appropriately named administration tasks.

Add Service Account

Before you start using OMA, we recommend adding a user who runs your NAV Service instance, to the list of NAV Users. The SUPER role should be assigned to this user. It is necessary to allow this user to change database schemes when you import and compile tables.

By default, this service account is Network Service. It could also be a dedicated domain account. OMA will import/export NAV objects on behalf of this account in the background, on your server.

You can find out which user is running your NAV service by opening the corresponding service in Services console. Please see the example below:

Regional Settings

OMA requires that the Regional Settings are the same on your client and server machines. The regional settings can be applied for the user account. At the same time, NAV Service Instance can be run by a service account that doesn’t have any regional settings specified. In that case, this account will use “default” regional settings on the server.

These “default” settings are also applied for new user accounts. Sometimes (especially in European countries) it is required to synchronize the regional settings between your current and “default” accounts. You can do so by using the Copy settings… feature.

Please see below:

Please be aware that you will need to restart your server after applying these changes.

 

Multi-Tenant Setup

In a multi tenant setup the databases are split into APPLICATION and DATA databases.

Once the database has been split, OMA tables will be automatically moved to the DATA database. At the same time, the SQL Trace Modification Trigger assigned to the Object table will be located in the APP database. This trigger will try to access OMA tables in the same database, but will not be able to find these tables in APP.

In this scenario, it is required to enable the Tenant Database option in the Database Card > Tenant Database tab. You will also need to provide the other details of the SQL connection to your DATA database.

So, the APP database connection should be configured on the Database tab and the DATA database on the Tenant Database tab. Please see below:

 

Once it is done, please click Test action. If the connections are OK, you should go to Object Manager > Administration > Administration Tasks.

  • Select and execute Remove Trace Modification trigger task to delete the existing trigger from Object table.

  • Select and execute Add Trace Modification trigger task to add a new trigger which will be adjusted for multi-tenant setup.

Removing Object Manager Advanced

To remove Object Manager Advanced from the database, do as follows:

  1. Go to Departments > Object Manager > Administration > Administration Tasks.

  2. In the Administration Tasks window, select Remove Object Manager from database and click Execute.

This action is time-consuming.

 

IDYN 2024