Managing dependencies

Altogic manages the dependencies across the models and fields of your data model design. For example, when you use expressions that access fields of a model in another field's default value expression or validation rules or create object references, you indirectly create dependencies among models and fields.

Dependency information is useful, especially when you try to delete a field and/or model. In such a case, Altogic automatically identifies all dependencies to the model and/or field that will be deleted and provides a warning message. Then, of course, you can continue with the delete operation. Still, in such a case, you need to update all dependencies to eliminate any possible errors in the execution of your services.

To view dependencies to a specific field via the Designer, you need to Navigate to Models view and select the model or the field that you would like to see its dependencies. Next, you will be directed to the model or field details view. Select the Dependencies tab to access all models and/or fields dependent on the selected model or field.

The example below shows dependencies to the product model. There are two models, "procurementOrder" and "salesOrder," dependent on the product model. In both "procurementOrder" and "salesOrder" models, there is an object reference field called "product," which points to the product model.

Below is another dependency example that shows dependency on a model field. This example shows that the "fullName" field in the "user" model is dependent on the "lastName" field in the same model. The reason fullName is dependent on lastName because its default value expression uses the "lastName" field.