SYNC: Organizationnodes

When importing data to Silverbucket it is vital to keep the structure identical to the example datasheet to ensure a flawless import:

- First row contains the names of the headers - it is not necessary to edit the first row.
- Second row in your file is where your data starts to get imported
- Columns need to be in the same exact order as in the examples
- Rows after the default structure's last column are never read / handled when importing
- Never have hidden columns in your data sheets

What data is this integration used for
- Organization nodes

After import you can find the integrated data in the admin view's Organizations tab. Organization is metadata for people and projects in Silverbucket.

Integration's data fields
col. A
B
C
Code for the organization
Name of the organization
ParentOrganization's Code

The example file in the screenshot will integrate / create the following:

https://slite.com/api/files/BHHoITDJzuWyCQ/image.png?apiToken=eyJhbGciOiJIUzI1NiIsImtpZCI6IjIwMjMtMDUtMDQifQ.eyJzY29wZSI6Im5vdGUtZXhwb3J0IiwibmlkIjoiZ0NzWjZmSDUwdGtOVGMiLCJpYXQiOjE3MzIxOTYxMjYsImlzcyI6Imh0dHBzOi8vc2xpdGUuY29tIiwianRpIjoicldyZDhHOTl4QlVyTzkiLCJleHAiOjE3MzQ3ODgxMjZ9.2GZF7_zOUPq_oaMyQ6p2QBVLZRp2lV1v3CqKNmbu4YE

1) An organization with a code of "FIN" named "Finland"
2) An organization with a code of "HEL-1", named "Helsinki 1" under the parent organization "FIN"
3) An organization with a code of "TAM-1", named "Tampere 1" under the parent organization "FIN"

Rules & basic principles of this integration
- Parent Organizations need to be created before Child Organizations - make sure to run your integration twice if a Parent Organization is located later in the data than its descendant

- Code and name (first two columns) are mandatory

- ParentOrganization is optional

- ParentOrganization is identified with organization's code

- If an organizationNode is already in the system with different code but same name, a new organizationNode will be created

- If an organizationNode is set as passive in the system and an organizationNode with identical information (same code, same name) is brought in the data: nothing happens and the pre-existing orgNode stays as passive in the system

If the data structure was correct, you can see the outcome in Silverbucket right after the upload. Navigate to the admin-view and its 'Organizations' tab, for example:

https://slite.com/api/files/wyH8Ff4AZ0ZJ7i/image.png?apiToken=eyJhbGciOiJIUzI1NiIsImtpZCI6IjIwMjMtMDUtMDQifQ.eyJzY29wZSI6Im5vdGUtZXhwb3J0IiwibmlkIjoiZ0NzWjZmSDUwdGtOVGMiLCJpYXQiOjE3MzIxOTYxMjYsImlzcyI6Imh0dHBzOi8vc2xpdGUuY29tIiwianRpIjoicldyZDhHOTl4QlVyTzkiLCJleHAiOjE3MzQ3ODgxMjZ9.2GZF7_zOUPq_oaMyQ6p2QBVLZRp2lV1v3CqKNmbu4YE


organizationNodes_import.csv
70Bytes, Uploaded 8 months ago

organizationNodes_import_exampleRow.csv
95Bytes, Uploaded 8 months ago