Skip to content

Generated names for person contact fields become pc, pc_dup, pc_dup_dup... #98

@wuservices

Description

@wuservices

When generating code in an organization with Person Accounts enabled, custom Contact fields on an Account are exposed as Account.ContactField__pc and Account.OtherContactField__pc, but the code generator names these as pc and pc_dup (then pc_dup_dup and so on for more fields), instead of contactField and otherContactField.

This isn't a huge deal, since you can still fix it by overriding the defaults per the awesome docs:

{
  "apiName": "Account",
  "fieldMappings": [
    {
      "apiName" : "ContactField__pc",
      "propName": "contactField"
    },
    {
      "apiName" : "OtherContactField__pc",
      "propName": "otherContactField"
    }
  ]
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions