Custom MU_ Security Groups is not syncing from CM to EERP
- Knowledge Assistant
A custom MU_ CM security group created within the Content Manager Full Client has been linked to a user's EERP role, but is not syncing over from EERP to the user's ID within the CM Full Client.
- Enterprise Resource Planning
- EERP
- Content Manager
- CM
- Full Client
- Custom Security Groups
- Permissions
- The custom MU_ CM security group ID likely has more than 20 characters which does not allow EERP to recognize and sync it to the CM Full Client.
- The group ID has a special character, such as a comma in the Group Name. Group Names can include dashes and spaces, but all other special characters should not be used.
Adjust the MU_ CM security group in the CM Full Client:
- Launch the CM Full Client
- Navigate to Administration > Security Manager > Groups
- Find and click once on custom MU_ CM security group
- Click the Duplicate Selected Item this is the double paper icon in the upper right hand corner
- Adjust the Group ID field to 20 or less total characters, all else can stay the same
- Adjust the Group Name, removing any special characters
- Click OK
- Find the and select the original 20+ character MU_ CM security group and click Show Menu (double green arrows in upper right hand corner) and then click Remove Entry
Navigate back to EERP:
- Launch the Tyler Menu
- Navigate to System Administration > General Administration > TylerCM for Munis Settings
- Proceed to reset the Master Password and Rebuild CM Cache
This custom MU_ CM security group will show up when linked to the desired Munis role, and will now sync over successfully from EERP to CM where it no longer has 20+ characters as the Group ID.
Please contact Content Manager Support for any further questions if the steps above are not working to sync the custom MU_ CM security group over from EERP to CM. Please also provide the particular custom MU_ CM group name as well as which environment you are working in (LIVE,TEST,TRAIN, etc).