Alteryx Designer Desktop Ideas

Hello Alteryx fans and Devs!

For the Summarise tool - would it be useful to have a "Rank" option for the potential Summarise options we can use? Just a thought!

For example, allowing the letters in front of the column titles to be formatted differently to make them stand out on a report. 

Hi 

1:
I'm from Denmark, and like several other european countries we use commas instead of dot as decimal seperator. And we use dot as thousand seperator.

So if im working in a flow with loads of price fields, lets say cost price, amount per unit, amount and amount including vat i need to do a multi field replace. Else I dont get the output i can work with in excel or other programs.

So it would be great beeing able to set seperators on a flow level, like you can in excel when importing.

2.
Beeing able to set a date format on a flow level.
Lets say my input data is 12.12.2019 and i need 2019-12-12 in my output. If i work with several different date fields i need to use several datetime fields.
Alternate could be a multi field datetime ? 

3.
Having a search function when using the select ? And maybe a numbers order.

So if i scroll down, i could enter 3 - which means this would now be my 3. shown field? 

recently loaded the new V11 and gettting used to it.  one immediate gripe is the new version of the Formula Tool no longer supports multiple field actions.  In the prior version I could change Data Types on many fields at once.  I could move multiple fields in a block at once.  there were a few other things but these are things I am sorely missing on my first use of V11.  I created about 20 fields in quick succession just getting names down and then going back and putting in formula which were variations on a theme.  When done I noticed the default DataType was V_WString and I wanted integer.  In the past it was no big deal because I could select the block or interspersed fields and then right click to change data type for all to the same data type.  it was very handy and now appears to be gone.  please bring these things back.

Hi All,

I believe the following would help improve the functionality of Select Tool.

The idea is to have a defaulting option for each of the field in the Select Tool (which I believe should be a light weight Tool i.e. not adversely impacting performance and gives best exhaustive picture of all columns flowing through a (/particular point in ) pipeline).

Following are some of the cases where defaulting might come handy -

1) Fields which are supposed to hold monetary data - instead of Null, one can put 0.00 to help roll up summary properly.
2) Fields which are supposed to hold dates (say expiry date) - instead of Null, one can put some enterprise standards like 31-12-2099 to avoid mixing Nulls and 31-12-2099.
3) Fields which are supposed to hold purchase quantity/number of employees/number of merchandise - instead of Null, one can put 0 (and not 0.00) again to help with roll up summary.
4) Fields which are supposed to hold Currency - instead of Null, one can put USD.
5) Fields which are supposed to hold dates (say this time create date) - instead of Null, one can hardcode actual date, or an additional feature to put Now() kind of functions.

At present one of the options of achieving same might be to put a Formula Tool and to code whatever is desired inside the Formula Tool.

Benefits of having the functionality inside Select Tool would be -

1) It would be more user friendly and call for faster build to just write '0.00' or 'USD' or '31-12-2099' as compared to writing IF IsNull()... statements.
2) Inside Formula Tool, user needs to pull desired fields from the drop down and hence exhaustive view of all fields passing through pipeline is not available.

Pain in selection of fields from drop down and writing actual formulas might be aggravated with the number of columns increasing and might be more prone to human omission related errors.

Thanks,
Rohit Bajaj

Hey guys!!

I was just thinking... they might not need to fully build out a python ide, but could still reach the same objective.

You should be able to keep a python file on its own and call it in r.  By doing this, you might be able to have the json/xml handling of python with the visual/stats power of R while it being nicely bundled in your workflow.  This uses base functions in r and does a good job turning a pandas dataset to an r dataframe you can move along your workflow.

You could always just use this same idea to write a file somewhere and once it's written, your workflow will continue.  If you do, the code is literally 1 line in r...  Anyway, let me know your thoughts! 🙂

Will this work for your organization?

https://www.linkedin.com/pulse/using-python-r-windows-7-subhash-jaini?trk=hp-feed-article-title-publ...