Hello,
I’m currently using SQLcl Projects version 24.4.1 and have encountered an issue when deploying an APEX application.
Description:
- My APEX app is deployed to a test workspace that has a different workspace name and app ID.
- The initial deployment completed successfully without any issues.
- After adding a new page to the application, I created a new release and attempted to deploy it again using SQLcl Projects. However, I encountered the following error:
ERROR: Exception Details
ERROR: Exception Primary Class: ValidationFailedException
ERROR: Exception Primary Reason: Validation Failed:
1 changesets check sum
releases/apex/f106/f106.xml::INSTALL_106::SQLCL-Generated was: 9:6eba3c7690b06b454178b27504955129 but is now: 9:59a767b7ace2662ac8340f3fd5d81100
Observations & Workaround:
- The error indicates that the checksum for the changeset has changed, which makes sense since the APEX application was modified.
- However, I would not expect this to cause a validation error, as it’s normal for an APEX file’s checksum to change when adjustments are made.
- To resolve the issue, I manually added
runOnChange="true" to the changeset header in the app XML, and the deployment then worked as expected.
Question:
Would it make sense for runOnChange="true" to be the default setting for APEX changesets? This would help prevent validation failures for legitimate app changes.
I’d appreciate your insights on whether this is the intended behavior or a potential bug.
Thanks in advance for your help!
Best regards,
Patrizia