Skip to main content
All CollectionsTroubleshootingSalesforce validation errorsSalesforce validation errors
Resolving validation errors - "In field: QuickAction - no QuickAction named <xxx> found"
Resolving validation errors - "In field: QuickAction - no QuickAction named <xxx> found"

Cause and resolutions to this Salesforce validation error

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

Explanation of the error

This Salesforce validation error that Gearset is surfacing is likely to occur on the Layout metadata type.

The error message returned by Salesforce is:
​"In field: QuickAction - no QuickAction named <xxx> found" - where <xxx> is a name referencing a specific quick action.

Example of the error shown in Gearset:


On this specific example Salesforce requires that QuickAction metadata is present in the deployment package for the deployment of the Layout to succeed.

By including the Quick action metadata type in your comparison's filter (if you're using Compare and deploy), you should be able to resolve the validation/deployment error.

Resolution

As per Salesforce documentation, this error is happening because Salesforce is unable to find the standard Global Action during validation (or deployment).

Usually, by adding Quick action metadata type to your metadata filter in Gearset app, you'd be able to resolve the error.

This is because Quick action metadata would retrieve the component <xxx> (quick action) specified within Salesforce's error message. This would also allow our Problem Analyzers to suggest you to add it (the missing component) to the deployment package for the validation to succeed.

Salesforce also explains that in case you do not see standard Global Action <xxx> (e.g. it isn't retrieved in your comparison results), you would need to create a new Global Action (in the source environment) with name <xxx>, and then add that component to your deployment package.

Note: When manually creating the Global Action in your source environment (org), the component's name <xxx> must match the name referenced in the Salesforce's error message.

More information about resolution to this error type can be found in:

Salesforce Help (12 July 2023)

Other workarounds

There are also other workarounds proposed in the SFDX-Hardis documentation, such as:

  • If QuickAction referenced in the error message is a standard Quick Action, you can activate related features in the target org. You'd need to know what those related features are.

  • Resolve other validation errors that could impact the deployment of your QuickAction. This may be applicable when your deployment fails with multiple validation errors.

  • If none of the above helps, consider removing QuickAction from the source XML.

    Gearset can help with that - our app allows you to download your deployment package, amend it (e.g. by removing specific lines of XML), and then use the amended version of the deployment package as the source of your new comparison (and essentially a source of a new deployment).
    Read below guidance for more information:
    How can I change the deployment package before deploying?

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.

Did this answer your question?