Hello, community:
I have a pretty strange problem that I need to discuss to see if there is a fix for. Let me set things up with a little context.
Context
I work in a small team; there are three users and we often work on Alteryx flows in tandem. The newest member of our team was exploring and learning about our new flows, but if he tried to run them, they would result in an error. We've come to the strange conclusion that it is because he's using Windows 10 and the other two of us are using Windows 7.
The Issue
I have an illustration of this. But here's the short synopsis: When a Windows 7 user opens a workflow and it writes to a database, in Windows 7, the configuration options retain our last known state in Alteryx. Most of the time, we're doing an 'Update, insert if new' or the driver-equivalent of that.
Our poor Windows 10 user will open the same workflow from the same location immediately after a Windows 7 user saves it, and the output tool defaults to 'Create a new table'
If he runs that flow without explicitly changing the output tool, he receives an error message. Worse yet, if he saves the workflow unwittingly, it will throw an error when we schedule the workflow as a part of a larger batch of jobs we run. So, essentially, he's off-limits to saving workflows or even opening certain workflows currently due to this strange bug.
Here are pictures:
Windows 7 view
Windows 10 view of the same file
Additional details
While the example above is using the Teradata bulk loader protocol, the same issue happens if the Windows 10 user is using an ODBC protocol.
Has anyone had this problem before? And, better yet, does anyone have a solution or workaround?
Our current plan of attack is to downgrade the user to Windows 7. We have some other issues with Windows 10 that necessitate this. But I thought I would bring it up to the community to alert Alteryx to this problem as well.
Thanks,
Cedric
