Page History

Issue 1 : How to update Salesforce using status writer update source when there are no fields to map with the external Id from database External ID of Salesforce from a Database table.

Description: Getting an “Application request abort” error message on QuickBooks web connector whenever This happens when you try to hit update select button from web connector.This usually happens whenever you enter an incorrect file path in the QuickBooks desktop connector in your project. This might also happen when you try to sync using web connector which is not configured with the opened file. Resolution 1: If there is no external Id field then we can just sync integrate from Salesforce to Database. Let us say there is no External ID of Salesforce to map with primary key of a table in a Database. If so then, you cannot update status back to Salesforce.

Resolution : Create a Rule that will process data from Salesforce to Database along with Salesforce IdID. Then, which is a normal process.In the next step add add one more workflow Rule and use update Update operation to just bring back the Salesforce Id from database to Salesforce, this way ID from the Database. By so doing, we can successfully map update the status back to Salesforce.

Issue 2 :  What if we have an external ID in order object Can we map the External ID of Salesforce with the primary key of a Database table to update back the status of Salesforce? 

Description : Lets say we have an External ID field on Order object in Salesforce (Order_external_ID__c) which should be the SeqNo that is being created in Database. So, when we create new order in Database, we get SeqNo which I need to update back . A DBSync user would like to map it with SeqNo (auto generated primary key) field of a Database table. So, whenever a new order is inserted into a Database, DBSync gets SeqNo to update back to Salesforce on success map . But that is not visible on success map.

Description : This issue occurs when an user try to hit the update select from the web-connector. The cause of this issue when an web connector is configured by an non - admin user of the QuickBooks but later the user is deleted from the QuickBooks. The error is as shown in the below image.

Resolution : SEQNO is a autonumber in Database and it should not be mapped at all as it does that, in turn, will not be visible in Salesforce.

Image Added

Resolution :  Since SeqNo field is an auto number in Database, we advise that you do not map it with External ID of Salesforce. This is because, an auto generated ID can not hold the value we provide externally.  we You should only map the externalID ExternalID (Order_external_ID__c) to some other field in database, and then a Database. Then, after sync we , you can get this value and the field value that can be used to update back to Salesforce.

...