QuickBooks Time
QuickBooks Time is a web-based and mobile time tracking and employee scheduling app.
Data integration: Skyvia supports importing data to and from QuickBooks Time, exporting QuickBooks Time data to CSV files, replicating QuickBooks Time data to relational databases and synchronizing QuickBooks Time data with other cloud apps and relational databases.
Backup: Skyvia Backup does not support QuickBooks Time.
Query: Skyvia Query supports QuickBooks Time.
QuickBooks Time Specific Features and Limitations
Skyvia has the following limitations for QuickBooks Time:
-
In the Data Integration product, QuickBooks Time connections are supported only for packages, which use a new data integration runtime.
Make sure that the Use new runtime checkbox is selected on the tab bar if you want to use QuickBooks Time in your package.
- Skyvia supports DML operations for the following QuickBooks Time objects:
- INSERT, UPDATE, DELETE: Timesheets.
- INSERT, UPDATE: CustomFieldItems, CustomFields, Groups, Jobcodes, Locations, Reminders, ScheduleEvents, TimeOffRequestEntries, TimeOffRequests, Users.
- INSERT, DELETE: JobcodeAssignments, Notifications.
- INSERT: Geolocations.
- Skyvia supports Replication with Incremental Updates for most QuickBooks Time objects except EffectiveSettings, LastModifiedTimestamps.
- Skyvia supports Synchronization for such QuickBooks Time objects as CustomFieldItems, CustomFields, Groups, Jobcodes, Locations, Reminders, ScheduleEvents, Timesheets, TimeOffRequests, TimeOffRequestEntries, Users.
-
Timesheets object and its peculiarities. Since there are two types of timesheets (manual and regular) in the Timesheets object, each has its own required fields for import, and common required fields for both types.
In Skyvia’s metadata, common fields have a required attribute, but the fields, required depending on the type, are not defined as required. That is why you need to specify the required fields based on the timesheet type yourself; otherwise, you will receive an error when loading data to QuickBooks Time timesheets.
-
TimeOffRequests object and its peculiarities. When importing data to the TimeOffRequests object, provide values for the TimeOffRequestEntries field as JSON array, for example:
1 2 3 4 5 6 7 8 9 10 11
"time_off_request_entries": [{ "date": "2020-09-20", "entry_method": "manual", "duration": 28800, "jobcode_id": 4057357 }]
as well as values for the TimeOffRequestNotes field as such JSON array:
1
[{"note": "Taking a two day weekend to go on vacation."}]
-
Reminders object and its peculiarities. The data in the Reminders object is displayed by default with UserId=0.
To get information about reminders for other users, you can filter data by the UserIds field. This field is of the String type and, as a filter value for it, you can specify several user id values separated by commas (for example, 2886910,2886474,2886548).
When reading records of the Reminders object, the UserId field remains always empty since it is used only for filtering.
QuickBooks Time Connections
When creating a QuickBooks Time connection, you need to sign in to QuickBooks Time via OAuth 2.0. The OAuth authentication token is stored on the Skyvia server. Your QuickBooks Time account login and password are not stored on the Skyvia server.
To create an QuickBooks Time connection, perform the following steps:
- Click +NEW in the top menu.
- Click Connection in the menu on the left to open the Select Connector page.
- In the opened page, select QuickBooks Time.
-
In the Connection Editor page, specify a connection name that will be used to identify the connection.
- Click Sign In with QuickBooks Time.
- In the opened window, enter your email address and password used when registering in QuickBooks Time and click Continue.
- Skyvia will request permission to access your QuickBooks Time account. Click Allow.
- When everything is ready, use the Test Connection button to make sure that the connection is successful and then click Create Connection.
Supported Actions and Actions Specifics
QuickBooks Time connector supports the following actions:
- Execute Command in Source, Lookup, and Target components in Data Flow packages, in Source in Export packages.
- Execute Query in Source in Data Flow and Export packages.
- Lookup in Lookup Data Flow components.
- Insert in Target Data Flow components.
- Update in Target Data Flow components.
- Delete in Target Data Flow components.