Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Person Account Custom fields ignored #71

Open
vaumont opened this issue Apr 9, 2021 · 4 comments
Open

Person Account Custom fields ignored #71

vaumont opened this issue Apr 9, 2021 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@vaumont
Copy link

vaumont commented Apr 9, 2021

In an org with Person Account enabled:

  1. create a xyz__c custom field on the Contact object
    Salesforce automatically creates a xyz__pc field on the Account object

OrgCheck does not report on the __pc field.

  1. On the account object, create an abc__c formula fields that references the Account.xyz___pc field
  • Account.xyz__pc is still not listed
  • OC shows that abc__c uses xyz :

image

@VinceFINET VinceFINET self-assigned this Apr 13, 2021
@VinceFINET VinceFINET added the bug Something isn't working label Apr 13, 2021
@VinceFINET VinceFINET added this to the Version 1.9.3 milestone Apr 13, 2021
@VinceFINET
Copy link
Collaborator

On the "Objects" tab, I can see the Person Account field on the Account object
image

And the DAPI is showing this for this field:
image

@VinceFINET
Copy link
Collaborator

Effectively on the "Custom Fields" tab, i cannot see the same on the account object.
i see only the field on Contact
image

@VinceFINET
Copy link
Collaborator

The following query from Tooling API is not showing the pc field

SELECT Id, TableEnumOrId, DeveloperName, NamespacePrefix
FROM CustomField 
WHERE TableEnumOrId = 'Account'
AND DeveloperName = 'xyz_test'

I found the field if I change the statement with TableEnumOrId = 'Contact'

My assumption is that Tooling API does show up the pc fields.
I will investigate internally.

@VinceFINET
Copy link
Collaborator

pushing this feature to future release as it may means to refactor from tooling to metadata api...

@VinceFINET VinceFINET removed this from the Version 1.9.5 milestone Jun 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants