topic Re: Salesforce Module Name not selectable in Talend Studio

Salesforce Module Name not selectable

Selina1 — Sat, 16 Nov 2024 09:02:36 GMT

Hello,

I am using Talend Data Management Platform 6.4.1.20170926_0449-patch. The Talend job of connecting to Salesforce was upgraded from 6.2.1 to 6.4.1 recently. Job can connect to Salesforce and pull data without any problem.

However, if I tried to change the Module Name from Account to other module by clicking "......", it hangs there forever.

Here is my connection string

Connection String should be fine because I can run the job to connect to SF without issue. The problem is I can not change the existing module. I also tried to create a new tSalesforceInput, I can not select module neither.

Does anyone have this issue? I can not test if 6.2.1 have this issue because our servers were decommissioned already.

Any help would be much appreciated!

Yan

Re: Salesforce Module Name not selectable

TRF — Fri, 17 Nov 2017 18:26:48 GMT

Hi,
Are context variables populated using an external file or database?
If so, try to defined default values for these variables in context tab.
Hope this helps.

Re: Salesforce Module Name not selectable

Selina1 — Fri, 17 Nov 2017 18:51:18 GMT

Thank you TRF!

Yes, context variables are defined in context tab, not populated from external file or DB.

Thank you!

Yan

Re: Salesforce Module Name not selectable

TRF — Fri, 17 Nov 2017 19:14:24 GMT

Sounds like a bug.

Works fine with Talend DI.

Sorry to be unable to help you.

Re: Salesforce Module Name not selectable

Selina1 — Fri, 17 Nov 2017 19:18:47 GMT

Thank you very much for trying to help!

What is your production full name and version?

Yan

Re: Salesforce Module Name not selectable

TRF — Fri, 17 Nov 2017 19:21:15 GMT

Talend Open Studio for Data Integration
Version: 6.4.1
Build: 20170623_1246

Re: Salesforce Module Name not selectable

Selina1 — Fri, 17 Nov 2017 19:23:54 GMT

Thank you very much! I will open a support ticket to see and update here for the solution.

Yan

Re: Salesforce Module Name not selectable

Selina1 — Mon, 15 Jan 2018 21:27:40 GMT

It is not I forgot to update you guys. I have not got solution from Talend Support. My ticket has been opened about two month, they even have not been able to reproduce the issue I have --- It is not that they could not reproduce the problem after they followed my instruction, it is they have been not able to exactly follow my instruction. They once responded to me not being able to reproduce my issue and I found they missed one step in my instruction. They are very unresponsive, almost never updated me until I checked status.

Re: Salesforce Module Name not selectable

Anonymous — Wed, 17 Jan 2018 02:59:08 GMT

Hello ,

Thanks for letting us your current situation. Would you mind giving us your case ID and we will check it with support team about your issue?

Our apologies for the inconvenience and unresponsive. We'll keep you posted as soon as we can.

Best regards

Sabrina

Re: Salesforce Module Name not selectable

Selina1 — Wed, 17 Jan 2018 17:18:13 GMT

Thank you Sabrina!

Here is the case number -- Case# 00087546 - SalesForce connect to upload data

Re: Salesforce Module Name not selectable

Anonymous — Tue, 18 Jun 2019 15:17:38 GMT

I have the same problem.

Any ideas ???

Re: Salesforce Module Name not selectable

Selina1 — Tue, 18 Jun 2019 18:11:16 GMT

Sorry, I do not have solution.

Ticket was opened and support tried to get Salesforce testing account to reproduce the issue. Then it stopped there. I did not followup.

Re: Salesforce Module Name not selectable

Anonymous — Wed, 19 Jun 2019 08:30:55 GMT

I have already solved this problem configurating the proxy manually in Talend.

Set proxy in talend

Automatic Proxy configuration for Talend

In the menu bar, go to “Windows > Preferences”
Locate “General > Network Connections”
Set “Active Provider” to “Manual”
Under “Proxy entries, highlight “HTTP” and click [Edit…]
Set the values:
Click [OK]
Click [OK]
Restart Talend.

Re: Salesforce Module Name not selectable

Selina1 — Wed, 19 Jun 2019 15:31:33 GMT

Thank you very much for posting your solution!

We are currently working on migrating from 6.4.1 to 7.1.1. Do not know if issue is fixed or not. If not, I will try your solution.