Creating a New Entity Type Schema

Each new Identity Cloud customer is issued a single entity type (user) that comes with a reasonably large number of predefined attributes. Of course, that leads to an obvious question: is one entity type really going to be enough for you? 

To be honest, that question is largely irrelevant. After all, if one entity type isn’t going to be enough for you then you can simply create as many additional entity types as you need. In this section of the documentation, we’ll walk you through the process of creating a new entity type by:

  • Making a copy of an existing entity type. Keep in mind that this process creates an exact replica of the existing entity type’s schema: you now have a second entity type that contains the same attributes, validations, and transformations as found in the “base” entity type. However, new entity type doesn't contain any of the data stored in the existing entity type. Your new entity type will consist of a schema and no data. We’re copying the schema (i.e., the database blueprint) and not the entire database.
     
  • Importing a JSON (JavaScript Object Notation) file containing definitions for all attributes to be included in the new entity type. Importing a JSON file gives you the ability to create a truly custom entity type in a single operation. At the same time, however, it does require you to create a JSON file from scratch, something that can be a bit challenging if your new entity type includes objects and/or plurals.

Regardless of how you initially create your new entity type, you can change that entity type at any time, adding attributes, deleting attributes, modifying validations and transformations, and so on.