Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesHello all,
This may be a little controversial. As of today, when you buy an Alteryx Server, the basic package covers up to 4 cores :
https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/How-Alteryx-defines-cores-for-licensing-our-products/ta-p/158030
I have always known that. But these last years, the technology, the world has evolved. Especially the number of cores in a server. As an example, AMD Epyc CPU for server begin at 8 cores :
https://www.amd.com/en/processors/epyc-7002-series
So the idea is to update the number of cores in initial package for 8 or even 16 cores. It would :
-make Alteryx more competitive
-cost only very few money
-end some user frustration
Moreover, Alteryx Server Additional Capacity license should be 4 cores.
Best regards,
Simon
The Inputs to an Alteryx App look very clunky and are not formatted well on the Gallery. The App Inputs look fairly decent when executed from Designer, but the Gallery input tabs looks like a work-in-progress that never got out of beta. We desperately need some way to make the app input tabs aesthetically pleasing and functional. An "artisan" does not like to create a masterpiece app that has a Model-T front end.
Gallery Scheduler can schedule the workflows recurring,custom and once.
Idea 1 : Incase the scheduled run fails it would be good to have an retry option incase the source file path has network latency or network glitch.
Idea 2 : It would also be good if the scheduler checks if the latest feed or file is present in the source file path and have an option to kick off to run job the moment the latest file is present.
Idea 3 : For workflow to run on start and end of the working day month date we currently do not have an option in scheduler. we have an option to choose the first day and last day but the first and last working days in a month.
Idea 4 : When we choose the replace workflow option that changes the version of the workflow on gallery the schedule automatically is disabled. We will have to manually enable the schedule and also re-enter the credentials which is difficult if we keep updating our workflows every time with new changes as per business needs. request to have the schedule option enabled incase the replace workflow is done and also not to erase the workflow credentials.
We are constantly moving workflows from our Dev environment up to Prod and then back down again to improve them. Even though we only used Gallery shared data connections, and both environments have the same name for each connection; the connections still break when opening the workflow in the other environment. This is because designer actually uses an ID code behind the string name instead of the name. And, even though connections exist by the same name in each environment, the code behind them is different.
I would like a way to be able to specify the data connection code so that I can make the code the same in both environments.
We have a bunch of workflows in our public gallery that have no inputs, and so the results are the same no matter who runs them, it just depends on the time. It is a huge oversight and a massive waste of resources that a person can only see workflow results for the times that one user ran the workflow. If I have user A run a workflow at 10AM and user B doesn't know about it, he's going to run it at 10:05 AM and we just wasted valuable compute time and resources to produce the same exact data set.
Or, say it runs on a schedule, and you want people to access the results via gallery instead of saving as spreadsheet or something somewhere. But you can't. Only the person who setup the schedule can see the results.
Now, I can see that some workflow applications may produced different results based on inputs, and some results may be sensitive. But then at least make it a check box when publishing the workflow to gallery whether or not results should b shared globally.
Right now we can set the limit of processes a worker can run and each worker will ping the controller when a slot is available so that it can assign a new process. However, this is not efficient and you can truly load balance because you don't know how busy that worker acutally is...
We need a way that might be simliar to how we do on DataStage GRID environment where the LSF platform balances that workload across the entire GRID.
Currently it takes four clicks and three displays (including the current scheduler display I'm attempting to post as well) just to temporarily disable a job. It would be so much more convenient if there were a one touch icon on this display that allowed you to do that function.
Hi All,
The limit of data connections in Alteryx Gallery is 100 only.
Is it possible to increase the limit ?
Best Regards,
Samuel
Option to update ownership to any other valid license holder as needed.
Use Case: Currently the canvas owner is marked by default as the user publishing the canvas to production.
However, we have seen instances where the person moves teams and would like to hand it over to another person.
I wish Alteryx had an Alteryx gallery not only for workflows but for pure data sources as well which we can access with;
And I would like to be able to get weather data as a starter;
But especially the most needed aspects are;
Obviously 5 day 3 hour forecasts for all these aspects are another thing and probably this will generate some revenue...
This information is so essential in order to accurately forecast
Mathematica (since version 7) and wolfram has this built in already!
https://www.wolfram.com/products/mathematica/newin7/content/CurrentAndHistoricalWeatherData/
http://demonstrations.wolfram.com/symbol.html?symbol=WeatherData
This is the source of data; http://reference.wolfram.com/language/note/WeatherDataSourceInformation.html
Totally agree that maintaining a data source covering worldwide is not an easy task but I think will help Alteryx users and customers a lot...
We've purchased a server license and several designer licenses to publish analytics apps to customers via our internal/company gallery. Whether a user signs in or not, users should not be subjected to corporate Alteryx ads. This is a terrible user experience and detracts from our ability to deploy self-serve solutions.
Hello,
Looks like the user inputs (check boxes, free text fields, drop downs, file uploads etc., ) to the app are "temporarily" stored during the course of the app "Run" time. These - especially the "uploaded files" get deleted from the temporary folder after the successful run of the workflow.
Ex: user uploads 2 files to the app as inputs. see attached interface.
It is important that the user selections are persisted on the alteryx server for debugging, investigation, audit trail purposes.
Of-course - there are workarounds by some extra code/logic within the app. But - in-order for the "server" tool to be considered as robust/industrialized - it is critical to "log" the user interactions on the server side.
Is it something already looked into?
Regards,
Sandeep.
Hi
My idea is to facilitate scheduling through Gallery vs the separate scheduler built into Designer. The reasons for this:
Thanks,
Ryan
As the single user who upload workflow MYWorkspace ends up being very crowded. I move them to collections to be able to share but on My workspace, I can not see which collection they are associated to. It would be nice if there was a column displayed that showed associated collections. As well as being able to have some different types of category classification. I would want something like a development stage: (In-progress, UAT level, deployed, retired) If they are retired a way to remove them off my general workspace area.
The current Alteryx user interface is displayed in a vertical orientation without the option for customization. To optimize space efficiency, it would be highly advantageous if the filters could be arranged horizontally, as depicted in the attached figure.
Additionally, there is a usability issue with the options list for interface tools like the list box. Currently, all options are displayed without utilizing a dropdown, requiring users to scroll extensively when multiple tools with numerous options are present within a single analytic app. Implementing a dropdown functionality for improved navigation would significantly enhance the overall user experience.
Option to Zip All Outputs
For workflows that produce various different output files, I think it would be nice if the Gallery had the functionality to create a single zip file containing all outputs. The user would opt in or out of this functionality using a checkbox in the Gallery workflow settings (for apps, this checkbox could also appear as an additional setting above "Questions"). After the workflow has been run, the user would only see the zip file in the output preview instead of each individual output file.
This functionality would create a more user-friendly experience as it would eliminate the need for zip file creation workarounds, such as using the Run Command Tool or the "zipfile" Python library to create zip files (these options also do not generate a zip file in the Gallery output preview).
Hi,
I have an existing app in my company's gallery. I updated the app in the gallery to not allow others to download. I just made changes to the desktop version of the app and saved it to the gallery, then went thru the steps of replacing my existing gallery app with the new version (this part I like). BUT, after updating the app, when I went back into the app settings, the option for others to download was checked again. To me, the app should inherit anything that was manually done to it in the gallery, like making it not downloadable. Is it possible to have this changed in a future release?
Thanks!
Aliases are a really powerful tool, particularly when you have multiple environments (EG Test, Prod) and need a published workflow to work without any code changes (In particular in an IT or Release/Change Control model). By configuring a system alias on your Test and Prod servers, code will dynamically point to the correct server.
However, aliases can be somewhat cumbersome if you have a lot of databases on a server, and those database names change by environment. Effectively, you end up needing an alias for each Database, which runs into naming convention and standardization issues.
Having the ability to configure a "database value" or a "database alias" would do a lot to help this. This could either be a file that would be attached (allowing for easy config changes without risk of modifying the underlying code structure) or a secondary tier of aliases, so that a connection string might go from:
aka:SQLSERVER (contains sqlserver and database information)
to:
aka:SQLSERVER||aka:database - so that at runtime Alteryx would evaluate the SQLSERVER alias and the database alias to create the correct connection string for that environment.
We have groups asking within our organization for ways to check the status of a running workflow in Gallery. They are wanting to understand which step in the process the workflow has completed for longer-running workflows.
They are looking for an experience similar to when running in Designer where they can see which tools have been completed. At the very least, they would like the log to be reported live and not shown at the end of the run.
Currently, the run feels like a black box where they do not know how close it is to completion or which steps it has made it through.
We have tried to build workarounds like the Email tool, but have been unsuccessful. For example, the Email tool does not send an Email until the workflow completes which defeats the purpose. The closest workaround is writing our own log along the way that can be reported on which is not a clean solution.
Hello, Alteryx users,
My idea is simple but would make things way easier for the analytical app users on the Gallery.
Currently, the order is ascending and we can see all the files from all the applications we have run before.
It would help a million to see the most recent files first and only see the files related to this workflow.
Thank you,
Fernando Vizcaino
Currently, DCM credentials appear to only be used in combination with a DCM Data Source.
For ease of use for my end users (non-Designers), I would like my end users to be able to save a user ID and password as a standalone DCM credential. Then, I want the user to have the option to select that credential for use in two places:
Having this functionality would remove administrative burden from both our Designers and the end users they support.