What happens on a subsequent update in Redshift if a record that's created in Syncari from Redshift and then created in SFDC from Syncari is then deleted from SFDC? Will Syncari recreate the record in SFDC or block it from being created because of the original deletion?
It should not. the ID mapping should show the deleted salesforce record and the only way for that Redshift record to send an update to salesforce is if someone creates a salesforce record that matches the criteria from the redshift source and the ID mapping shifts to the non-deleted record.
How do I troubleshoot OAuth authentication errors?
If you authenticate using OAuth and encounter errors while configuring or testing a Salesforce synapse or if you see this error message, follow the troubleshooting steps below:
ApiFault exceptionCode='INVALID_SESSION_ID' exceptionMessage='Invalid Session ID found in SessionHeader
- Make sure that you're using a Salesforce edition with API Access. Salesforce Enterprise and Unlimited include API Access, and you can purchase API access for the Professional edition. Check out this Salesforce help article to be sure you have a supported edition.
- Make sure that the OAuth user does not have the Multi-Factor Authentication for User Interface Logins permission. See this Salesforce help article for details.
- Make sure that the OAuth user does not have single logout (SLO) enabled. See this Salesforce help article for details.
- Make sure that your organization uses API version 45 or later. See how to check in this Salesforce help article.
- Make sure that the Refresh Token Policy is not set to Immediately expire refresh token. See how to check in this Salesforce help article.
- Check your Session Settings. Check out this Salesforce help article or more.
- Make sure that the Session Timeout is no lower than two hours.
- Make sure that the following Session Settings are not selected:
- Lock sessions to the IP address from which they originated
- Lock sessions to the domain in which they were first used
Related to