When a new Lite Model is built, it produces a 'materialized data model' and a 'model definition file'. If you created a new database from the Target stage, a 'materialized database' will also be produced. The materialized model is the data model that is accessed via Discover, where queries are run against the materialized model and visualized as data discoveries. Custom formulations can also be built on the materialized model in Formulate. The materialized model is stored in a materialized database on the selected server.
The model definition file, on the other hand, is the file containing all the logic and settings defined by the user when building the data model. Like other content items, the definition file is stored in the content manager, where it can be opened, copied, moved, and deleted.
To edit an existing data model you must access its definition file, which will be opened in the Model Pro module.
Open the Model
By default, the definition file of the Lite Model is saved to the My Content folder of the user who created it. To open the definition file, go to My Content and click the file.
Edit the Model
The file will be opened in the Model Pro app, where you can edit it from four modules:
- Master_Flow: only users belonging to a Profile that has permissions to the Master Flow will have access to it. The Master Flow is an advanced toolset used to perform complex data cleansing and manipulation.
- Data Flow: connect to a data source, manipulate the data set as required, and load it into a destination.
- Data Model: define relationships between the model’s tables, define measure columns, construct hierarchies, and more.
- Security: set security permissions for the data model by selecting which roles will have read or write access the database and/ or the data model. Users belonging to a role with read access to the model will be able to open it in Discover; those belonging to a role with write access will be able to edit the model.
After editing the data model, be sure to save changes and reprocess the model. Reprocessing ensures that the model is rebuilt, so it will reflect any changes or edits made to the definition file.