Versions Compared

Old Version 2

changes.mady.by.user Knowledge Assistant

Saved on

compared with

New Version Current

changes.mady.by.user Knowledge Assistant

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
borderColor#03396c
titleColorWhite
titleBGColor#03396c
titleDescription of Issue
  • How do you Export Roles from and Import Roles into MunisEnterprise ERP?
  • Created roles in one database and need to move them into another without manual entry

...

Panel
borderColor#03396c
titleColorWhite
titleBGColor#03396c
titleContext
  • Munis
  • Security & User Administration
  • Enterprise ERP


Panel
borderColor#03396c
titleColorWhite
titleBGColor#03396c
titleCause
  • Site created roles in the wrong Munis Enterprise ERP database and needs to move them into the correct environment 
  • Site is moving Munis Enterprise ERP versions and needs to test before the entire database is copied over
  • Site deleted a role and needs to copy it from another environment


Panel
borderColor#03396c
titleColorWhite
titleBGColor#03396c
titleResolution
  • The Export Role Data program allows you to export role-based security control records from a database. Using the Import Role Data program, you can import the control records into another database.
    Browse to Munis > System
  • IMPORTANT! Backup the target Enterprise ERP Database or export the Roles/Users of the target environment before attempting the steps below!


Export Role Data

  1. Log into source environment
  2. From the Enterprise ERP menu, navigate to System Administration > Security > Export Role Data
Select
  1. Click Define
Enter Choose
  1. In the
needed Export Directory file path
  1. Export directoryfield, enter the full path where the program is to store the export file on the source environment's application server
    1. OnPrem Example: D:\musys\muntest\export_test
    2. SaaS Example: D:\musys\mun1234test\export_1234test
  2. Choose desired Export Type
    1. All
(
    1. - export all role permission types
)
    2. Custom
(
    1. - enable custom export options for roles and users at bottom of the screen
)The Import Role Data program imports role-based security control records into one database after you have exported them from another database using the Export Role Data program.  Browse to Munis > System
  2. Click Accept
  • Export
    1. Click Export
    2. When complete, click OK


    Move Exported Files

    Move/copy the exported files from the source environment's export directory to the target environment's import directory. SaaS hosted sites, please reach out to TSM SaaS Support to have the files moved.

    • roassign.unl
    • rousratt.unl
    • rousrmst.unl
    • rodtlmnu.unl
    • rodtlmod.unl
    • rodtlper.unl
    • rodtlrng.unl
    • rolemast.unl


    Import Role Data  

    1. Ensure a backup of the target database has been taken before proceeding
    2. Log into target environment
    3. From the Enterprise ERP menu, navigate to System Administration > Security > Import Role Data
    4. Click Define
    Enter
    1. In the Import directoryfield, enter the full
    file path for the import directory
  • Complete the remaining fields according to the import requirements. Refer to the help screen's Field Descriptions table for details.
  • Accept
    • Import
    When the import is complete, the program displays a confirmation message.
    1. path of the location where the import file is stored on the target environment's application server
      1. OnPrem Example: D:\musys\muntrain\import_train\
      2. SaaS Example: D:\musys\mun1234train\import_1234train\
    2. Complete the import option fields as desired
    3. Click Accept
    4. Click Import
    5. On RBAC Import pop-up, click Yes
    6. When complete, click OK


    Panel
    borderColor#03396c
    titleColorWhite
    titleBGColor#03396c
    titleAdditional Information
    • SaaS hosted clients: Prod and Non-Prods are hosted on different servers. TSM SaaS can assist with moving the files out of the EXPORT Dir and into the IMPORT Dir for the environment needing the import.   
    • This is typically done with implementation or in coordinating coordination with deployment during server or version upgrades
    • Process required when refreshing database is not an option to copy roles from one database to another

    ...