5/28/2026
Due to past UI technology changes, certain hidden fields were unintentionally exposed. These fields were not intended for client use. Addressing this issue requires broader remediation beyond a simple defect fix and has been added to our product backlog for further assessment and requirements gathering. Archer recommends that clients who have utilized hidden fields review their internal processes and discontinue usage in preparation for upcoming product updates.
There will be no product changes in 2026.06 related to this issue.
4/14/2026 The Archer team apologizes for the delay in providing an update. Our internal investigation has identified additional information that requires further analysis. Before making any changes to the code in this area, we will complete that investigation and provide an update accordingly. In the interim, any cases, opened requesting execution of the previously provided script, will be closed.
3/27/2026 Add the following comment: Please see post for today's status update.
Archer is still investigating the data conditions that underlies the reported issue. Archer is removing the current script from this post until we complete this investigation. We will provide an updated script upon completion of testing. For OnPrem clients, a new script will be supplied in a future posting. For SaaS clients if you have an existing open case for the script to be run, the results will be automatically provided once the new script is available. If you have not contacted Technical Support on this issue, please wait until the new script is posted as available.
3/24/2026 Updated with comment:
Archer has identified an additional data point that will make the script outlined in this post more useful. An update script is in process of creation and testing. Please check back for an update on this Announcement. We appreciate your patience and understanding.
Hidden Subform Related Record Fields Used in Calculations May Cause Application Discrepancies
Applies To
Product(s): Archer Platform
Impacted Version(s): Prior to 2024.06 and later
Primary Deployment: SaaS and On-Premises
Summary
For a brief time, from Archer Platform version 6.12 through the 2024.06 release, Subform Related Record fields, which were designed to be hidden fields, were visible in the Data Fields list and displayed using GUID values. Some of these GUIDs had been used in calculated fields in the Subform records resulting in the exposure.
Change Details
Subform Related Record fields are intended to be hidden and should not be used in calculations. Starting with the 2024.06 release, these fields were removed from the UI to align with this intended behaviour. However, calculated fields that were previously configured using these related record fields continued to be evaluated in the background, even after the fields were no longer visible in the UI.
Beginning with the Archer Platform 2026.06 release, a change will be introduced to fully remove hidden Subform Related Record fields from the backend.
This change may impact applications where:
- Hidden related record fields were previously used in calculated fields
- Those calculated fields are still referenced in layouts or content
This could lead to content save issues or calculation discrepancies.
To mitigate this, a fix has been added, so content saves will not fail with an error due to these hidden calculated fields and will complete successfully. Because these fields could have been errantly used in client calculations, application behaviour and calculation results may be inconsistent.
Required Action
The following steps are designed to assist clients who think they might be impacted.
SaaS Clients
If possible, Archer recommends completing the following tasks prior to the upgrade of the production environments to Archer Platform version 2026.06 planned for late June.
1. Contact Archer Technical Support to submit and ASR to obtain discovery script results.
2. Review the SQL results to identify affected calculated fields.
- Update calculation formulas to remove any dependency on hidden Subform Related Record fields.
- Modify application layouts to ensure these fields are no longer referenced.
- Validate calculations after remediation to ensure expected behaviour.
After the SaaS environment upgrades in June, validate calculations are behaving as expected.
On-Premises Clients
Archer recommends completing the following tasks before upgrading your production environment to Archer Platform LTS version 2026.12 or later post December 2026.
1. Make a database back-up.
2. Identify Affected Calculated Fields using the script outlined below.
3. Run the discovery script against your Archer instance database.
- Review the SQL results to identify affected calculated fields.
- Update calculation formulas to remove any dependency on hidden Subform Related Record fields.
- Modify application layouts to ensure these fields are no longer referenced.
- Validate calculations after remediation to ensure expected behaviour.
The content in this document is believed to be accurate at the time of publication. This content may change at any time without notice.
Originally posted on March 23, 2026 in the Archer Community.
Comments
4 comments
Archer has identified an additional data point that will make the script outlined in this post more useful. An update script is in process of creation and testing. Please check back for an update on this Announcement. We appreciate your patience and understanding.
Originally posted on March 24, 2026.
Will these hidden related records fields still be accessible via the API?
Originally posted on March 25, 2026.
Please see post for today's status update.
Originally posted on March 27, 2026.
Please see post for today's status update.
Originally posted on April 14, 2026.
Please sign in to leave a comment.