In Business Central
In Microsoft Dynamics 365 Business Central, a product of Microsoft, the connector appears as an extension called Clockify Connector. It takes in approved time from Clockify, a product of CAKE.com, and shows what became of it. Spainlink built it, and neither company did.
Your team sees two things: the page in Clockify, for following approved time and editing the mapping, and the Business Central role center, for working with the entries themselves and for setup.
Clockify roles do not apply to the pages below. Your Business Central administrator gives people access by assigning them the Clockify Connector permission set.
The role center
Clockify Connector adds two parts to the end of the Business Manager and Project Manager role centers: Clockify Time Sync, with the tiles, and Clockify Time, with the charts. On any other role center, search for the pages below by name.
The tiles are the same four as on the page in Clockify, where each one is explained, plus Needs Review and Posted Hours.
| Tile | Choosing it opens |
|---|---|
| Received, In Journal, Posted | Clockify Time Entries, filtered to that status |
| Failed | Clockify Time Entries, filtered to Failed, with the Error Message column showing |
| Needs Review | Clockify Time Entries, showing the entries flagged for review, with their Review Reason. See Corrections |
| Posted Hours | Clockify Posted Time, the posted project ledger entries that came from Clockify. The hours on the tile are read from those entries |
Clockify Time Sync also has four actions: All Time Entries, Posted Time, Sync Log and Setup.
Charts
The Clockify Time chart shows posted entries from the last twelve months, and its actions switch between four views.
| View | What it shows |
|---|---|
| Hours by User | Posted hours per Clockify user |
| Hours by Project | Posted hours per Business Central project |
| Hours by Clockify Project | Posted hours per Clockify project, in the names your workspace uses. Several Clockify projects can map to one Business Central project |
| Amount by Project | Posted cost and price per project, read from the project ledger entries that came from Clockify. The connector sends cost and no prices: see the cost rule |
The time entries list
Clockify Time Entries has one row for every entry that reached Business Central: who tracked it, the project and task on both sides, the hours, the status and the posted amounts. A skipped entry is not here, because it never reached Business Central.
The status reads Received, Written To Journal, Posted or Failed. Written To Journal is what the In Journal tile counts.
A failed entry shows why it failed. Opened from the Failed tile, the list adds an Error Message column. From anywhere else, open the row: the reason is on its card, Clockify Time Entry.
Select a row to use these actions.
| Action | What it does |
|---|---|
| Sync Log | Shows everything the connector did with the selected entry |
| Retry | Puts the selected failed entries back in line for the next sync and clears their error |
| Posted Entry | Opens the posted project ledger entries that carry the selected entry |
| Mark Reviewed | Clears the review flag on the selected entries, once someone has looked at the change |
A failed entry is not tried again by itself. Fix the cause, then use Retry. If the mapping was the cause, correct the row’s card first: a corrected mapping only applies to entries that have not reached Business Central yet. Then check the entry’s Sync Log. After Write Failed, use Retry, which sends the entry as its row holds it. After Post Failed the journal line still exists, and Retry would post that line as it stands, so delete the line from the project journal instead. The next sync whose window still reaches the entry writes it again from its row, as long as its timesheet is still approved. For time that has already posted, see Corrections.
The sync log
Clockify Sync Log records every action the connector took in your Business Central, with timestamps, newest first. Open it from the role center for the whole log, or with Sync Log on the time entries list for one entry’s history. It is append-only.
| Event | What happened |
|---|---|
| Written To Journal | A project journal line was created for the entry |
| Journal Line Updated | That line was changed before it posted |
| Posted | The line was posted, and the row carries the project ledger entry number |
| Journal Line Deleted | The line was deleted before it posted, and the next sync writes the entry again |
| Staging Row Deleted | The entry’s row was removed from Clockify Time Entries. A posted ledger entry is not affected |
| Write Failed, Post Failed | Business Central refused to write or post the entry. The reason is on the time entries list |
| Modified After Sync | The entry changed in Clockify after it posted, and is flagged for review |
| Deleted In Clockify | The entry was deleted in Clockify after it posted, and is flagged for review |
| Marked As Reviewed | A person cleared the review flag with Mark Reviewed |
A normal entry appears twice: Written To Journal, then Posted.
The setup page
Clockify Connector Setup is where you check the connection. Open it with Setup on the role center. It also holds Project Journal Template, Project Journal Batch, Default Work Type Code and Default Line Type, and its Posting Date Checks action lists the connector’s recent date checks.
- Connection Status reads “Ready” once the setup is filled in. “Ready” does not show that the connection works.
- Test Middleware Connection is the real check. It calls the add-on service from your Business Central and shows the answer. HTTP status 200 means your Business Central reached the service. The result does not affect posting.
- Allow HttpClient Requests matters in a Business Central sandbox, which blocks outside calls until this setting is on. Test Middleware Connection fails until then, ending with “The request could not be sent.” To turn it on, open Extension Management, choose the name Clockify Connector to open Extension Settings, and switch it on there.