Closed VivekMChawla closed 5 years ago
The relevant code is found here: https://github.com/sfdx-isv/territory-management-tools/blob/6f58c8304ab6a931a305e23b5037858927a68b79/src/modules/tm-tools-objects/territory2-rule.ts#L149-L150
I've added this check to ensure that every field is prepended by Account.
. Most field names in the CSV file that serves as the source for this transform ARE PRE-PENDED by Account.
but some fields are not.
This code ensures every field name gets Account.
prepended. Hopefully this fixes things but I'll keep this bug open a bit until we do more tests.
The fix mentioned in the previous comment appears to have held up. Closing this issue.
The end result of a
tm-tools:tm1:transform
operation results in an extraAccount
being prepended t thefield
key in theruleItems
set.Here's an example of a malformed metadata component:
The
<field>
tag should sayAccount.Territory_vod__c
, but instead it saysAccount.Account.Territory_vod__c