function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Darryl Moyers 20Darryl Moyers 20 

Data Integration Rules (Geocoding) not hitting Trigger

Hi All,

We have setup native Data Integration Rules for geocoding our Account BillingAddress. The Geocoding is working well and we've verified that the latitude/longitude is being updated appropriately and almost-instantaneously after an address update.

We have ensured that the Bypass Trigger checkbox is disabled, but cannot seem to get the process to hit our Trigger. We have tried toggling it off/on but still to no avail.

We have a very simple Debug message at the top of our Account Trigger (Before/After Insert/Update... if it matters) and can confirm that the Trigger is only being hit ONCE. When it is hit, we have confirmed that the Trigger has no awareness of the updated geocoordinates (ie the Trigger call is definitely not initiated by the Data Integration process).

But on a refresh of the record page, the geocoordinates have been updated.

What are we missing here? How do we ensure that the Trigger will get hit after the Geocoding process is completed?

Thanks in advance,
Darryl Moyers
mukesh guptamukesh gupta
Hi Darry,

What methodology you are using for data integration. Like DataLoader or API integration

Please confirm