You are viewing an earlier version of the admin guide. For the latest version, please visit EmpowerID Admin Guide v7.211.0.0.

Create Data Model Mapping File

The data model mapping file maps the columns of the delimited file and EmpowerID object attributes. In an outbound mode, a data model mapping file will define which EmpowerID object attributes are exported to which column of the Flat File. Whereas in an inbound mode, a mapping file will point which columns to import into what attributes of the EmpowerID database. E.g., you might choose to export/import an attribute BirthDay in EmpowerID into the Date_of_Birth column in flat files. The mapping file is a CSV file.

Sample Data Model Mapping File


Please find a sample of the model mapping file below. You can download and modify it to fit your requirements.


How to Create A Data Model Mapping File


To create the mapping file you will mainly need ObjectAttributeName, PersonSecurityBoundaryAttributeName, SystemSecurityBoundaryAttributeName, RbacObjectName, SystemSecurityBoundaryAttributeName & SyncDirection. Please find the details below about how you can find these information/attributes to complete the mapping file.

ObjectAttributeName


The first information to populate in the mapping file is ObjectAttributeName. Please follow the details below to find the ObjectAttributeName,

  1. Navigate to Admin → Application and Directories → Manage Schema

  2. Click on the Security Boundry Attributes tab.

  3. Click on the down arrow on the search textbox to bring advanced search options.

  4. Now we will find the required Object Attribute. Select the Security Boundary Type and click on search.
    One easy way to find the object attributes is to search by Security Boundary Type. E.g., You want to write the LOCAT attribute to the flat file. If you know that this attribute comes from the SAP-HR, you can filter the results using the same Security Boundary Type.

     

  5. Find the object attributes for the field you are looking to import/export. Please add the required attribute to the ObjectAttributeName column on the mapping file.
    E.g., you can see that the Object Attribute for LOCAT is StreetAddress3, so that's the Name of the attribute "StreetAddress3 "to map in the ObjectAttributeName column of the mapping file.

PersonSecurityBoundaryAttributeName:


We have already explored how to find the ObjectAttributeName in the previous section. The mapping file also contains a column for PersonSecurityBoundaryAttributeName, which must be specified for all the attributes you have in the ObjectAttributeName column. Please follow the details below to find the PersonSecurityBoundaryAttributeName,

  1. Navigate to Admin → Application and Directories → Manage Schema

  2. Click on the Security Boundry Attributes tab.

  3. Click on the down arrow on the search textbox to bring advanced search options.

  4. Change the Security Boundary Type to EMPOWERID, provide the ObjectAttribute Name you are looking for and click on search. In the screenshot below, we are searching for StreetAddress3.




  5. Find the PersonSecurityBoundaryAttributeName and add it to the mapping file. e.g., StreetAddress3 is the PersonSecurityBoundaryAttributeName for the attribute.

SystemSecurityBoundaryAttributeName


SystemSecurityBoundaryAttributeName is the column name in the Flat Files. Please specify the column headers for attributes to target while exporting or importing the data from the connector.

 

RbacObjectName


Specify “Account "as the RbacObjectName.

 

RbacObjectAttributeName


RbacObjectAttributeName is the Name of the mapped attribute in the Account table. Please follow the steps below to find the list of RbacObjectAttributeName information.

  1. Navigate to Admin → Application and Directories → Manage Schema

  2. Click on the RbacObjectAttribute tab.

  3. Click on the down arrow on the search textbox to bring advanced search options.

  4. Type Account in the ComponentName and click on search to filter all Account object attributes. You can also specify a name to find attributes with a similar name. If no similar attribute exists in Account RbacObject, an ExtensionAttribute or a CustomAttribute can be use.



  5. Find the Name of the attribute you want and add the names for the attributes in the mapping file. E.g., There is an attribute of StreetAddress3 for the account in the screenshot above.

SyncDirection

Please specify the mode of synchronization of a particular attribute between an external system and EmpowerID.

Inbound

Use inbound mode to sync an attribute only from the external system into EmpowerID.

Outbound

With Outbound mode, attribute changes in EmpowerID will be synced into specified columns of flat files.

Bidirectional

Bidirectional mode synchronizes attributes from the External system into EmpowerId and vice versa using flat files.

 

Once you have mapped all the attributes described above, you can use the Data Model Mapping File to create the Flat File Connector account store.

Â