Tyler Technologies provides Munis ERP, a product designed to help municipal entities with their enterprise resource planning (ERP). Munis ERP is also utilized in the education sector through ERP for Schools (powered by Munis), which is commonly adopted by larger K-12 school districts in the United States.

The Munis ERP platform includes specialized modules for:

Integration aims to support streamlined integration of user data through the Human Capital Management area of Munis ERP by providing districts using the cloud-hosted and on-premise versions of Munis ERP with tools to import key user data into iiQ on a recurring basis. User data imported through this integration will be key for streamlining cross-departmental workflows for IT, HRSD, and Facilities teams at K-12 school districts.

The Munis ERP integration for user data works through an automatic .csv file import utilizing Secure File Transfer Protocol (SFTP). After uploading a .csv file to the authorized SFTP server, Admins will have the ability to map columns contained in the .csv file to user fields in iiQ to import contents of the file to user profiles using any or all of the following matching methods (id, email, or username). In addition to mapping columns to new user fields, admins will also have the ability to create new custom fields for user data from the app management interface. Based on mappings configured within the app that determine how the file should be parsed and imported, the nightly import will occur during a recurring nightly “sync” of the app. This integration offers the option for districts to utilize an iiQ-hosted server or a server hosted by the district for file transfer.

​

An iiQ Admin, or user with permission to Manage Apps, will first need to go to Incident IQ Apps > Browse from the left navigation menu, search for “Munis ERP,” and install the app.

After successfully installing the app, select “Manage App Settings”.

After installing the app, Admins need to configure the server settings to support the nightly file transfer. IF the district wishes to use a server hosted by the district for the nightly import, they will need to add the following information to the settings tab:

If the district would like to use an iiQ-hosted FTP site, admins should simply click the option to Use iiQ Hosted FTP site. Once the server has been successfully provisioned, the user should receive a confirmation message containing the credentials needed to access the server.

Once the SFTP server credentials have been saved within the app in iiQ, the district will need to upload a .csv file to the server to complete the mapping profile for the file. Once a file has been uploaded to the server, the admin will need to map a user identifier within the Settings tab of the app prior to running the first sync.

Map User Identifiers for Matching

Mapping a user identifier is the only required field mapping for running the import, and this field mapping basically instructs the importer on how to match rows or entries contained within the .csv file to existing user accounts in iiQ. While only 1 mapping is required, districts are encouraged to map as many as necessary for an enhanced matching logic.

Admins will need to map any column from their .csv file (drop-down on left) to the ID, username, or email field mapping options within the app (drop-down selector on right) for matching. Please note that the contents of the mapped column should be exact matches for the data currently captured for the corresponding field in iiQ.

If multiple identifiers are mapped, the following logic will be used for processing (same as SSO app matching logic).

The logic looks up based on several properties in the following order and returns the first match it finds. So if it finds one by ID, it returns that user. Otherwise, it goes to the next, etc.

Complete field mappings

After selecting an identifier for matching, admins will then need to map any columns from the imported file to their corresponding user fields in iiQ. IF new fields are needed for mapping (IE, custom fields), these can also be created from within the app via mapping creation. After adding mappings, they need to click “Save” at the bottom of the page.

Mapping to default fields

Admin selects a field from the drop-down on the left that corresponds with the column header from the importer file they want to import.

Admin selects the corresponding field in iiQ that should map to the selected column.

Mapping to newly created custom fields

To create new custom fields that map to column headers from the Munis ERP export, select the “Custom Field” option in the selector on the right side. After selecting this option, a new set of options will appear on the right. The custom field's name should be added in the first text field. Once the name is entered, a field type (Text, Date, Number) should be selected. If the admin would like to filter by the field, they should select the “custom field is searchable” option.

This app supports 2 types of syncs:

The sync History tab of the app functions very similarly to the Sync History tab for one roster .csv-based SIS apps. Admins will have the ability to:

Several new primary fields will be added to Users as part of the Munis ERP release. In addition to the new primary fields, field visibility, and editability controls have been implemented so that some fields are only visible or editable from specific products on the platform.

List of new fields:

A full list of the new Primary fields to be added to user profiles in iiQ can be found below. Please note that the fields with an * are only visible and editable from HRSD.

HRSD New Onboarding workflow - Add New Hire Email to both email fields

When a “New Employee Onboarding” ticket is submitted from HRSD, the email address captured in the “New Hire Email” field will be captured in both the “Email” and “Personal Email” fields on the newly created guest account.

User merge logic - Preserve personal email address during user merge

When user accounts are merged, the personal email address captured for the “Source User” account will be migrated to the “Target User” during the merge, so that this information is maintained on the user profile throughout the duration of that user’s employment with the district- this will assist with streamlining retirement/off-boarding workflows in HRSD.

Data Mapping - Add new primary fields as field mapping options

The following fields have been added to the field mapping options for Users within the Incident IQ Apps > Manage > Data Mapping page in iiQ Administration settings. These options will allow admins to specify which apps (or if any apps) should be able to overwrite the contents of that field for all user accounts.

User Revisions - Log field changes in the revisions widget

Changes made to the newly added primary fields for users will be logged in the revisions widget on user profiles.

User Views - (excludes home address and personal phone number)

Newly added primary fields will be available as filtering options in Users Explorer, Column Headers for User views, and exportable from iiQ (with the exception of home address and personal phone number).

User Importer - support new fields as mapping options in User Importer

Newly added primary fields will be available as mapping options for User Imports.

SSO Field mapping - Add new fields as mapping options in SSO apps

Newly added primary fields will be available as field mapping options within SSO apps.

---

Hannah Bailey - Director, Customer Engagement