MALFORMED_ID:N° facture: Valeur d'ID de type incorrect : 0123______0123:NxxxxxFxxxxe__c --

Highlighted
Six Stars

MALFORMED_ID:N° facture: Valeur d'ID de type incorrect : 0123______0123:NxxxxxFxxxxe__c --

Hi all

I can't figure out why is the data rejected in this case.
I want to update the data in salesforce and I have this message every time I try to update data  in salesforce.
For example, The below record is present in both the tables to which my job refers.
 07011811001987
Still I have this error 
MALFORMED_ID:N° facture: Valeur d'ID de type incorrect : 0123______0123:NxxxxxFxxxxe__c --

Kindly suggest what can be done in Talend job to resolve the issue.

Highlighted
Sixteen Stars
Sixteen Stars

Re: MALFORMED_ID:N° facture: Valeur d'ID de type incorrect : 0123______0123:NxxxxxFxxxxe__c --

Are you sure the field Id contains a regular Salesforce id?

TRF
Highlighted
Six Stars

Re: MALFORMED_ID:N° facture: Valeur d'ID de type incorrect : 0123______0123:NxxxxxFxxxxe__c --

Yes, I have checked.
The ID is a regular salesforce ID.




Highlighted
Six Stars

Re: MALFORMED_ID:N° facture: Valeur d'ID de type incorrect : 0123______0123:NxxxxxFxxxxe__c --

@TRF

Can you please suggest any clue  or possibilities on how I can solve this error.

Highlighted
Sixteen Stars
Sixteen Stars

Re: MALFORMED_ID:N° facture: Valeur d'ID de type incorrect : 0123______0123:NxxxxxFxxxxe__c --

Can you share an extract of the data flow which is send to salesforce (including the header line)?


TRF

2019 GARTNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

Best Practices for Using Context Variables with Talend – Part 2

Part 2 of a series on Context Variables

Blog

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema

Blog