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.
Right now the PublishToPowerBI connector only publishes to "My Workspace." I manage datasets that feed reports for multiple workspaces, some of which are not necessarily personal workspaces (so there is no login associated). A drop-down that lets you select which workspace, that you are a member of, would be fantastic!
The workaround right now is to ETL in Alteryx then save the dataset out to OneDrive. You can then "Publish" the Excel sheet to Power BI natively, and the data refreshes once an hour. This works for some data, but we have use cases that need refresh rates much higher than that. Plus publishing directly to Power BI would be ideal.
I'd like to see Alteryx allow a second install of your license on a second, personal machine. Tableau allows this and IMO is why there is such a robust online / blog community around that product.
For those of us that work at mid-size to large organizations, there are often strict rules governing internal data and use of cloud-based data sources. If I discover some new trick I'd like the share with my fellow Alteryx analysts outside of my company, I have no clear way to do that the same way I can with Tableau where I can do it at home not using my company's data.
Being able to learn new features and test things out on commonly available public data (ever notice that Superstore data set everyone who gets Tableau has?) would accelerate what we're able to do with the community site here and the larger analytics blogging community.
This got me to think a little more about localized logging options in Alteryx.
At a high level, there are ways to accomplish this in Designer at a User or System level by enabling a Logging directory and then parsing those logs with a separate Alteryx job. However, this would involve logging ALL Designer executions, which seems like it may be overkill for this need. A user can also manually save a log after each execution, although this requires manual intervention.
I think adding an option in the Runtime settings for Workflow Configuration to Enable Logging and (optionally) specify a Logging directory would be a great feature add for Designer. In my opinion this should not apply once a workflow runs on Server (Server logging should be handled in a fully standardized way), but should apply to designer "UI" execution. Having the ability to add a logging naming convention (perhaps including a workflow name and run date in the log name) would be icing on the cake.
This would allow for a piecemeal logging solution to log specific flows or processes that might be high visiblity or high importance, while avoiding saving hundreds or thousands of logs daily of less important processes, and of dev test. It would also reduce or eliminate a manual process to save these logs individually.
I work as an accountant for one of the nation's largest firms. In my day-to-day work, I utilize alteryx to cleanse and format data provided by our clients in preparation for use in another program that is very specific with its imports.
I was recently reviewing an Alteryx workflow prepared by a colleague. Upon attempting to run it again (with new input data) I noted some data fall out and am now reviewing the workflow tool by tool (first to develop understanding of the developer's mind, and second to make changes where needed).
During this review, I thought it would be very cool to have a Review/Markup view, where each tool could have a checkbox that could be checked/unchecked if that specific tool was reviewed/unreviewed. There could also be a circle function that could bring attention to specific places that are of concern in a workflow. This might work similar to how when one drags an Interface tool on the canvas, appropriate connections above non-Interface tools appear, only it would be a view that could be turned on/off.
In addition, I have a tendency to annotate the heck out of my workflows I create -- however there isn't really a way for reviewers to do this without modifying the workflow annotations nor adding a Comment tool with comments. It's especially difficult to do the later since space might be tight. Having a comment function that only shows up in the Review/Markup view would be amazing and very appreciated as I don't want to visually alter the workflow to accommodate such comments if it can be helped.
It would be even more helpful if a review/markup report (maybe a temporary PDF or .yxdb) that would summarized what was summarized as "reviewed, with no comments", "reviewed, with comments', "unreviewed, with comments", "needs attention", etc.
Lastly, with regards to fallout data, I would like to tag/trace a record and, after running the workflow, have the last location of that record be circled in red (or some other visual cue) on the canvas. Currently, I just create a "Flag" column (or, if it works, track a specific RecordID in Alteryx and follow my best guess of where the data may have fallen off -- something that can be very time consuming when I'm not familiar with the workflow.
The organization I work for has experienced some of the best time savings from Alteryx and currently supplies licenses to our staff members. In particular our Audit function may need to review some client processes, which may be entirely in some part Alteryx. As our managers attain Alteryx familiarity, they may also want to review our workflows for completeness and data integrity purposes. Having these functions above would definitely be something to look into and would further drive the review function further away from other more archaic programs and increase our usage of Alteryx throughout, and I'd be happy to be part of a testing for this if possible!
I collaborate with a team using Git. We commit all of our work automatically with the exception of the Alteryx Alias file. It must be moved manually into the repository and then other teammates must move it out of the repository manually into their local folder and overwrite the old file. This is not an enterprise-friendly solution. If we could configure the location of the Alias file in Designer, we could set it to live in the repository. That way, everyone could automatically have the latest file with tracked changes. Please create this functionality. Thank you.
I know this has been suggested before, but it would be great if calculations and transformations could be cached between workflow executions. Perhaps the browse tools could be configured as caches. Any spot that has a browse tool fixes the value of that node between runs provided that there are no upstream tool changes. The cache could be optional (or flushed) to allow for dynamic input data that could change between executions, even if the tool chain didn't.
Please extend the Workflow Dependencies functionality to include dependencies of used macros in the worflow too. Currenctly macros are simply marked as dependencies by themselves, but the underlying dependencies (e.g. data sources) of these macros are not included.
We have a large ETL process developed with Alteryx that applies several layers of custom and complex macros and several data sources referenced using aliases. Currently the process is deployed locally (non-server) and executed ad-hoc, but will be moved to the server platform at some point.
Recently I had to prep an employee for running the process. This requires creating aliases and associated connections and making sure that access to needed network locations is in place (storing macros, temp files, etc.). Hence I needed to identify all aliases and components/macros used. As everything is wrapped nicely by a single workflow, I hoped that the workflow dependencies functionality would cover dependencies in the macro nodes within, but unfortunately it didn't and I had to look through the dependencies of 10-15 macros.
When creating a workflow I generally open a "TEMPLATE" first and then immediately save it to the "NEW WORKFLOW NAME". My template includes all my preferences that aren't set naturally within the user settings and won't get RESET by them either. It has a comment box and containers as well as logos and copyrights. It would be nice to have ready access to this feature. Maybe others have standards that they want applied to all users and their workflows too.
I've come across multiple requests for help that relate to dates. Having to know that "2016-05-04" is the only way to get May 4th, 2016 into a date field is sometimes a challenge for new users. When they begin to use date functions and now have to learn adding and trimming etcetera the complication factor increases. Then we date time format and have to do all of this in English (my one and only language), makes me think that there is room for improvements.