Error overview
You may run into this Salesforce validation error when deploying a new or changed Lightning page metadata component (also known as FlexiPage).
Example
An example of the error message returned in our app would look as below:
"Invalid property [label] in component [flexipage:tabset]"
In this example, Salesforce is returning information that property [label] is an invalid element in component [flexipage:tabset].
Explanation of the error
This error can happen when you're making an org to org deployment where the source org (environment you're deploying from) is on higher API version than the org you're deploying to (target environment) - as surfaced on Salesforce StackExchange forum.
Example: source org with API v 50, and target org with API version 49.
Note: Keep in mind there may be other reasons for this validation error to surface that we may not be aware of.
Resolution
To resolve the error, follow one of the two workarounds we propose.
Workaround 1
If you're making an org to org deployment via Compare and deploy, try to amend the API version of your comparison to match the lower API version used by the target org.
To find out how to amend the API version used in the comparison, check this article:
Workaround 2
Note: If you're running into this specific validation error: "Invalid property [enableActionsInNative] in component [force:highlightsPanel]" - check Salesforce documentation on how to resolve it.
If the workaround 1 doesn't work, or if it isn't applicable to your use case (e.g. because both of your orgs are on the same API version), we recommend to:
1. Download your deployment package from Gearset (after having run the comparison).
2. Then amend the package locally (e.g. in VS Code) by removing the line(s) of code referenced in the error message.
You'd need to remove it from the XML of the failing metadata type (e.g. in above example it's a Lightning page from which <name>label</name> property was removed).
3. Use the amended deployment package in .zip format as the source of your new deployment in Gearset.
For more info on how to download and change the deployment package, check this article: How can I change the package XML 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.