Option to ignore: <personAccountDefault> in XML
When comparing XML for RecordType permissions in Profiles, some Sandboxes return:
<personAccountDefault>true</personAccountDefault>
As part of the XML, even though person accounts are not enabled, this makes comparing annoying.
It would be nice to have an option to ignore this.
Eric van Horssen
shared this idea
-
Tyler Meadows commented
Would benefit from a generalized version of this — the same class of problem hits External Client Apps (<orgScopedExternalApp>, <oauthLink>, <consumerKey>, <clientCredentialsFlowUser>, <commaSeparatedPermissionSet>) which are auto-populated with org-specific identifiers that fail cross-org deploys. A generic 'ignore XML node' filter would solve both."
-
Justin Slagle commented
Experiencing the same thing - getting the following in comparisons, even though I don't have Person Account activated in the org:
<personAccountDefault>true</personAccountDefault>
Not sure what is causing this attribute to show up, but I'd love to know what the fix is for this.
-
Tommy Dhondt
commented
I'm experiencing exactly the same Gearset issue (Person Accounts is not enabled in our SF landscape).