Repository navigation
Generated names for person contact fields become pc, pc_dup, pc_dup_dup... #98
Description
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"
}
]
}
Activity
[-]Generated names for person contact fields become pc_dup, pc_dup_dup, pc_dup_dup_dup...[/-][+]Generated names for person contact fields become pc, pc_dup, pc_dup_dup...[/+]ChuckJonas commentedon Dec 31, 2020
oh interesting... I had no idea there was a
__pcAPI ending. I think it just needs to be added to this line of code:https://github.com/ChuckJonas/ts-force/blob/master/ts-force-gen/src/util.ts#L5
Would be a good opportunity to rewrite the function to be a little less horrible.
Generate field names without pc_dup_dup ChuckJonas#98