User menu
Individual settings for each user are opened via the user menu. It is located at the level of the heading, to the right above the respective workspace. The settings in this area only affect the user who made them.
The menu shows information such as name, email and the Business Central instance for the logged-in user. The user can explicitly log out here, switch companies and enter the user settings.
Switch companies
To change the company, the user must be created in the other company. Time recordings, templates and the users themselves are company-specific. Therefore, time recordings and templates from one company are not visible in other companies.
Settings
The user settings are divided into a General part and a part specifically for Time Tracking.
General
Settings on the General page control how the entire app is displayed to the user.
-
**Language and region
The Language and Region is taken from the browser when the user first logs in. Each user can change the language and region in the Settings. The region effects the date and time format. English and German languages are available. If a language other than German is stored in the browser, English will be defaulted to. Some browsers allow setting a language but no region. In Chrome, for example, German or German/Germany can be selected in the languages settings. If no region is stored or cannot be recognized, United States will be selected automatically. -
Dark mode
If the Dark Mode is activated, the complete app is displayed in eye-friendly colors. Dark Mode can be activated and deactivated via the Mode toggle. -
Consent to the use of user data and data traffic
In order to provide optimal support and to continuously improve DYCE Connect, we record user data and data traffic. Consent can be given via the cookie banner and in the setup. If no consent is given, no data is recorded. No errors either.
Time tracking
Settings in the Time Tracking page only affect the display of the Time Tracking area.
- Selection of Time Tracking form
Different time recording masks can be selected to use for creating time recordings. All masks work basically in the same way, they only differ regarding the fields displayed. The following time recording masks can be selected: - All
In this mask all fields are displayed. This time recording mask is used as default when the time recording is opened for the first time. - Compact
In this mask the fields Start, End and Break are not displayed. - Simple
In this mask the fields Start, End, Break and Customer are not displayed. - Dynamic
This mask is one of the masks used in Azure DevOps. All fields are displayed in this mask.
The preview below the selection shows the selected mask. Changing the Time Tracking Form changes the display on the Recordings, Incomplete and Templates page.
-
Export
Time Recordings are automatically synchronized in Business Central. Time Recordings can also be exported using the Export function. Only the time recordings of the user performing the export are exported. The exported Time Recordings are provided as JSON. -
Show days without capacity
The Show days without capacity button controls which days are displayed in time recordings and the dashboard. Depending on the setting, all days or only working days are displayed. By default, only working days are preset according to the working time model and base calendar. -
Calendar settings
Before you can see your Outlook calendar entries, you must grant read permission once. The read permission can be revoked at https://myapps.microsoft.com/. Find the DYCE app, click on the three dots, select Manage your application and then Revoke Access.
Miscellaneous
-
Task Grouping
The grouping of tasks is defined here. Each user can choose between grouping by Customer, Project (default), Start date and End date. -
URL
Information on the app, page, environment, company and tag can be encoded in the URL.
| Component | Example URL | Comment |
|---|---|---|
| Base URL | https://app.dyce.cloud/ | Opens the selection of apps. If the user only has access to one app, they are automatically redirected to this app. |
| App | https://app.dyce.cloud/timetracking | Opens the Time Tracking app in the last used environment and company. |
| Page | https://app.dyce.cloud/timetracking/dailyrecordings | Opens the page Time Recordings (dailyrecordings) on the current day and last used environment and company. |
| Dailyrecordings | https://app.dyce.cloud/timetracking/dailyrecordings#2024-04-12 | Opens the Time Recordings on 12.04.2024. The filter #2024-04-12 only works on the page Time Recordings. |
| Environment | https://app.dyce.cloud/timetracking/dailyrecordings?instance=demo#2024-04-12 | Opens Time Recordings on 12.04.2024 in the Demo environment (?instance=demo). |
| Company | https://app.dyce.cloud/timetracking/dailyrecordings?instance=demo&company=Intern#2024-04-12 | Opens the Time Recordings on 12.04.2024 in the company Intern (?instance=demo&company=intern). |
| Tenant | https://app.dyce.cloud/?tenant=customer.onmicrosoft.com | Signs a B2B guest user in against a specific tenant. See Guest login for external tenants. |
instance and company select the environment and company the app opens in. Specify both to open a specific workspace. Either may be left out when it is unambiguous: company alone is enough when the user has access to only one environment, and instance alone is enough when that environment contains only one company. If the environment or company still cannot be resolved, or the user has no access to it, the app falls back to its usual behavior: the last used environment and company, otherwise the selection screen, or the only available one when there is just one.
Special characters that represent invalid characters in a URL must be encoded. For example, blanks must be replaced by %20.
Pre-fill a new time recording via URL
An external system, for example a ticket tool, can open DYCE Time Tracking on a new time recording that is already pre-filled with the data known in the source system. The user only completes the remaining fields and saves, which keeps manual data entry to a minimum.
To request a pre-filled form, open the Time Recordings page with newRecord=true and at least one of the parameters below, for example:
https://app.dyce.cloud/timetracking/dailyrecordings?newRecord=true&jobId=<id>&duration=60&description=Kickoff%20call
newRecord=true on its own opens the normal empty new-record form.
| Parameter | Description |
|---|---|
newRecord=true | Requests the pre-filled form. Must be set to true, together with at least one of the parameters below. |
instance | Business Central environment (as in the URL table above). |
company | Company within the environment. |
date | Date of the time recording as an ISO date (YYYY-MM-DD). Takes precedence over a #YYYY-MM-DD hash. Can be omitted when start (or end) already includes the date. |
start | Start time as a full ISO date and time. |
end | End time as a full ISO date and time. |
duration | Duration in minutes. |
durationBillable | Billable duration in minutes. |
break | Break in minutes. |
description | Free-text description. |
customerId | Customer id. |
jobId | Project id. |
jobTaskId | Project Task id. |
jobPlanningLineId | Project Planning Line id. |
tntModelLineId | Time & Travel Model Line id; the matching activity is selected accordingly. |
workOrderId | Work Order id; its customer and project are taken over into the time recording. |
nonBillableReason | Non-billable reason. Applied only when it matches a valid value. |
Each id is the record's System Id (a GUID), the same identifier the record has in Business Central. If the parameters contradict each other (for example a customer and a project that do not belong together), the higher-level field wins and the lower-level field is left blank. As above, special characters must be URL-encoded, for example a blank as %20.
Start and end times
start and end are ISO 8601 date and time values and can be passed in two ways:
- Without a time-zone offset (simplest): the time is interpreted in the user's local time zone, for example
start=2026-09-22T14:00:00. - With an explicit offset: the
+must be encoded as %2B, otherwise it is read as a space and the offset is lost, for examplestart=2026-09-22T14:00:00%2B02:00for UTC+02:00.