Maintenance update 26.1.2534.283 Published August 22, 2025

Periodically, Sparkrock may publish maintenance updates between releases. This maintenance update replaces previously released updates. All maintenance updates are cumulative.

Problems that are resolved in this maintenance update

The following problems are resolved in this maintenance update.

Platform

Case Number	Description
Not applicable	On the mySparkrock Solution Setup page, the Enable use of Finance pages field label does not clearly indicate that the field controls whether purchase and payment pages are available for configuration. To improve clarity, the field must be renamed to Purchase and Payments Pages.PD-7053

Finance and Procurement

Case Number	Description
131949	When renaming a Location Code, Sparkrock 365 displays the following error message: Status must be equal to 'Open' in Purchase Request Header: No.=REQ00016, Type=Purchase. Current value is 'Completed'. Sparkrock 365 requires changes to prevent this error and ensure that all related records are updated correctly when a Location Code is renamed.PD-7046
131274	Sparkrock 365 incorrectly prevents you from turning on Blocked on the Fixed Asset Card page after a purchase credit memo is posted to the fixed asset ledger. Blocking must only be prevented when there is an unposted purchase line that includes the fixed asset.PD-6978

Case Number

Description

131949

When renaming a Location Code, Sparkrock 365 displays the following error message:

Status must be equal to 'Open' in Purchase Request Header: No.=REQ00016, Type=Purchase. Current value is 'Completed'.

Sparkrock 365 requires changes to prevent this error and ensure that all related records are updated correctly when a Location Code is renamed.PD-7046

131274

Sparkrock 365 incorrectly prevents you from turning on Blocked on the Fixed Asset Card page after a purchase credit memo is posted to the fixed asset ledger. Blocking must only be prevented when there is an unposted purchase line that includes the fixed asset.PD-6978

HR Management

Case Number	Description
127933	When creating a Record of Employment (ROE), Sparkrock 365 is populating an incorrect First Date Worked in the following scenario: An employee is hired. At least one payroll is processed. A transfer or progression HR request is processed for that employee. At least one payroll is processed. A leave HR request is processed for that employee with an effective date after the last payroll. In this case, Sparkrock 365 uses the Calculation Start Date from the transfer or progression HR request as the First Date Worked, instead of using the Calculation Start Date from the new hire HR request.PD-7087
Not applicable	On the Employee Attendance Plan page, when a balance is transferred to a new cause of absence code that isn't displayed, Sparkrock 365 does not automatically refresh the page to show the new line.PD-7054

Case Number

Description

127933

When creating a Record of Employment (ROE), Sparkrock 365 is populating an incorrect First Date Worked in the following scenario:

An employee is hired.
At least one payroll is processed.
A transfer or progression HR request is processed for that employee.
At least one payroll is processed.
A leave HR request is processed for that employee with an effective date after the last payroll.

In this case, Sparkrock 365 uses the Calculation Start Date from the transfer or progression HR request as the First Date Worked, instead of using the Calculation Start Date from the new hire HR request.PD-7087

Not applicable

On the Employee Attendance Plan page, when a balance is transferred to a new cause of absence code that isn't displayed, Sparkrock 365 does not automatically refresh the page to show the new line.PD-7054

New for Sparkrock ERP
Platform maintenance updates
Finance and procurement maintenance updates
HR management maintenance updates

Feedback

To send feedback about this page, select the following link:

feedback-product-docs@sparkrock.com