- 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
-
+ 12...
-
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: Hour-integration (actual hours)
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
- Importing actual hours for personnel between the given timespan.
Integration's data fields
col. A |
B |
C |
D |
E |
F |
Username |
Date (YYYY-MM-DD) |
Task name (optional) |
Project's Code |
Hours (for example 4,5) |
Note (optional) |
The example file in the screenshot will integrate / create the following:
1) 4,5 hours for project [RS]Bridge 2 with a note "Documentation" for user whose username is 'olivia.hall_91'
2) Row 2 will be skipped because no such project code is found in Silverbucket as "RS 23". Before re-integrating the file, a project with such Project Code should be created first.
2) Row 2 will be skipped because no such project code is found in Silverbucket as "RS 23". Before re-integrating the file, a project with such Project Code should be created first.
Rules & basic principles of this integration
- Silverbucket matches rows to Silverbucket's usernames case-sensitively ("SilverBucket_Support" is not considered the same as "silverbucket_support")
If the data structure was correct, you can see the outcome in Silverbucket right after the upload. You can check this by using the User Report that tracks actual hours, for example.
How did we do with this article?