Moving Attributes in CloudConnect Modeler
CloudConnect is a legacy tool and will be discontinued. We recommend that to prepare your data you use the GoodData data pipeline as described in Data Preparation and Distribution. For data modeling, see Data Modeling in GoodData to learn how to work with Logical Data Modeler.
After you have moved the attribute from the Payments dataset to the Employees dataset, double-click the Employees dataset. Notice the name of the moved attribute (Employee ID):
attr.payments.employeeid
This structure enables the unique identification by name of any object in the model.
Although the attribute has been moved, its internal identifier does not change, which preserves the relationships of the attribute within any project in the platform that is relying on this logical data model. The attribute may be logically repositioned in the model. However, it can still be referenced by the metrics, reports, and dashboards under its initial identifier. This identifier does not change as long as the object remains in the data model.
Move objects between datasets. Do not delete an object from one dataset and then add a new version of it to the other. Moving objects between datasets preserves internal identifiers and relationships between objects.
If you do need to remove objects from a logical data model that is already in use in projects, you may need to perform additional steps. See Managing LDM Dependencies in CloudConnect.
Structurally, the distinction between moving and deleting-then-adding is similar to dropping a database table and then adding a new version elsewhere in the database.
For more information on identifiers, see Attributes and Facts Window in CloudConnect.