- People
-
Projects
- Projects > Listing & Projects > Allocations
- Project's Dashboard
- Project's Basic Information
- Project Numbers table
- Projects > Allocations Main Graph
- Progress Numbers
- Actions (Project's Dashboard)
- Membership Actions (Project's Dashboard)
- Project's Resourcing View
- Grouping in Project's Dashboard
-
+ 13...
-
Resourcing
- Resourcing with 'Quick Edit'
- Resourcing with 'Grid View'
- Finding and Resourcing the Available & Suitable People for Your Projects
- Soft Booking
- Use Cases for Soft Booking
- Resourcing Log
- Allocation Notes
- Resourcing Requests
- In-Depth: Getting an Overview / Utilization Rate of a Specific Target
- In-Depth: Using the Utilization Range in Person Filters
-
+ 2...
- Reports
- Timesheet
- Competencies
- Resourcing Intelligence
-
SYNC View (admins of Silverbucket)
- Integrating Data with with Silverbucket's SYNC-view
- SYNC-View: Competency
- SYNC-View: Customers
- SYNC-View: Extended-customers
- SYNC-View: People
- SYNC-View: Extended-people
- SYNC-View: Projects
- SYNC-View: Extended-projects
- SYNC-View: Hour-integration (actual hours)
- SYNC-View: OrganizationNodes-integration
SYNC-View: 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
- 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 simple metadata
The outcome of this import can be seen in the Projects > Listing view, for example.
Integration's data fields
col. A |
B |
C |
D |
E |
F |
Project's name |
Project manager's e-mail |
Project's customer's name |
Start date (format: YYYY-MM-DD)
|
End date (format: YYYY-MM-DD)
|
Project's code |
The example file in the screenshot will integrate / create the following:
1) A project called 'Support Project' with the following metadata:
Project Manager = freshUser@email.com (this user wasn't yet added to Silverbucket before the import, so the user will be created with email "freshUser@email.com")
Project's customer = City of Helsinki
Project's start date = 15th of February, 2020
Project's code = 'SP'
2) A project called 'Maintenance' with the following metadata:
Project Manager = Adam Adamson (matched by the email adam@email.com)
Project end date = 30th June, 2020
Code = 'MTNC'
Row 4 will be skipped; project name is a mandatory field. Fill in the name for the project in order to import it.
Project Manager = freshUser@email.com (this user wasn't yet added to Silverbucket before the import, so the user will be created with email "freshUser@email.com")
Project's customer = City of Helsinki
Project's start date = 15th of February, 2020
Project's code = 'SP'
2) A project called 'Maintenance' with the following metadata:
Project Manager = Adam Adamson (matched by the email adam@email.com)
Project end date = 30th June, 2020
Code = 'MTNC'
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)
How did we do with this article?