Version 4.0 and 4.1 of the Salesforce Input Connector doesn't work on Alteryx Server - I'm on 2019.2. I'm in the process of migrating workflows onto Server, which we recently purchased and the fact that I can't move my Salesforce ETL processes without downgrading Server is a big problem. I've been wrestling with this for two weeks - it was a big distraction during Inspire before I realized there was a known issue here.
Others are having this problem:
https://community.alteryx.com/t5/Dev-Space/Publishing-workflows-with-encrypted-password-to-the-Gallery/td-p/377324
@BlytheE , can we PLEASE prioritize this?!? Thanks!
@matt2 we totally hear you on this one and this is a high priority for me. I want to clarify the workaround for other people having this issue - it's not to downgrade your server version, it's to downgrade the Salesforce Input tool to use a pre-4.0 version.
Not on Scheduler either. Please fix it, thanks.
We reverted back to the deprecated non-py Salesforce input tool and it works on the server 2019.1 - also in a batch macro.
Thank you for the suggestion, @BlytheE ! That helps. One thing, I had to right-click in my Tools area and "show depreciated tools" in Designer. I'm on 2019.2.
Apologies - as my intentions are not to whine about this. However, our organization has experienced nothing but headaches with both versions 4.0 and 4.1 of the Salesforce input tool. I've been patient as this was honestly a last resort, but with Salesforce being, well, Salesforce, I feel that Alteryx should prioritize fixing the bugs in this connector that are literally stopping production for many customers. First, we found 4.1 to be such as drag on the UI (probably due to HTML GUI Set/Get Config settings, etc.) that it was absolutely unbearable to continue development on any workflow using v4.1 of the tool. It also riddles downstream tools (most commonly Selects and Joins) with the indescribably annoying "You have found a bug" errors - which seem to only be remediated via deleting, replacing, and reconfiguring.
So, we downgraded to 4.0, which significantly sped up the GUI experience, but then noticed that it prevented multi-user collaboration of workflows that use the 4.0 input due to the fact that the tool stores session info which is directly tied to a logged in user. Even when we're using a Salesforce (shared) service account for each input, the session errors exist when a different user opens the same workflow. Ideally the tool, upon instantiation (HTML GUI Set/Get Config) would detect already existing username/token/password in the tool's XML config and re-authenticate, at that point, and obtain a new session/token, correct?
Anywho, kindly asking for any progress update on a thoroughly tested new version that addresses these bugs. I'm only passionate because we do love this tool and rely it for business critical processes. It is a great tool for the most widely used CRM in world, after all!
Please fix this to run on gallery!!!!
@BlytheE Any info on a timeline to update the Salesforce connector? As I continue to use the connector (v4.1.0), I am finding some things to look at (I'm working around them by updating the Python code):
Hi @dalym - I believe @bora_perusic is better suited to answer that question. My area is the SDKs themselves that are used to build those connectors, so I don't know specific information around development plans for those tools. Thanks!
Hi I am using v2019.1 and when downloading any of the versions of the salesforce tool, while the tool installer runs i get this error and it fails to load the tool: "No matching distribution for aiohttp==3.3.2 (from -r requirements.txt (line 1))".
What is the solution to have the install tool work correctly?
Need this please
looks Like Alteryx Still did not fix any of the issues that were reported here. That's So bad ..
The Older Versions of the Tool was working okay but they won't work with new sales force API's.
The issue is so bad, that if a Developer develops the Workflow using SFDC input tool v.1 we cannot upload to the server/gallery as the workflow is doing Machine Encryption. That's so Dum. Not sure why it was created like that. It's really useless if we cannot upload it to the server .
Its almost been an year and none of the issues have been addressed , either we get a 401 authentication error or decrypt error and issues with SOQL queries if they are not ordered properly, is there a new version in the near future?
Hello, the Salesforce Connector tools continue to be finicky, especially when used on the Gallery, but can be made to work with some tricks and adjustments. I configured a workflow hosted on my company's Gallery that allows users to search for people within a company and optionally push those people straight into Salesforce as leads. Below are 2 steps I took to enable the Salesforce Connectors:
1. The first error you probably run into is a credential error, where you see one of the following errors:
Error: Salesforce Input (309): 'error': 'invalid_grant', 'error_description': 'authentication failure'
OR
Error: Salesforce Input (309): Traceback (most recent call last): File "main.py", line 71, in pi_initRuntimeError: Internal Error: DecryptPassword - buffer too small
I believe that the root of this problem is that when you enter credentials in the tools on your computer, they are encrypted, not within the workflow itself, but somewhere else within the local computer. Thus, when you upload the workflow to Gallery and try to run it, the workflow is run on your Alteryx server computer and it does not know how to decrypt the credentials.
To solve this, you just need to open the workflow on the remote desktop your Gallery is hosted on and enter your credentials into the Salesforce tools there. By saving the workflow on the same computer it will be run on when ran via the Gallery, you should get around these credential problems.
2. Additionally, I also ran into error handling problems within the Output connector. An example of one of these was when a user would accidentally attempt to push a lead to Salesforce that already existed. With the basic configuration of the Salesforce macro, this causes an error and stops the workflow. I made some adjustments within the macro to simply skip leads already in Salesforce and not throw an error; I did the same for several other errors. Below is the macro with these adjustments:
I hope this helps some of you!
Is this error still happening or was it fixed?
I was not able to get this working, so we are using the Simba Salesforce ODBC driver
