I'm facing the following error:
Layout: In field: excludeButtons, no such standard action:IsotopeSubscription
I've no idea whatsoever about the error. Can anyone help me out? Thank you.
Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It only takes a minute to sign up.
Sign up to join this communityI'm facing the following error:
Layout: In field: excludeButtons, no such standard action:IsotopeSubscription
I've no idea whatsoever about the error. Can anyone help me out? Thank you.
There's nothing you can do about this. You need to contact the vendor of the managed package and advise them of the issue on Spring '22 prerelease. Note however that this may or may not represent an actual issue in Spring '22; preview orgs occasionally contain unusual configurations that do not persist into production.
If you are working on this managed package, you'll need to remove the reference to IsotopeSubscription
from your Page Layout metadata, which is likely something that was captured from a development org but never intended as part of your product per se.
IsotopeSubscription
is related to. There won't be any impact as such in Spring '22 because you're simply removing a button that is no longer available anyway.
My error looked like this:
MyCustomObject__c: No such standard button to exclude IsotopeSubscription
The error popped up recently for no apparent reason on a project that is several years old. With my particular DevOps setup, it was preventing me from pushing code changes. I'm guessing it was caused by platform updates made by Salesforce.
I deleted all instances of the following:
<excludeButtons>IsotopeSubscription</excludeButtons>
(Found it in .layout
files.)
And I deleted all instances of the following:
<excludedStandardButtons>IsotopeSubscription</excludedStandardButtons>
(Found it in .object
files.)
That did it for me.
I had this error when creating 2GP package.
Fixed by upping to minor version instead of patch.
Previous version: 1.4.0
Failing version: 1.4.1
Working version: 1.5.0
Skipping ancestry check didn't make any difference.