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
Often as I am scraping web sites, some clever developer has put an invisible character (ASCII or Unicode) in the data which causes terrible trouble.
I've identified 89 instances of zero-width or non-zero-width glyphs that are not visible and/or Alteryx does not classify as whitespace. There are probably more, but Unicode is big y'all.
Unfortunately, the Trim() string function only removes 4 of these characters (Tab, Newline, Carriage Feed, and Space).
REGEX_REPLACE with the \s option (which is what the Cleanse macro uses) is a little better but still only removes 20. And it removes all instances, not just leading and trailing.
I've attached a workflow which proves this issue.
@apolly: this is what I mentioned at GKO.
And I did see this post (https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Elegantly-remove-all-ASCII-characters-...), but it's too brute force. Especially as Alteryx is localized and more users need those Unicode characters.
I see many posts where users want to view numeric or string data as monetary values. I think that it would be friendly to have a masking option (like excel) where you could choose a format or customize one for display. The next step is to apply the formatting to the workflow so that folks who want to export the data can do so.
In the Report Map tool - you have the ability to select units - KM vs. Miles
You also have the ability to put a map buffer around your zoomed points - either in % or distance.
However - if you've selected your units as KM - the "Expand Extent" is still in Miles - see picture below.
Please can you make this consistent?
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.
A problem I'm currently trying to solve and feel like I'm spending way too much time on it..
I have a data set which has some data in it from multiple languages, and I only want English values. I was able to get rid of the words with non English letters with a little regular expression and filtering. However, there's some words that do contain all English letters but aren't English. What I'm trying to do is bring in an English dictionary to compare words and see which rows have non English words according to the dictionary. However, this is proving to be a bit harder than I thought. I think I can do it, but it feels like this should be much simpler than it is.
It would be great to have a tool that would run a "spell check" on fields (almost all dictionaries for all languages are available free online). This could also be useful also just for cleaning up open text types of data where people type stuff in quickly and don't re-read it! 🙂
The Render Tool for creating reports like PDFs etc does not function if any of the table data it receives contains an accent or special character,
It also doesn't work if you want filenames output with accents/non-english characters.
So forget about reporting in proper representations of German/French/Swedish/Irish/Russian/Chinese/Japanese.
This is a bit surprising and needs a note in the render tool documentation also!
Can you fix this feature please!
I suggest to add the functionality to parse date strings containing non-English month/day names into Date format
Maybe by detecting the display language of Windows or the language of the DateTime format in Windows settings.
For example, right now in Alteryx, DateTimeParse('July 2008','%B %Y') works fine, but for French month name, DateTimeParse('Juillet 2008','%B %Y') returns null !
and when calling DateTimeFormat(DateTimeNow(), '%B') we would like to have "Juillet" instead of "July" for French version of Windows/DateTime settings.
Right now, we need to use workaround solutions like SWITCH to solve this issue!
With more people moving into urban developments, it would be helpful to allow analysts to measure customers within a "walking distance". Similar to drive time analysis, a step up would be to incorporate "walk time" analysis.
As you may be aware localisation is the adapting of computer software to regional differences of a target market, Internationalization is the process of designing software so that it can potentially be adapted to various languages without engineering changes.
The idea is to make Alteryx designer tool, the web help content and example workflows to be multilingual (Possibly with the use of "lic" language files or similar) Hopefully the sotware and tutorials will all be localised by crowdsourcing initiatives within the Alteryx community.
I sincerely believe this will help the tool get a lot of traction not in US and UK but in other parts of the world,
Highly likely Mandarin and Spanish would be the first two language versions...
Top languages by population per Nationalencyklopedin 2007 (2010)Language Native speakers(millions) Fraction of worldpopulation (2007)
My system's regional settings are German that uses a different decimal symbol and digit grouping than an English system.
Frequently I need to copy data from a browse tool in Alteryx to Excel to create a quick chart or further analysis; this often includes float or double data types.
Instead of the in my case correct ',' as decimal symbol, Alteryx uses the English '.', hence would cause incorrectly pasted values in Excel.
Always using an Excel file as output data is time consuming.
The request is: Make Floats and Double aware of the systems regional setting for copy and paste out of results.
Hello Alteryx, Please fix Salesforce Input and Output tools.
The input tool has a lot of issues with Login , , Custom SQL, Json issues, Machine Encryption, and saving to the gallery , .
Unable to use Crew macros with Salesforce input Workflows etc.... there is a lot of post's with all the issues with Salesforce V.1 Versions.
The layout of tables in the Visual Query Builder should be persistent. The placement, made by the user, should be persistent when called-up again.
I´ve looked in the forums, and the idea is new. It would be great if there would be an option to make it possible to give tooltips when writing a formular yourself not only in the "basis-language of the installation", but also in e.g. english (as Lingua Franca). The reasoning: in Excel or Tableau I know many a command in only one language - and have to undergo a timeconsuming process of A) thinking AND B) looking it up in the language you have to use at that project.
Even Tableau does not offer this - and you have to create a lot of calculated fields. Alteryx could gain in UI-friendliness...