--- title: "Managing Objects" canonical: "https://docs.vaultspeed.com/space/VPD/3013181478/Managing%20Objects" format: markdown --- > Macro (toc) # Loading and Managing Objects and Attributes Objects can be loaded in several ways based on the initial requirements: - **Load all objects:** Drag the **"ALL OBJECTS"** item from the selection menu onto the editor pane. > 📝 ***Note****: * > 📝 > 📝 The editor supports a maximum of 30 objects at a time. - A single object and its relations can be loaded to the editor by simply dragging an object item from the selection menu. A depth selector allows choosing a depth level of the objects that should also be included in the editor. The relating objects have direct or indirect relationships to the selected object based on the depth selection. - Loaded objects can be moved by simply pressing and dragging them around. - Loaded objects can be removed from the canvas by selecting them and clicking the remove icon in the toolbar. - To clear the editor, press on the clear icon found in the toolbar (empty sheet icon) # Object Errors Some objects may appear red in the selection pane as well as on the canvas. This indicates that there is a problem with the object which needs to be fixed before you can proceed. When the object is on the canvas it will also indicate that it is in error. And when it is selected on the canvas, the Properties pane will also indicate the error at the top of the pane. ![image](media://b3850290-036e-4532-86de-585994e638ef) In the above example, the error message states that the object has no Primary Key defined. In this case, the object only contains information about a relationship between other objects. This kind of object should be defined as a Many-to-Many Link which requires at least two Foreign Keys. In order to define this table as a Many-to-Many Link, click the edit button in the properties pane and a number of fields will become editable. Change the object type to "Many-to-Many Link" and press the “Save” button to commit the changes. ![image](media://f029c16a-0193-437b-8992-40e50568a64f) You can also change the type of an object by right-clicking in the header bar of the object on the canvas and using the dropdown context menu. Don’t forget to click the Set button to change the actual data type.   When all errors are solved on the object, you will see the object type in the header of the object and it is no longer indicated as an error: ![image](media://5ccc9fdb-318e-44e3-8031-b0774c16509d) # Object Properties In order to change object properties, click on the header of an object to show it’s properties in the properties pane. The following object properties can be changed: - **Short Name**: The short name for an object, used for creating Link table names. - **Abbreviated Name**: The abbreviated name for an object, used for Hub and Satellite names, as well as Hashkey attribute names. - **Object Type**: Currently, we support the following object types: - **HUB & Satellite**: For this object, a Hub and a Satellite will be generated in the data vault model. - **Many to Many Link and Satellite**: The table only contains information about a relationship between other tables. A Many to Many Link needs at least 2 relationships to HUB & Satellite objects. - **Reference Table**: This object will become a reference table. - **Satellite**: For this table, only a satellite object will be generated in the Data Vault Model. This object needs a 1-to-1 relation to a Hub object. Or you need to set it as a multi-active SAT when it is a 1-N relation. - **Non-Historized Link**: (also known as a Transactional link) type of relation-based link, where data cannot be modified in the source system. A Non-Historized Link needs at least 2 relationships to HUB & Satellite objects. - **Same as Link**: A type of link that indicates the related objects have the same content. A Same as Link needs at least 2 relationships to HUB & Satellite objects. This is an alias of the Many to Many Link with Satellite. - **Hierarchical Link**: A type of link that defines a parent-child relationship. A Hierarchical Link needs at least 2 relationships to HUB & Satellite objects. This is an alias of the Many to Many Link with Satellite. - **Incremental Load using Modification Flag & Date: **The Source System records INSERTs, UPDATEs, and DELETEs applied to source objects and makes a record available in simple relational Change Tables of what changed and when the change happened. - **Incremental Load using Modification Date**: source objects contain a column that is a date & timestamp on which the record was created and/or updated. The dataset is an incremental dataset, meaning we can’t do delete detection. - **Incremental Load using Modification Sequence**: The source system delivers changes with a sequence number indicating the order of the changes. The dataset that is delivered to VaultSpeed is an incremental set, meaning we can’t do delete detection. You should always use this option together with the CDC_BASED_LOADING_WINDOW parameter. More info on CDC-based loading windows can be found here: [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081633856](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081633856). - **Incremental Load: **The source system does not indicate when a record was created, updated, or deleted but incrementally delivers data. VaultSpeed will detect all new/updated records, but this makes it impossible to do delete detection. - **Full Load using Modification Date with Delete Management: **source objects contain a column that is a date & timestamp on which the record was created and/or updated. The dataset is always the full dataset. VaultSpeed will handle the delete management for you. - **Full Load using Modification Sequence with Delete Management: **The source system delivers changes with a sequence number indicating the order of the changes. The dataset that is delivered to VaultSpeed is always the full dataset. You should always use this option together with the CDC_BASED_LOADING_WINDOW parameter. More info on CDC-based loading windows can be found here: [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081633856](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3081633856). - **Full Load**: The source system does not indicate when a record was created and/or updated. VaultSpeed will detect all changes. - **Comments**: Add a comment for this table. - **Multi-Active**: Can more than one valid entry in the Satellite be assigned to a Business Key in the Hub for a certain Point-in-Time? (In the Data Vault Standard this is called a Multi-Active Satellite). - **Ignored:** These objects will not be used during data vault builds. - **Ignore reason:** The reason why an object is ignored, mandatory when the ignored flag is on. # Object Parameters Below the object properties in the properties pane, several parameters can be changed at the object level See [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3012755470](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3012755470) for more details on Parameters. > 📝 **Note:** When configuring a "Satellite" object, please be aware: > 📝 > 📝 - The parameter `STORE_BK_FIELDS_IN_SAT` is currently not supported. This means the business key will not be included in the resulting satellite object. You can use the search box at the top of the pane to find specific parameters. Remember to press the “Save” button to apply your changes. ![image](media://adf44b40-d1df-4bc5-a30e-85b1f96260b1) # Toggle Completion Status Once you have done all your modelling on a certain object, you can set the object to a status ‘completed'. This status is just a visual clue for yourself that you finished modelling it. It doesn’t lock the object or prevent any further modifications to it. To set an object to completed right-click in the header of the object and select the 'Toggle Completion Status' option. Once the status is set you will see a small check appear in both the header of the object and in the Selection window. # Signature Object Type Changes ## With Record Tracking Satellites When you change the **Signature Object Type** of an object that has a **Record Tracking Satellite (RTS)**, the following rules apply based on the **Target Signature Object Type**. **Record Tracking Satellite setting:** 1. **Objects that inherit the RTS setting:** - **Hub and Satellite**: The RTS setting is inherited from the parent object. - **Many-to-Many Link**: The RTS setting is inherited from the parent object. 2. **Objects where the RTS setting is automatically set to "N":** - **Satellite**: The RTS setting is automatically set to "N." - **Reference Table**: The RTS setting is automatically set to "N." - **Non-Historical Link**: The RTS setting is automatically set to "N." #### Examples - If the initial object is a **Hub and Satellite**, and it is changed to a **Non-Historical Link**, the **RTS** setting is automatically set to **N**. - If the initial object is a **Many-to-Many Link** with the **RTS** setting set to **Y**, and it is changed to a **Hub and Satellite**, the RTS setting is inherited and remains **Y**. > 📝 **Note: These rules apply to both split and non-split objects.** Modifying the Object type can impact the inheritance of certain settings, such as the Record Tracking Satellite (RTS).. For example, changing a **Hub **or **Satellite **to a **Reference Table** or **Non-Historical Link** will automatically set the Record Tracking Satellite to "**N**".