
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
tSalesforceInput BulkV2 encoding on Cloud engine VS Remote engine
Hello,
I am facing an issue regarding run of a job on Remote engine vs Cloud engine !
The job is a tSalesforceInput with BulkV2 query mode and a tLogRow to display results;
When running on Cloud engine, everyhting is fine (for instance : Autorité)
When running on Remote engine, the encoding is not ok (for instance : Autorité)
When running on the Studio, it is fine !
When switching to query mode "query", it is fine too on Cloud, Remote and Studio !
Do you have an idea what's wrong with BulkV2 on Remote engine ?
Thanks for your help !
Regards,
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
From the Job level:
Could you please click the Run tab > Advanced settings > select Use specific JVM arguments > New > enter -Dfile.encoding=UTF-8. Then re-publish your job Via your remote engine to cloud to see if it works?
Best regards
Sabrina

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Does this character encoding issue only happen with Bulk v2 jobs run by the Remote engine?
Would you please let me know on which talend build version you got this issue and which patch installed in Studio?
What is the encoding used in the salesforce data and on the job?
Thanks for your time.
Best regards
Sabrina

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Sabrina,
Thanks for your answer !
Yes, it is only happening with Bulk2 on Remote engine.
It happend with the studio 8 Build R2022-10 and R2022-09.
I didn't configure any encoding on the job and salesforce !
Regards,

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
From the Job level:
Could you please click the Run tab > Advanced settings > select Use specific JVM arguments > New > enter -Dfile.encoding=UTF-8. Then re-publish your job Via your remote engine to cloud to see if it works?
Best regards
Sabrina

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Thanks, it works !
Regards,

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Great it helps and feel free to let us know if there is any further help we can give.
Best regards
Sabrina
