This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Currently - if someone has accidentally kept an excel file open on their desktop, Alteryx will fail to load this flow.
However, it would make more sense to open this file without read-lock as a dirty-read (equivalent of "Read Uncommtted").
This may require some interaction with Microsoft but would be worth pursuing because it prevents / eliminates an entire category of needless canvas errors.
As a workaround, we've started using the run command tool and xcopy to duplicate our inputs before running a workflow to avoid these errors.
it's a good idea @BrianCalvanese - in our server environment we've locked down the use of the run command because of the potential to do damage (either maliciously or deliberately), but this definitely is a way round the file locking issue if you don't have this constraint.
We struggle with this a lot. We use Tableau and Alteryx for different purposes but sometimes use the same source data in an excel file.
Tableau works well with opened excel file and even reflects the changes being made on refreshing while alteryx throws an error on re running (refreshing) the workflow.
Every time save & close the excel to see if the workflow works is a huge annoyance and energy drainer..
This is a limitation on the Excel side, but we will explore whether or not there are better ways to handle it.
Is there a plan or timeline to work with Microsoft to implement this enhancement?
@ARich Understand the dependency , we get reported a lot of user issues due to the locked excel files. A potential fix would be greatly beneficial to our team.
I confirm the problems with Excel files.File is closed but there is some latence in Alteryx reading on the file.
Some Excel writing corrupt the Excel File...
We have dealt with this issue in a few admittedly inelegant ways:
🙂 Hey @seven - agree with you that there are a few ways round this (and in fact, our recommendation internally is to move away from Excel to CSV which doesn't have this same problem although it does have others).
Given that you've found ways around this through forcing the matter using folder security; or custom Python, would you be a supporter of this kind of capability being brought into the main product to aid those who may not be as technical?
@SeanAdamsI would support these capabilities in the main product for sure. The more Alteryx can take off our plate when dealing with Excel, the better and I totally agree with your original idea. The intention of my reply was to jump in with some solutions until the main product can tackle the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.