When you compare and deploy a ProfileTabVisibility.standard-QuickText item, you may run into a Salesforce deployment error:

"You can't edit tab settings for QuickText, as it's not a valid tab."

This article explains the root cause of this deployment issue and how to resolve it.

You may trigger this error if you select the Admin.ProfileTabVisibility.standard-QuickText item in a comparison (and/or the equivalent for other profiles) and try to validate or deploy it.

A Gearset Problem Analyzer may be triggered, suggesting that it is removed from deployment.

If you do not tick the box to accept the suggested fix, and proceed with a validation/deployment, you will see an error message for the Profile metadata type, like this:

This can happen if:

You should check both the Classic and Lightning settings below.

If you start out in Lightning mode, you should switch to Salesforce Classic and activate tabs in Classic mode as well.

You should be able to resolve the error by enabling the Quick Text Settings in your target org.

You can also enable the Quick Text Settings in Lightning in your target org; however, this only affects the Lightning Experience text, so it may not fully resolve the issue.

Please note that Classic and Lightning Quick Text settings do behave slightly differently with the Salesforce Metadata API.

If you run a comparison and the Classic Quick Text settings are different between the source and the target, the -QuickText item will appear in your comparison, so you can deploy this change via Gearset.

The Lightning Quick Text settings are not retrievable or deployable via the API, you would need to manually go into your Target Org and change the settings for Lightning Quick Text.
​

If you tick the Gearset Problem Analyzer suggested fix to remove the item from your deployment package, the error won't be triggered when you proceed.

In the profile of the Gearset connection user, try setting the tab permission to Default On. Some users have had success after doing this.

If you're still stuck after trying these steps out, please get in touch with us via the In-app chat, and we'll do our best to resolve the issue with you.