https://community.qlik.com/t5/Talend-Studio/tSalesforceOutputBulk-error-in-lookup-INVALID-FIELD-Cannot/m-p/2195974#M326 <P>So I figured out the solution and figured i'd update this in case anyone was curious.&nbsp; I had pulled down the whole schema for the object from salesforce even though I was only updating a few of the fields.&nbsp; Turns out one of the fields (unmapped) was the parent_contact__c field, which was having nothing sent to it.&nbsp; However because it was in the schema it wanted to upsert data to it as well but it was really not being updated.&nbsp; Removing the fields that weren't being updated and only including those that were fixed the problem.</P> <P>&nbsp;</P> Thu, 09 Apr 2020 18:35:25 GMT ibcrandy 2020-04-09T18:35:25Z https://community.qlik.com/t5/Talend-Studio/tSalesforceOutputBulk-error-in-lookup-INVALID-FIELD-Cannot/m-p/2195973#M325 <P>So I'm working through converting a bunch of SSIS jobs to Talend and while working on a couple of Salesforce jobs I hit an issue.&nbsp; I converted one job and got the lookups working and everything running fine.&nbsp; I use that as a template for converting another job and I hit this strange error:</P> <P>&nbsp;</P> <P>&nbsp; &nbsp; &nbsp;INVALID_FIELD:Cannot specify both an external ID reference hed__Parent_Contact__r and a salesforce id, hed__Parent_Contact__c:--</P> <P>&nbsp;</P> <P><SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AddressConfig.png" style="width: 999px;"><span class="lia-inline-image-display-wrapper" image-alt="0683p000009M9Oy.png"><img src="https://community.qlik.com/t5/image/serverpage/image-id/150405iEE1BD3792F71C520/image-size/large?v=v2&amp;px=999" role="button" title="0683p000009M9Oy.png" alt="0683p000009M9Oy.png" /></span></SPAN></P> <P>Above I have included how I have that particular bulk upsert configured.&nbsp; The differences between how this one is configured and the other are:</P> <OL> <LI>On the other object it was a master-detail relationship, where here it's a lookup relationship</LI> <LI>This is a managed object while the other was a custom object, though that has never caused issue with the SSIS job and it has been able to upsert just fine.</LI> </OL> <P>I've looked at the WSDL and I see no obvious difference in the fields being used for the lookup.&nbsp; Anyone have any idea why two very similarly configured jobs are getting such different results?&nbsp; Thanks!</P> Sat, 16 Nov 2024 02:44:06 GMT https://community.qlik.com/t5/Talend-Studio/tSalesforceOutputBulk-error-in-lookup-INVALID-FIELD-Cannot/m-p/2195973#M325 ibcrandy 2024-11-16T02:44:06Z https://community.qlik.com/t5/Talend-Studio/tSalesforceOutputBulk-error-in-lookup-INVALID-FIELD-Cannot/m-p/2195974#M326 <P>So I figured out the solution and figured i'd update this in case anyone was curious.&nbsp; I had pulled down the whole schema for the object from salesforce even though I was only updating a few of the fields.&nbsp; Turns out one of the fields (unmapped) was the parent_contact__c field, which was having nothing sent to it.&nbsp; However because it was in the schema it wanted to upsert data to it as well but it was really not being updated.&nbsp; Removing the fields that weren't being updated and only including those that were fixed the problem.</P> <P>&nbsp;</P> Thu, 09 Apr 2020 18:35:25 GMT https://community.qlik.com/t5/Talend-Studio/tSalesforceOutputBulk-error-in-lookup-INVALID-FIELD-Cannot/m-p/2195974#M326 ibcrandy 2020-04-09T18:35:25Z