Office +1 (678) 666-2100
Fax: +1 (678) 666-1997

Search:

How to move Easy Security data from a test environment to production

It is common practice to create Easy Security data such as Permission Sets, Permission Groups, Recordings, Object Properties, Logins, Field Level Security Codes and Data Security Codes in a test database in order to easily test new configurations without disrupting users in production. This data can be easily moved to production by using the Import/Export features in Easy Security.

This document is written under the assumption that Easy Security has already been installed in the production database.

Any or all of the following can be easily exported from the test database and imported into production.

Permission Sets

Permission Sets can be exported one at a time, or multiple Permission Sets may be selected and exported. Once exported, use the Import function to bring them into production. If the Permission Sets already exist and just need to be updated, use the Import (Overwrite Existing) option.



Note: The Permission Set export includes Recordings, Recording Permissions, and Role Builder Permissions. Roles that are not maintained with the Role Builder cannot be exported, this includes the SUPER and Permission Sets for Quick Security and Object Level Security generated based on the Object Properties.


Permission Groups

Permission Groups can be exported one at a time, or multiple Permission Groups may be selected and exported. Once exported, use the Import function to bring them into production. If the Permission Groups already exist and just need to be updated, use the Import (Overwrite existing) option.

Note: Permission Sets must already be imported if they are part of Permission Groups.

Object Properties

Object Properties can be exported one at a time, or multiple Object Properties may be selected and exported. Once exported, use the Import function to bring them into production. If the Object Properties already exist and just need to be updated, use the Import (Overwrite Existing) option.

The Permission Sets based on the Object Properties cannot be exported as a Permission Set this is the Quick Security and Object Level Security. When importing the Object Properties is the Permission Sets created properly, this include the Quick Security and Object level Security Permission Sets.

Note: If deleting records in the Object Properties, all Object Properties can be exported from the test database and before importing delete all the Object Properties in the production database.

Recordings (not included in a Role)

Recordings can be exported one at a time, or multiple Recordings may be selected and exported. Once exported, use the Import function to bring them into production. If the Recordings already exist and just need to be updated, use the Import (Overwrite Existing) option.

Note: When importing Recordings or Permission Sets including Recordings can the number series used for Recordings be messed up by newer numbers imported. Change the number series in the Security Setup for the production database to use a different number series than the default RECxxxx, it could be for example PRODxxxx.

Logins (Login Access Controls)

Login Access Controls can be exported one login at a time, or multiple Logins may be selected and exported. Once exported, use the Import function to bring them into production. If the Login Access Controls already exist and just need to be updated, use the Import (Overwrite existing) option. The Logins must already exist in Easy Security. To create the login; add the Users in the standard NAV security tables and use the Get New Logins from Live to add in Easy Security.

Note: Permission Sets and Permission Groups must already be imported if they are part of the Login Access Controls. Company Groups must be created manually to match the exported data.

Field Level Security Codes and Data Security Codes

Codes can be exported one at a time, or multiple codes may be selected and exported. Once exported, use the Import function to bring them into production. If the codes already exist and just need to be updated, use the Import (Overwrite Existing) option.

Note: If the Field Level Security Code or the Data Security Code is copied from the Setup Company must the import the done in the right company.

The following must be set manually in production:
User Security Setup
User Filters
Source Table Setups
Login Setup
All of the tables above is a simple record and can be copy/pasted in most version of NAV after importing the complex structures above.



Like   Don't Like

© 2017 Mergetool.com. All rights reserved.



Related resources

Download software from Mergetool.com