We have discussed on several occasions and in different forums, about the importance of having or providing Alteryx with order of execution control, conditional executions, design patterns and even orchestration.
I presented this idea some time ago, but someone asked me if it was posted, and since it was not, I’m putting it here so you can give some feedback on it.
The basic concept behind this idea is to allow us (users) to have:
This approach involves some functionalities that are already within the product (like exploiting Filtering logic, loading & saving, caching, blocking among others), exposed within a Tool Container with enhanced attributes, like this example:
The approach is to extend Tool Container’s attributes.
This proposition uses actual functionalities we already have in Designer.
So, basically, the Tool Container gets ‘superpowers’, with the addition of some capabilities like: Accepting input data, saving the contents within the container (to create a design pattern, or very commonly used sequence of tools chained together), output data, run the contents of the tools included in the container, etc.), plus a configuration screen like:
This should end a brief introduction to the idea, but taking it a little further, it will allow even to have something like an Orchestration layout, where the users can drag and drop containers or patterns and orchestrate them in a solution, like we can do with the Visual Layout Tool or the Interactive Chart tool:
I'm looking forward to hear what you think.
This has probably been mentioned before, but in case it hasn't....
Right now, if the dynamic input tool skips a file (which it often does!) it just appears as a warning and continues processing. Whilst this is still useful to continue processing, could it be built as an option in the tool to select a 'error if files are skipped'?
Right now it is either easy to miss this is happening, or in production / on server you may want this process to be stopped.
I surprisingly couldn't find this anywhere else as I know it's been discussed in person on many occasions.
Basically the Formula tool needs to be smarter in many ways, but this particular post focuses on the Data Type component.
The formula tool, should not always default to V_String as the data type when entering data or a formula into the formula tool, it should look at the data type and estimate the most likely option.
I know there are times where the logical type might not be consistent in all fields, but the Data Preview and the Function of the formula should be used to determine the most likely option.
E.G. If I type a number or a date directly into the formula tool, then Alteryx should be smart enough to change the data type from the standard V_String to Int, Double or date.
This is an extension to the ideas posted here:
I often need to create a record ID that automatically increments but grouped by a specific field. I currently do it using the Multi-Row Formula tool doing [Field-1:ID]+1 because there is no group by option in the Record ID tool.
Also, sometimes I need to start at 0 but the Multi-Row Formula tool doesn't allow this so I have to use a Formula tool right after to subtract 1.
So adding a group by option to the Record ID tool would allow the user not to use the multi-row formula to do this and to start at any value wanted.
Love the new updates to the Browse tool in 2019.2! However, if you choose the option Open results in new window, which I do often so I can see my whole dataset, the search/filter/sort functionality goes away. Would be great if that new functionality also worked in the new window. Thanks!
Can't wait for the new base maps!
In-app screens, lot of space is wasted because components/tools can just be stacked one below the other.
It would great if we could also insert them horizontally.
Tags : screen, app, macro, layout, tools, UI
When inputting a CSV file via the Azure Data Lake File Storage tool the default behaviour is for the first row to be interpreted as data.
When reading the same file locally using the File Input tool the default behaviour is for the first row to be interpreted as headers.
Since the majority of files will include headers on the first row, it would be helpful to have the "First row contains field names" option selected by default in the Azure Data Lake File Storage tool, and this would also bring the defaults of this tool in line with the standard File Input tool.
Illustration below showing the issue:
The Publish to Tableau Server tool is great.. but requires username and password. If you are using AD, there is a chance that your users don't have a password. In that case, you probably have a technical user that you share across the team. This is not an ideal situation and you loose the governance around the data.
Fortunately, there is an easy workaround. You can leverage personal token authentication : https://help.tableau.com/v2019.4/server/en-us/security_personal_access_tokens.htm
The advantage of this method is that it logs in with your user and your data source is uploaded under your name. This is still using the Tableau REST API so the changes to do in the current macro is MINOR.
Changes to do in the current macro :
1- Add a parameter authentication method with choices : Username/Password ; Personal Token
2- If Personal Token is selected, add two parameters : Token_Name and Token_Value
3 - In the TableauServer.Login supporting macro, improve the formula(13) to change the payload based on user selection. If Username/Password, keep it as is. Else use the syntax here : https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_concepts_auth.htm#make-a-sign-in-r...
This is quite a straight forward change but could help a lot of companies using Alteryx.
Can you please implement that changes to strengthen this tool ?
Thanks a lot,
If you forget to put a name on a new column in the formula tool - the error message is
The field "" is not contained in the record. (Expression #1)
Please could you replace this with a user-friendly message which is self descriptive like:
"Please provide a name for the new column created in expression 1"?
Hi Alteryx community,
It would be really nice to have v_string/v_wstring and max character size as a standard for text columns.
it is countless how many times I found that the error was related to a string truncation due to string size limit from the text input.
Thumbs-up those who lost their minds after discovering that the error was that! 😄
We store valuable data in our MS Teams sites (which are sharepoint folders behind the scenes). Currently, there is no way to connect to sharepoint directly (only if I sync sharepoint to my local drive, which is problematic and doesn't work on Alteryx server).
My recommendation is to have a sharepoint connector which works on both the desktop and server.
The original engine support expanding the formula tool with custom functions either in XML or C++. The new AMP doesn't support these yet.
There is a fair number of user who are using these in E1 and would be good to have this available in AMP
Currently Alteryx does not support writing to SharePoint document libraries.
However there are success sometimes but not at other times.
Please see attachment where we ran into an issue.
See this link for additional information.
We need official support for reading and writing to SharePoint document libraries.
It's an important Output target, and will becoming more so, as Alteryx enhances its reporting capabilities.
I would like to see the Publish to Tableau Server tool updated to include the option of authenticating with a Personal Access Token in addition to Username/Password. The user would be able to toggle the login method and provided the necessary credentials for that method.
When using the formula tool -- one of the nice features is that when you start typing in a function or variable -- the tool will show formulas/variables that begin with that letter and keep changing as you type in more letters. I believe this is called predictive typing.
However, this does not happen in tools like multi-row or multi-field where a user would have to search for functions and variables if they weren't sure what they are.
Can predictive typing be added to the multi-row and multi-field tools? If I want to take it further, any tool that allows a user to use the formula functionality should be able to see predictive typing.
Single point of maintenance for Salesforce Input tool connection to Salesforce
This prevents user maintenance every time their password (and token) changes which requires them to update every Tool with new credentials
Also logged as issue under Alteryx, Inc Case # 00252975: Connection to Salesforce Issue
On shared collection , users have access to the collection shared by other team members. When users copy the ‘Publish to Tableau Server ‘ tool from one workflow to another it copies with the credentials embedded in the tool as well.
As user John Doe’s workflow publishes data on to tableau server with Peter’s credentials as the publish to dashboard tool was copied from Peter’s workflow.
The concern really is Users copying tools from one workflow can really copy the credentials as well. Enhancement to the publish to Tableau tool would be much appreciated.
Tools within a workflow needs to be able to run in parallel whereever applicable.
For example: Extracting 10 million rows from one source, 12 million rows from a different source to perform blending.
currently the order of execution is the order in which tools are dragged into the canvas. Hence Source1 first, Source2 second and then the JOIN.
Here Source1 & Source2 are completely independent, hence can be run in parallel. Thus saving the workflow execution time.
Execution time is quite crucial when you have tight data loading window.
Hopefully alteryx considers this in the next release!
Well, the title is pretty simple : it appears that the tendancy right now is to have web version of any software on a server.
A few notes about that :
-a lot of Alteryx competitors are already in this mode and it's hard to sell you're still with a desktop-only mode for design, even if the product is far better.
-a good idea is the one used by Qlik with Qlik Sense : they still have a desktop and a web version of Sense but the desktop works mainly as an hidden browser plus an engine. The web version is cool too because you can make your own application, or your own data connection etc..
-the main interest of a web implementation of Alteryx would be to reduce installation on client computers (and that means packaging the installer, managing the data connection, the paths, the access to macros... etc) and to have a better control of the users.
PS : this idea is soooo simple and so obvious I'm surprised I didn't find it. It may be a duplicate.
The idea is to store credentials, login/pw in a "credential alias".
Then, those credential aliases can be used in :
-in database aliases/connection
-on user aliases for connected controllers/gallery
The idea is that I only have to change the credentials once for all the connection type (on Hive, I have the in db alias, the traditional alias and even an HDFS alias using exactly the same credentials !! and I have to change all that manually).
Microsoft Office provides a facility in all its apps to make the loading of frequently used files a breeze. In the FILE OPEN function the user can "PIN" a previously opened file so that it is always easy to find and load. This would make it easier to manage and retrieve Designer files.
This is what PINNING looks like in Excel
The lack of home use / learning editions of Alteryx is a serious mid-term competitive threat factor for Alteryx - and it's well worth both this Alteryx community; and the Alteryx Community Management team making this a key priority for the Alteryx platform.
The BI/Data science space is very competitive (as evidenced by the recent Gartner 2016 Magic Quadrants), and although Alteryx was given very favourable review in some factors - there were serious concerns about licensing costs; and time to productivity.
Clearly - Alterxy succeeds in direct proportion to the size of the active user base - so the question is "How do we increase the licensed / deployed user base" and I believe that there are 3 factors which all relate to the issue of learning-edition alteryx licenses.
a) Time to productivity: Right now - I cannot ask one of my staff to learn Alteryx at home and prove their capability before paying several thousand dollars to give them a license. Once I give them a license; it then takes them 2-3 months to become productive, and we run the lottery of finding out whether this person was a good fit for this kind of role in the first place. Solution: Make Alteryx available in a learning edition at home with a robust certification program; and a learning progression built in - that way I can tell my staff "I will give you a license once you demonstrate your competence by learning to this level". How does this help Alteryx: lower time to productivity = more attractive product
b) Size of committed user base: As tech professionals - we take our tech bias with us to our new role (the "Affinity effect"), and often will have some leverage in tool selection. The more people know Alteryx and are invested in their Alterxy skill set - the greater this "Affinity effect" will start to show in sales figures. This also makes the tool more sticky, reducing the defector population if users can see and use latest features at home.
Solution: Give the learning edition away for free - Pentaho spoon is currently free for learning; as is Tableau Public; and MS Power BI is incredibly cheap to learn. If Alteryx doesn't do this - others definitely will anyway, and this "Affinity Effect" will be washed out.
c) Increase the skill pool in the market: The more wide-spread the skills are - the more likely I am to purchase a toolset. So - if Alteryx skills are very broadly available in the market - it's easier to make the purchase decision for Alteryx rather than competitors. However - right now the skillset growth is severely constrained, so Alteryx is making the "Buy Alteryx" decision needlessly harder.
Solution: Make Alteryx available for training; learning; & Certification for free.
Note: Although this is directly contrary to my personal interests in the short term (the smaller the number of people with skillX, the higher the market value), it is also long-term selfish because I will be able to increase the impact within my firm by having access to a greater pool of skilled and instantly productive workers in the market.
Although price may be an issue - this is a separate matter. I believe that Alteryx can do a lot to create future sales pipeline, and a committed and very sticky user base by providing this home-learning & certification program. In my mind - this is probably one of the biggest competitive opportunities & threats facing Alteryx right now, given the velocity of this particular industry & segment.
I'd be very happy to talk this through in detail with the Alteryx team if that's helpful (just PM me)
I recently came to know that Alteryx doesn't support Denodo Data sources. We at our company are using Denodo as a data virtualization tool and also Alteryx is used for data blending. The request is for Alteryx to start supporting Denodo as a data source so that our company can reach out to Alteryx for any support related issues with Denodo.
Adam ( @AdamR ), Mark ( @MarqueeCrew) and many others have done a great job in putting together super helpful add-in macros in the CREW pack - and James ( @jdunkerley79 ) has really done an incredible job of filling in some gaps in a very useful way in the formula tools.
Would be possible to include a subset of these in the core product as part of the next release?
I'm thinking of (but others will chime in here to vote for their favourite):
- Unique only tool (CReW)
- Field Sort (CReW)
- Wildcard XLSX input (CReW) - this would eliminate a whole category of user queries on the discussion boards
- Runner (CReW - although this may have issues with licensing since many people don't have command line permission - Alteryx does really need the ability to do chained dependancy flows in a more smooth way.
- Date Utils (JDunkerly) - all of James's Date utils - again, these would immediately solve many of the support questions asked on the discussion forum
I think that these would really add richness & functionality to the core product, and at the same time get ahead of many of the more common queries raised by users. I guess the only question is whether the authors would have any objection?