In Alteryx, the Salesforce connector is very useful to easily import raw data from Salesforce using its wonderful API. All you need to input is the email and password for a API enabled user login, as well as the Security Token.
The connectors are so convenient to combine SFDC tables, that you will quickly have several within a single workflow, and you will most likely have several workflows, that you spent countless hours to configure, as Salesforce tables can be VERY long. For instance, you must select the proper combination of fields to extract, as Salesforce tables, especially the custom ones, are laden with open text fields, useless for analytics in most cases. Those open text fields are input with very few restrictions of characters and will often trip S3 or your database.
There is just a slight issue with this design: on one hand, the SFDC credentials you did input are stored locally in each connector object you deploy, on the other hand, most SFDC logins require episodic password changes as they are set to expire. And should that happen, you will have failing workflows, unless you tirelessly inventory the location of each and painstakingly process to edit them. In my experience, that is not the end of the suffering: when you click on the connector to go edit the credentials, Alteryx Designer sends a request to SFDC featuring credentials, and after a few of those requests, sometimes just a handful, SFDC will lock your login out! You will then need to either get an admin to unlock the account, always a fun conversation to have with an admin, or wait one hour for SFDC to automatically remove the lock.
Continue reading