Salesforce Advanced Connector Datasets Not Updating

Tom_Knickerbocker

Hi,

I have the following datasets that use the Salesforce Advanced Connector:

45a359e1-5f9e-4877-9e36-535dc45812a5

a46fe459-e856-44e2-8491-7699efcad941

Today, when running these datasets, the changes from the Salesforce side are not reflecting, despite the dataset running 'successfully.' The Data Preview seems correct but the actual data being imported in is not updating.

In 45a359e1-5f9e-4877-9e36-535dc45812a5, I deleted all records in Salesforce on the object in question, so the dataset results should show 0, but it's still showing 83 records. The Id values that were pulled in were checked in Salesforce, and Salesforce says they're deleted.

In a46fe459-e856-44e2-8491-7699efcad941 I updated some values in Salesforce which aren't being reflected in the Domo dataset.

I've re-authenticated my credentials in the dataset Settings, I've re-installed the Domo Connector package in Salesforce, ensured my permissions in Salesforce allow full admin rights to the records, ensured that it's only pulling Active records, and ensured the Scheduling is set to Replace and not Append.

Tom_Knickerbocker

Hi, first of all my apologies for including the dataset Ids, I mistakenly thought this board was for internal Domo support. I've since been able to resolve my issue with them.

The issue stemmed from having a Connector dataset in Domo that contained records, where the source data tied to the query was deleted from the source object. This resulted in the dataset failing to update. However, when I added one record back into the source table, the dataset updated successfully.

Apparently, if a Domo dataset that uses a Salesforce connect contains data, and all of the data is deleted from the source table within the query parameters, the dataset fails to update. There must be at least 1 record available in the source table for the query to update correctly.

I hope this helps others who are facing this problem.

OllyB

The issue you're facing with the Salesforce Advanced Connector in Domo, where changes in Salesforce are not reflecting in your datasets despite successful dataset runs, could be caused by several factors. Let's troubleshoot step by step:

1. Understand Salesforce Deleted Record Behavior

• Deleted Records in Salesforce: Even after deletion, records may still exist in the Salesforce Recycle Bin and can be retrieved in certain queries. Ensure the connector is configured to exclude records in the Recycle Bin by using the IsDeleted = false filter if applicable.
• Hard Deletes: If you're testing with hard-deleted records (bypassing the Recycle Bin), ensure the connector has access to this level of data.

2. Confirm Data Sync Timing

• Data Preview vs. Dataset Update: The "Data Preview" showing the correct data indicates that Salesforce is returning the correct results during manual inspection but may not be reflecting during scheduled updates. This could mean:
  • There's caching involved in the Domo connector.
  • The scheduling logic may not be refreshing correctly, despite being set to "Replace."
• Resolution:
  • Try manually running the dataset update instead of relying on scheduling.
  • Check if the dataset's job history shows any discrepancies between runs.

3. Connector Configuration

• Field-Level Filters and Queries: Check the query configuration in the dataset settings. Ensure filters like "Active Records Only" are correctly applied.
• Query Limits: If the dataset queries use conditions or limits, ensure these aren't restricting the data incorrectly.

4. Authentication and Permissions

• Re-authentication: You've re-authenticated credentials, which is good. Confirm that the connected Salesforce user account has access to the latest record states and all objects in question.
• API Access: Ensure that Salesforce API quotas are not exhausted or limited.

5. Connector Settings and Cache

• Dataset Caching: Sometimes, Domo connectors cache results to improve performance. Clear the cache or disable caching temporarily in the connector's settings (if supported).
• Full Refresh: Verify that the dataset is set to fully replace data on each run rather than appending.

6. Connector Version and Updates

• Domo Salesforce Connector Version: Ensure you're using the latest version of the Salesforce Advanced Connector. Older versions might not handle updated Salesforce schemas or API behaviors correctly.
• Reinstallation Confirmation: Since you've reinstalled the Domo Connector package in Salesforce, verify that the package and its configurations are fully functional.

7. Error Logging and Support

• Error Logs: Review the logs for both the Domo dataset runs and Salesforce API calls for any subtle errors.
• Contact Domo Support: If the above steps don't resolve the issue, Domo Support can review backend logs for anomalies in the connector’s data ingestion process.

Additional Suggestions:

• For dataset 45a359e1-5f9e-4877-9e36-535dc45812a5, ensure the query explicitly excludes deleted records (IsDeleted = false).
• For dataset a46fe459-e856-44e2-8491-7699efcad941, verify that field mappings are correct and updated values are within the connector's field scope.

Let me know how these steps work out!

Tom_Knickerbocker

Hi, first of all my apologies for including the dataset Ids, I mistakenly thought this board was for internal Domo support. I've since been able to resolve my issue with them.

The issue stemmed from having a Connector dataset in Domo that contained records, where the source data tied to the query was deleted from the source object. This resulted in the dataset failing to update. However, when I added one record back into the source table, the dataset updated successfully.

Apparently, if a Domo dataset that uses a Salesforce connect contains data, and all of the data is deleted from the source table within the query parameters, the dataset fails to update. There must be at least 1 record available in the source table for the query to update correctly.

I hope this helps others who are facing this problem.