When and Where to Paste Merge Data – Orgvue Knowledgebase

When would you paste merge in Settings vs Workspace?

The following Use Case examples and Merge Rules in Settings and Workspace will get you started on when it is best to paste merge in Settings or in Workspace.

Items you'll need:

1. Source data file. The file that contains new/updated data.

2. Target dataset in Orgvue. This is where your updates will be applied.

Use Case 1: Update Existing Nodes

If you find that you need to update existing property or properties for existing nodes, you can do this in both Settings and Workspace.

In Settings, the following is required:

1. You will need a new file with the Auto ID and the associated properties with changed values.

a. Make sure to include the following fields/properties on your csv/excel file upload:

i. AutoID (designated on the Dataset in Settings)
ii. Property Key for the values you are changing which is designated in the Dataset's metadata screen.

Example: Lets say for example, in a Positions Dataset, one of the roles need to be changed/corrected. The property is role and the property value is “Allocations Solution Architect ÃÂ¢ÃÂÃÂ Summit Project”. Let's change the role value to "Allocations Solution Architect ACA Summit Project".

On the original source file, I went to the node with the role change and changed the value. Merged the updated file using the Merge Operation "Merge", so all the other nodes and properties will remain intact, but will update the nodes you specified in your file.

To check that the Merge was successful you can do two things, you can download the dataset from Settings and see if the corrected update is there and you can open up a Pack in Workspace to see this change as well.

Example:

b. You can also paste merge in new properties if they don't already exist in the dataset.

i. Include the new properties in the file being paste merged.

Follow the steps below to guide you through updating the data in the selected dataset or Links dataset in five steps:

1. Select a file
2. Edit Details
3. Configure Properties
4. Node Review
5. Summary

Use Case 2: Add New Nodes

Adding new nodes to a dataset, using new spreadsheet/upload file.

In Settings, the following is required:

1. You will need a new file with the Auto ID and the associated properties with changed values.

2. While it is possible to merge data and update properties for existing nodes using a matching property present in both the source and target data, to merge data and add new nodes the ID property column must be present in the source data

The Id property for any new nodes may be left blank in the source data as long as the column header is present and Orgvue will assign an autoID which can be amended later in workspace if required

Example: Let’s add three new roles as placeholder Roles.

If you have upcoming new Roles/nodes to add as a placeholder where you're awaiting confirmation of all the rest of the data for existing properties, you can Merge new nodes into a Dataset.
Include the AutoID: position_id, and whatever other properties you are updating.
Add the three new placeholder roles without manager IDs and only have data for some properties, not all.
Example: The Positions dataset in this example has 6,859 nodes prior to adding these three (3) Placeholder Roles. Once the Paste Merge is complete using Merge Operation: Merge, the total number of nodes that will appear in the dataset's summary page is 6,862.

If you don't know what the Manager ID is yet, you can leave them blank on your source file to upload/merge. However, be sure to include those as column headers in your merge file.
You can then add those Manager IDs for those new nodes in Workspace by opening a pack, focusing on the new nodes in a Worksheet slide and then enter in their Manager IDs.
- Example:

The following Table will help guide what can be done in Settings vs Workspace when it comes to Paste Merging:

Merge Rules: Settings vs Workspace
Use Cases/Paste Merge Operations	Settings	Workspace
1. Update data for existing properties and nodes for stand alone datasets (i.e., unlinked datasets, People/Positions/Roles/Activities, etc.)	Can be performed here. Requirements: • AutoID • Property or properties with new data	Can be performed here Requirements: • Property to Merge On • Property or properties with new data
2. Update data for existing properties and nodes for linked datasets.	Can be performed here. Requirements: • Upload files for paste merge process must contain the from_id, to_id properties at minimum • The merge process will recalculate the link_id based on the from_id & to_id and will only update the allocation and any other property values from the upload file where the link_id is the same • If you paste merge from_id and to_id with no specified allocation, Orgvue will create an allocation and will set the link allocation to one (1). • Unless the Replace option is chosen any from_id, to_id links that are not present in the upload file will be preserved	Paste merging to links datasets cannot be performed.
3. Adding New Properties to standalone Datasets	Can be performed here. To add a new property follow the steps detailed in Merge or Replace Dataset via Settings.	Paste Merge in Workspace will only update values in existing properties, you cannot create a new property using this method.
4. Add New Nodes for Existing Properties	Can be performed here.	Can be performed here.
5. Paste Merging Dates	Can be performed here. When paste merging data that includes dates, Orgvue will recognize the following date formats: ISO format (YYYY-MM-DD) US format (MM/DD/YYYY) UK format (DD/MM/YYYY) Note: Orgvue automatically detects which of the US/UK date formats to use based upon the user's locale as reported by the browser.	Can be performed here. Same as in Settings.
6. Merge on Matching Properties	In Settings, you are required to have at least the property key of the target dataset's AutoID in the source data file that is being paste merged.	Workspace will allow you to merge on a property using either the Property Key or Display Name For example the property containing the unique ID of your Nodes may have the Property Key: unique_id but the Display Name: Position Number Workspace will recognize and merge on either This applies to any property you are merging on or any target properties you are updating
7. Paste Merge on Fuzzy matching	In Settings, if the column header isn't clear, it will not paste merge.	Workspace will try its best to match a property and will ignore the formatting of the column headers that you paste in For example if you paste in the column header DeP_art ment Workspace will match this to the property with the Display Name Department

Merge Operations:

Merge Operations Explained:
Merge	This option will merge the uploaded data into the target dataset, preserving all other unchanged data. Example: Changing/updating an existing node/property value.
Merge & Delete	This option will merge the uploaded data into the target dataset and will delete any rows in the target dataset that are not in the uploaded data. All properties are preserved. This process will only delete rows in the target dataset not in the uploaded data that have unique IDs. It will not delete any duplicate rows. Example: Uploading a different source file that has less rows than what is in the dataset. The merge will only keep the new file’s rows and columns, removing what is no longer useful in the existing dataset.
Merge/Replace	This final option replaces all data in the target dataset with the uploaded data, deleting rows and columns (properties) that are not in the uploaded data. Example: Uploading a different source file that has more rows than what is in the existing dataset. Upon merging, only the rows and columns that exist in the new upload file will merge.