Update 28.1.2644.975 Published October 30, 2026
Periodically, Sparkrock may publish updates between major releases. All updates are cumulative.
Highlights
The following sections highlight the major accomplishments in this update.
Finance and Procurement
HR Management
Problems that are resolved in this update
The following problems are resolved in this update.
Finance and Procurement
| Description | |
|---|---|
| When Retain PI Line Field Values is turned on in Purchases & Payables Setup, and you change the G/L Account on a purchase invoice line, Sparkrock Impact clears the Details field on the line. As a result, the posted invoice line does not include the details text, unless you enter the text again before you post the invoice. |
|
| When a Business Central update is applied to an environment that has a large number of vendors and purchase documents, the update may take an excessive time to complete, or may not complete at all. This problem occurs when the update is populating the buy-from vendor posting group on existing purchase documents. |
|
| In mySparkrock, when you try to add a line to a purchase requisition right after saving the document, the line may not be added, and no error message displays. This problem occurs because requisition type data is not shared properly between mySparkrock and Sparkrock Impact. |
|
| When a financial document approval workflow has an approval level with more than one approver and no default approver, and one of the approvers is also an approver on a higher approval level, Sparkrock Impact automatically approves the higher approval level after another approver approves the lower level. As a result, the document is approved without the approver for the higher level taking action. |
|
| When lines are generated from an allocation account line on a purchase document or sales document, the generated lines do not include the text from the Details field of the allocation account line. This problem also occurs when the document is posted. |
HR Management
| Description | |
|---|---|
| On the Trakstar Perform Setup page, when you select Test Connection for a correctly configured tenant on the Canadian Trakstar Perform host, Sparkrock Impact displays the following message, which does not explain the reason: Test Connection failed (403). As a result, the integration cannot get a token to synchronize. To resolve this problem, Test Connection now succeeds for a correctly configured tenant, and when a test fails, Sparkrock Impact displays the reason that Trakstar Perform returns. In addition, when the Trakstar Base URL field includes a trailing slash or a path, the connection may fail. To resolve this slash or path problem, Sparkrock Impact now removes a trailing slash, and displays the following error when you enter a value that includes a path: Enter the Trakstar Perform host without a path, for example https://perform.trakstar.com. The /api/v1/... part is added automatically. |
Related information
New for Sparkrock Impact
Finance and Procurement updates
HR Management updates
Version 28.1 for Sparkrock Impact 2026 release wave 1 release notes
Feedback
To send feedback about this page, select the following link: