Error overview
This Salesforce validation error that Gearset is surfacing is likely to occur on the Flow metadata type during an org deployment made via Compare and deploy, or during a PR validation in Gearset Pipelines.
On below example, we're seeing the error:
"Name (Screen Component) - inputsOnNextNavToAssocScrn isn't supported for field Type "InputField"."
We've seen users encountering this error in particularly in relation to inputsOnNextNavToAssocScrn referenced in the XML of the Flow (example below).
Explanation of the error
Based on our previous investigations, this validation error is usually caused by your Gearset comparison running on a lower API version than the API version used by the Flow you're trying to deploy.
On below example, Gearset comparison uses API version 55, while the Flow is on API version 59.
Updating the comparison's API version to v59 would resolve the validation error.
Resolution in Compare and deploy
If you're using Compare and deploy feature, e.g. for a simple org to org (or Git to org) deployment, follow these steps:
1) Check the API version of the Flow you're trying to deploy.
2) If you confirm the Flow is on API version higher than the API version of your comparison - amend the comparison's API version to match the version of the Flow, or use a higher API version.
3) Re-run the validation, which should hopefully succeed.
Resolution in Gearset Pipelines
If the error is happening during PR validation in Gearset Pipeline, follow these steps:
1) Update the API version for the CI job used in the environment to which you're promoting the PR. Then re-validate the PR.
Note: API version of the CI job should match the API version of the Flow, or be set to higher version.2) If the above doesn't resolve it, check the API version used in your feature branch.
Note: For the PR validation to succeed - API version of the repository and feature branch should match the API version of the Flow, or be set to higher.
For scenarios where API version differences may not be the root cause
If you've troubleshooted points 1 and 2, and confirmed that API version differences are not a root cause of the validation error, consider below options:
3) If you're deploying Flow from a Git branch, consider removing the line(s) of code from the XML referencing "
inputsOnNextNavToAssocScrn", such as:
4) Root cause of the same error surfaced by another user:
They added a lookup to the Flow screen using the record field feature, rather than a standalone lookup. To resolve the error, they reworked the Flow to not use the new feature - this resulted in successful validation.
Note: Keep in mind this resolution may be applicable for specific user scenarios, therefore may not apply to all cases.
Disclaimer: This error is returned by Salesforce directly, rather than Gearset. Even so, we offer guidance based on our combined experience with the Metadata API. Where possible, we try to help guide you to fix or avoid this error. In the case that this isn't possible, we may need to direct you to Salesforce support for further clarification.