- Issue created by @rishi kulshreshtha
When using the Salesforce module to sync data between Salesforce and Drupal, updates to existing Salesforce records are not reflected in Drupal unless a manual force pull is performed. While new users are created when a record is added in Salesforce, updates to existing users are not being synced automatically via cron. Attempts to sync using both cron and the standalone queue have produced the same results: updates only occur when manually triggered. This creates a gap in synchronization for existing records, as Drupal does not reflect the latest changes from Salesforce unless a manual intervention is made.
1. Set up the Salesforce module with cron-based synchronization.
2. Update an existing user record in Salesforce.
3. Wait for the scheduled cron run to trigger the pull operation.
4. Check the corresponding Drupal user record to see if the updates from Salesforce are reflected.
5. If the updates are not reflected, manually force-pull the updated record from Salesforce and check the Drupal user record again.
Investigate why automatic updates to existing Salesforce records are not being pulled by cron or the standalone queue. Ensure that the cron and queue mechanisms are correctly fetching updates to existing records. If any specific settings or configurations are required, document those clearly for users to avoid confusion. Also, check if there is a mismatch in how the pull operations are handled between new and existing records.
- Debug why cron and queue operations are failing to update existing user records.
- Identify if additional configuration is needed for updating existing records versus creating new ones.
- Document findings and provide guidance on settings or adjustments that need to be made.
- Test to ensure that after fixes, updates from Salesforce reflect correctly in Drupal without manual intervention.
No anticipated user interface changes.
No API changes expected at this time.
No changes to the data model are expected.
Active
5.1
salesforce_pull.module