Found a minor bug in the Alteryx Connect Salesforce Loader..
I kept getting errors trying to run this app and wanted to share the quick fix if anyone else was having similar troubles. A version of the application is attached to this post that contains a proposed fix/workaround.
The bug is specifically within the REGEX_Replace() expression in the formula tool (tool ID #4) for the field "SOAPGetTokenURL". The formula simply alters the user's instance URL (https://[instance].salesforce.com). However, it will result in errors when a user's intance is at a subdomain of another subdomain.
For example, take my organization's salesforce instance:
https://bcbsnc.my.salesforce.com/
The current formula in the tool for SOAPGetTokenURL will yield an incorrect URI, like so:
https://bcbsnc.salesforce.com/services/Soap/u/40.0
...because the REGEX_Replace() expression replaces any character after the first period before appending the root domain and endpoint. Here is the current formula along with a proposed working solution. I'm not great with regular expressions so I'm sure there's a better way...expecially since the original formula is probably trying to help mistypings of salesforce.com
\\ current 'https://' + REGEX_Replace([URL], '.*(?://)(.*?)\..*', '$1') + '.salesforce.com/services/Soap/u/40.0' \\ a working solution 'https://' + REGEX_Replace([URL], '.*(?://)(.*?)\.salesforce\.com*', '$1') + '.salesforce.com/services/Soap/u/40.0'
\\ or you could just trust that user provided good input for the URL like all of the other field's formulas do..
[URL] + '/services/Soap/u/40.0'
Again, working app version attached..
If it's at true bug I don't think it should be a product idea, I think you need to submit it to support@alteryx.com
Ben
Sure thing, thanks @BenMoss
Thx for reporting, it's already in our development backlog and will be fixed soon.
Ondrej,
Connect Team
Whats up with all the bots that keep starring this??
Hi @Coxta45,
We are going to investigate, thanks for mentioning.
It appears you were the target of a most wholesome spam attach wherein the spammer wanted to shower you with affection.
We've resolved the issue, and if you run into any future wholesome spammers please let us know.
Thanks for all you do and happy 4th!