ACT NOW: The Alteryx team will be retiring support for Community account recovery and Community email-change requests Early 2026. Make sure to check your account preferences in my.alteryx.com to make sure you have filled out your security questions. Learn more here
Start Free Trial

Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.

Alteryx Server bad argument type for built-in operation on Salesforce Input Connector

Pablo123
5 - Atom

Hi,

 

I am using the Salesforce input connector to extract data from our salesforce environment. The workflow runs fine on my desktop in designer but when I publish to the gallery, I get this error "bad argument type for built-in operation". How do I resolve this?

3 REPLIES 3
fmvizcaino
17 - Castor
17 - Castor

Hi @Pablo123 ,

 

Are you using DCM to save your credentials? If so, please synchronize your Designer with your Server`s DCM.
https://knowledge.alteryx.com/index/s/article/DCM-Sharing-and-Syncing-DCM-Connections

 

Best,

Fernando

fnfunkin
5 - Atom

@Pablo123 FNF wrote:

Hi,

 

I am using the Salesforce input connector to extract data from our salesforce environment. The workflow runs fine on my desktop in designer but when I publish to the gallery, I get this error "bad argument type for built-in operation". How do I resolve this?


Synchronizing the version between Designer and Gallery is difficult. You should double-check that the Salesforce connector version and the Python environment on the server match your personal computer, as this error is often caused by library conflicts.

chandra_balusugure
7 - Meteor

Hi @Pablo123,

 

Please cross-check the Salesforce connector version on your local Designer and the Alteryx Server. If both versions are the same, please try the following resolution:

 

  1. Open the affected Server workflows in Alteryx Designer.

  2. Review the existing Salesforce Connector tool configuration(s) and make a note of the current settings.

  3. Remove the Salesforce Connector tool(s), then add them back to the workflow and reconfigure them using the same settings as before.

  4. Save the updated workflow back to the Server.

 

Regards,

@chandra_balusugure