1. Home
  2. General
  3. Master Dictionary Menu

Master Dictionary Menu

A recent common request has been the ability to control multiple dictionary menus from a central/master dictionary. In the past, the answer for this request has been to drop the mrc security tables from the database and create views in each dictionary pointing to the master dictionary security tables. While this method will continue to work, we have implemented a simpler approach without the need for direct database access.

Step 1: Master Dictionary

Configure your master dictionary security with your desired users, user roles, and menu.

Step 2: mrcMenu.json File

  1. Download the mrcMenu.json file onto the m-Power server.
  2. Open the file in a text editor such as notepad++.
  3. Replace “DICTIONARY” with the name of your master dictionary name. Note: If using SQL Server, be sure to include the “.dbo.” schema qualifier between the database and table name.

Step 3: Point Sign On Security to Master Dictionary

  1. Switch to a non-master dictionary and toggle/enable security.
  2. Open Security Settings.
  3. Make sure “Validation Type” is set to ‘Validate by database table’.
  4. Under “Validate by Table”, set the “tablename” to the master dictionary name. Note: Again, if using SQL Server, be sure to include the “.dbo.” schema qualifier between the database and table name.
  5. Save.
  6. Repeat for all dictionaries.

Step 4: Point Menus to Master Dictionary Menu

  1. Move this mrcMenu.json file to all dictionaries of your choice. Place this in the /mrcjava/WEB-INF/classes/[DICTIONARY] (where [DICTIONARY] is the name of your dictionary).
  2. Restart Tomcat.

Editor Notes

  • You can also use non-MRCSEC tables to point your dictionary menu towards by replacing the appropriate MRCSEC# table. Be aware: The field names of the non-MRCSEC tables must match the field names of the proper MRCSEC tables in order for the menu mapping to work correctly.
Updated on May 19, 2023

Was this article helpful?

Related Articles

Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
CONTACT SUPPORT