There is no unique id/field/column to select in the snap so that, we can update that particular record/row in the table.
A Mapper Snap before the Salesforce Update Snap can be used to specify ID.
See the example in the documentation: https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438491/Salesforce+Update
for example, I want to update the table in which 3 columns are there; empNo, Salary, Department.
now, I want to increase the salary for particular department. My question is where we are configuring that Department is condition and Salary is the updating column. In mapper we just map two columns Salary and Department.
I’m having a similar problem with a custom object. I believe it has to do with permissions and if the columns are accessible and updateable to your user. I am currently working with my Salesforce administrator prior to raising a support ticket.
Hi @brianrandolph , I could not get in what way it is related to my question.
You stated that you can’t see the empNo column in the mapper snap. It may be due to the permissions on the column for the user id you are using.
@GBekkanti, to use the Salesforce Update snap, you must have the Salesforce record “Id” present in the document. So your upstream snaps will need to capture the Id from Salesforce for the particular record(s) you want to update and pass the Id through to where you can include it in the Mapper before the update snap.
Here’s a simplistic example to increase all the Sales department by $5. Notice, only Id and Salary__c are required in the Mapper. Department__c is not required in the Mapper. (I did include it in the Read snap Output fields, but it wasn’t necessary unless you want to use a downstream Filter snap instead of the Read snap’s Where clause.)
Disclaimer: I mocked this up without testing, so please excuse any typos.
Thank You @del