All Collections
Troubleshooting
Salesforce Validation Errors
Resolving Validation Errors - "RecordType (Screen Component) - inputsOnNextNavToAssocScm isn't supported for fieldType <xxx>"
Resolving Validation Errors - "RecordType (Screen Component) - inputsOnNextNavToAssocScm isn't supported for fieldType <xxx>"

Cause and solution for this Salesforce validation or deployment error

Mateusz Kochanowicz avatar
Written by Mateusz Kochanowicz
Updated over a week ago

You may come across this Salesforce error on a Flow metadata type:

RecordType (Screen Component) - inputsOnNextNavToAssocScm isn't supported for fieldType "<xxx>" - where "<xxx>" in this context is a reference to a specific field type (InputField) within your org.

This could be a 'DropdownBox' or a 'ComponentChoice' (our users have reported this error on these field types), or it could be yet another field in your use case.

This article explains why this error occurs and how you can get past it.


What in my metadata is causing the error?

In your Gearset comparison results, identify the Flow metadata component that is causing the error. Check the XML file of that component to see if it includes the tag
<inputsOnNextNavToAssocScrn>UseStoredValues</inputsOnNextNavToAssocScrn> under the fieldType referenced in the error message.

In this example (screenshot below), we can see that field 'DropdownBox' includes the tag <inputsOnNextNavToAssocScrn>UseStoredValues</inputsOnNextNavToAssocScrn> which is the cause of the error.

You'll have to use a VS Code (or a similar XML editor) and manually remove that tag (highlighted in blue on below screenshot) from the failing component's XML file.

Or you can remove from the XML file both the field (fieldType) and the tag.

In this example the field to be removed from the XML would be:
<fieldType>DropdownBox<fieldType> (highlighted in red on below screenshot) along with <inputsOnNextNavToAssocScrn>UseStoredValues</inputsOnNextNavToAssocScrn>

Salesforce provides more information about this error type in their Known Issues forum and they advise to apply this workaround to resolve the error.

Note: The name of the field (referenced as fieldType in your XML) will be different to 'DropdownBox', as this is a custom name given to this field in the Git source comparison screenshot used in this article.

Did this answer your question?