SYNC: Extended-projects
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
- Projects with extended metadata
All the metadata added can be found from the added Project's Dashboard afterwards. The metadata can be used to filter your projects in various manners in Silverbucket and with this integration you can add a multitude of projects at once with the correct information. Outcome can be seen in the Projects > Listing and on every projects' dashboard by checking the project's metadata.
Integration's data fields
Name of the project
Project's project manager's e-mail
Project's customer's name
Project's start date
Project's end date
Project's code
Is the project invoicable? Y/N
Probability of the project (0-100)
Code of the project's organizationNode
Name of the project's organizationNode
Budgeted hours for the project
Budgeted currency for the project
Description for the project
Is the project an absence project? Y/N
Portfolio 1
Portfolio 2
Portfolio 3
Portfolio 4
Portfolio 5
The example file in the screenshot will integrate / create the following:
1) A project called 'Construction' with the following metadata:
Project manager = const@building.com (this user will be created as the file is imported, as identical email can't be found from the system)
Customer = City of Vaasa
Start date = 25th of April, 2020
End date = 31st of December, 2020
Project's code = CON
Project type = Invoiceable (column G = 'Yes')
Project's probability = 100%
Organization = [VA]VAASA_1
Budgeted hours = 2000h
Budgeted currency = 800 000€ (based on your system's default currency)
Project desc. = "Let's build a house"
2) A project called 'Internal Work' with the following metadata:
Project manager = Boss Supervisor (match found from the system with the e-mail 'boss@email.com)
Customer = Internal
Start date = 1st of January, 2020
Project's code = INT
Project type = Non-invoiceable (column G = 'No')
Project's probability = 100%
Organization = [INT]INTERNAL
Project desc. = "Only internal work!"
Row 4 will be skipped; project name is a mandatory field. Fill in the name for the project in order to import it.
Rules & basic principles of this integration
Silverbucket matches rows to Silverbucket's data case-sensitively ("SilverBucket_Support" is not considered the same as "silverbucket_support").
However, matching email fields is done case-insensitively (" Support@Silverbucket.Com " is considered the same as " support@silverbucket.com " when creating a user, for example)
- Existing projects are matched by 1) project's extra code 2) project's code 3) project's name
A) If a match is found the existing project will be updated with that row's corresponding information
B) If no match is found from Silverbucket, a new project will be created with the row's information:
- Project Managers are matched to personnel by email (projectlead:email)
- Project manager will be created with the added email (projectlead:email) if no match is found
- Customer will be created if no match is found. Customer are matched with name, has to be identical with the existing one (customer:name)
- Organization is matched with code & name. If missing, the organization will be created
If the data structure was correct, you can see the outcome in Silverbucket right after the upload. You can check this by navigating to a Project's Dashboard, for example:
silverbucket_extended_projects_import.csv
359Bytes, Uploaded 8 months ago
silverbucket_extended_projects_import_exampleRow.csv
524Bytes, Uploaded 8 months ago