When mapping related objects, often you would just want to indicate what the lookup / master record is. However, for the sake of data integrity, TaroWorks normally forces all required fields in the object to be mapped to a question and that question is set as required. This means that your field officers would be forced to enter a value and that can overwrite the existing data.
To resolve all the issues with this scenario, you should mark the lookup / master object as “Is Reference Object” using the checkbox of the same name. This has the following effects:
- The requirement to map required fields are overridden.
- You can only map ONE question to an identifying field. (This includes: Object Name, Autonumber, Unique Fields, External ID Fields and Last Name for the Contact Object.)
- You cannot map any other fields, required or not. This is because that record is meant only as reference.
IMPORTANT: If the designated record is not found (due to incorrect entry of the Id Field), the android device would report error 20014. That job would not be synced and would remain in the device, generating an error message every time the device is synced.
Comments
2 comments
It would be great if there were a video outlining how you go about populating a custom object with the necessary fields to make it relate to another object.
Thanks for the feedback AJ! In the mean time here's a quick reference from Salesforce: https://www.salesforce.com/developer/docs/api/Content/relationships_among_objects.htm
Please sign in to leave a comment.