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

Hi All,

We've setup a reasonably straightforward Apex Class that's running via a Lightning Component. Happy to share the code, eventually, but we seem to have narrowed down the specific scope of our problem... and we're stumped.

When we run our code and attach a debug/trace... It works correctly. All logic performs desirably.

When we run our code without a debug/trace... It performs incorrectly. We're not hitting errors, but our hypothesis is that collections that should have had, say, 3 items in them (when the code works properly, and/or when we attach a debug log/trace) may only contain 1 when we don't do the debug.

Does the problem we're describing above sound familiar to anyone? Our suspicion is that the debug logs / traces are either slowing down the code execution (in a way that's desirable for our code...) or holding onto simple collection variables in a way that they normally wouldn't.

Nothing makes sense, but it is repeatable. 

We're dealing with ~100 lines of Apex, 3 DML statements, and all code is properly bulkified. No callouts. Nothing asynchronous. Just vanilla.

When we run it with Debugs, it works fine; when we run it without debugs, it works incorrectly.

Any thoughts?

Hi All,

We've setup a reasonably straightforward Apex Class that's running via a Lightning Component. Happy to share the code, eventually, but we seem to have narrowed down the specific scope of our problem... and we're stumped.

When we run our code and attach a debug/trace... It works correctly. All logic performs desirably.

When we run our code without a debug/trace... It performs incorrectly. We're not hitting errors, but our hypothesis is that collections that should have had, say, 3 items in them (when the code works properly, and/or when we attach a debug log/trace) may only contain 1 when we don't do the debug.

Does the problem we're describing above sound familiar to anyone? Our suspicion is that the debug logs / traces are either slowing down the code execution (in a way that's desirable for our code...) or holding onto simple collection variables in a way that they normally wouldn't.

Nothing makes sense, but it is repeatable. 

We're dealing with ~100 lines of Apex, 3 DML statements, and all code is properly bulkified. No callouts. Nothing asynchronous. Just vanilla.

When we run it with Debugs, it works fine; when we run it without debugs, it works incorrectly.

Any thoughts?

Hi All,

We've setup a reasonably straightforward Apex Class that's running via a Lightning Component. Happy to share the code, eventually, but we seem to have narrowed down the specific scope of our problem... and we're stumped.

When we run our code and attach a debug/trace... It works correctly. All logic performs desirably.

When we run our code without a debug/trace... It performs incorrectly. We're not hitting errors, but our hypothesis is that collections that should have had, say, 3 items in them (when the code works properly, and/or when we attach a debug log/trace) may only contain 1 when we don't do the debug.

Does the problem we're describing above sound familiar to anyone? Our suspicion is that the debug logs / traces are either slowing down the code execution (in a way that's desirable for our code...) or holding onto simple collection variables in a way that they normally wouldn't.

Nothing makes sense, but it is repeatable. 

We're dealing with ~100 lines of Apex, 3 DML statements, and all code is properly bulkified. No callouts. Nothing asynchronous. Just vanilla.

When we run it with Debugs, it works fine; when we run it without debugs, it works incorrectly.

Any thoughts?

We are using CPQ managed package in our org, when we tring to preview on quote we get this error
No Visualforce context has been established!