Dynamically Mapping User Identification Information
If the standard SuiteSignOn ID fields are insufficient for a certain application, you can establish dynamic identity mappings. To establish dynamic identity mappings, you can create a landing page and prompt each user upon first connection to log in. Alternatively, enter their ID in the third-party system, and submit the mapping back into a custom entity field, which is available to SuiteSignOn through SOAP web services.
When you populate the field, the third-party application connection bypasses the landing page. The identity of the user is known. The user must be logged in to NetSuite with a role with permission to update user's own entity record to set the custom field.
If the logged in user's role does not have the permission to update the entity record, you can create a custom record to track identity mappings for a certain SuiteSignOn integration. Another entity custom field can source the mapping from the custom record.
For instructions for setting up custom fields, in the NetSuite Help Center see Creating a Custom Field. For instruction on creating custom records, see Custom Records.