Updating a Blueprint
Last updated
Was this helpful?
Last updated
Was this helpful?
You can manage your and all its via:
The for a visual graph-based interface
Or by directly manipulating .
The is the most visually appealing of managing your blueprints, but it's not the most powerful one.
From the builder you are unable to:
Edit the blueprint's title.
Edit a property's metadata or data-type.
Edit a relation's title or (e.g. its target blueprint or its cardinality between one-to-one and one-to-many).
For these operations, you need to perform updates directly on the .
Changing a blueprint's ID is impossible across the product, regardless of whether via the UI or API. This is a measure meant to prevent issues related to data misalignment.
To see the content of a Blueprint, click on its node in the graph view.
From here, you can create new properties and relations.
You can also delete existing properties and relations.
You can also edit a blueprint's icon or deleting the blueprint.
From here, you can customise every aspect regarding your blueprint, like:
Editing the blueprint's metadata (except for the ID).
Some considerations:
Changing a blueprint's ID is impossible across the product, regardless of whether via the UI or API. This is a measure meant to prevent issues related to data misalignment.
From existing relations, you can establish .
Deleting a property or drastically changing its type in the blueprint can cause entities created from it to enter a conflict state that you'll need to resolve manually, see .
Deleting a blueprint can cause other blueprints that have relations to it and its respective entities to enter a conflict state that you'll need to resolve manually, see .
From a blueprint card you can also directly access the for more powerful manipulation capabilities.
Directly manipulating the is the most powerful way of managing your blueprint, but it also requires deeper technical knowledge.
Editing properties' metadata and .
Editing relations' metadata and (e.g. its target blueprint or its cardinality between one-to-one and one-to-many).
Deleting a property or drastically changing its type in the blueprint can cause entities created from it to enter a conflict state that you'll need to resolve manually, see .
Deleting a blueprint can cause other blueprints that have relations to it and its respective entities to enter a conflict state that you'll need to resolve manually, see .
