10,882
edits
Salesforce admins: Urgent action required!
Mark as Parent Pointer: Difference between revisions
Jump to navigation
Jump to search
→Implications
| Line 24: | Line 24: | ||
Finally, there is one Salesforce-specific impact, aimed at data download optimization: | Finally, there is one Salesforce-specific impact, aimed at data download optimization: | ||
* (Salesforce only) Check '''Mark as Parent Pointer''' for sf_attachment.parentid property to download only attachments belonging to records that are available offline. Use this “trick” when you see that sync clears a lot of sf_attachment records, which were just downloaded. | * (Salesforce only) Check '''Mark as Parent Pointer''' for sf_attachment.parentid property to download only attachments belonging to records that are available offline. Use this “trick” when you see that sync clears a lot of sf_attachment records, which were just downloaded. | ||
== Missing parent pointer flag for custom tables == | |||
For standard Power Platform/Dynamics tables, Woodford automatically enables the '''Mark as Parent Pointer''' option. For custom tables, Woodford administrator has to enable the option manually. If you don't enable it, you can observe one or more of the following problems: | |||
; Sync upload errors for orphaned child records | |||
* The user has created a parent record and a few child records in the app. Later, the user deleted the parent record. Because of the missing parent-child relationship, the child records remained orphaned. This manifested during sync as upload errors. Deleting local data was an immediate fix for the affected user, but letting Resco Mobile CRM know that there's a parent-child relationship between the tables is the permanent fix. | |||
; Child records not available | |||
* Woodford admin enabled two custom tables, but did not set up the parent-child relationship in Woodford. Resco Mobile CRM did not download any child records. Why? In Power Platform/Dynamics, child table permissions are inherited from the parent table. If Resco is unaware of the parent-child relation, the child table has no permissions (including Read). Therefore, no records can be downloaded during sync. | |||
[[Category:Woodford]] [[Category:Synchronization]] | [[Category:Woodford]] [[Category:Synchronization]] | ||