Tips & Tricks - Match user schema between two portals

This article shows how several portal instances of one and the same portal (e.g. development, test and production portal) can be kept at the same configuration level with an extended schema. If new attributes are created for user objects, these should exist in all portals with identical GUIDs, names and database field names. The complete user schema can be exported and imported into the target portals.

If an application (e.g. from a development portal) is exported that has links to user-defined attributes, missing attributes are displayed when the application is imported into the target portal (e.g. a test portal) or it is possible to link the attributes to attributes in the target portal. With this procedure, however, the GUIDs of the attributes differ.

To avoid this, the complete schema can be exported in the source portal (e.g. in the development portal) in the "User" module via the "Schema" menu in the schema manager. The schema is saved as an XML file for all object classes of the portal and can be imported in the target portal (e.g. in the test portal) in the same way. The schema synchronization should be performed consistently after every change between all relevant portals. After synchronization, the basic requirements for application imports are identical. The import can then be carried out smoothly in the target portal.