Thursday, 20 June 2019

#Alteryx19 - Nashville: We turned it up to Eleven!

Can you CReW with the best?

As part of #Alteryx19 we conducted not one, but two sold out CReW macro training classes.  With the assistance of @TessaEnns we demonstrated how to gain productivity through the use of CReW macros.  We delved into some alternative methods for getting to the same results, how to open and investigate the macros along with how to get involved with CReW.

Tessa drove and I was the navigator and tour guide for the sessions.  There were some twists and turns as we fielded questions from the class participants.  We explored existing and new use cases that included questions like:  "How can you make the DISTANCE tool execute faster when applying TomTom drive time distances?"  Our answers included options of:  Don't use it when you've previously calculated that distance (save your results),  Overlay a grid to your catchment (trade) area and calculate the distance/times from the center of each grid rather than from the specific household address, Amp up your memory.

Upon return from Nashville, we've added 5 short YouTube videos explaining the following macros:

If you haven't yet subscribed to my (MarqueeCrew) YouTube channel, please do so.

There's been lots of discussion about incorporating CReW functionality into the Alteryx product.  It's no secret that many of the macros would benefit the product and make it easier on new and existing members of #AlterNation.  These ideas have been officially posted to Community and your vote (star) couldn't hurt:

Elevate Crew Macro Pack support from Community based to Officially Supported
Can we add some of the CReW tools and JDunkerly formulae to Alteryx

Even if Alteryx brings all of the macros to life within the product, we'll likely still be here as a proving ground for new innovation.  As a Minimum Viable Product (MVP) or better, the CReW macros assist in making Alteryx more useful and easier to configure.

Hidden in plain view (at the end of this blog) is a note of caution.  It has come to our attention that the Runner Macros do not run on computers with Windows 10 Enterprise.  If you have overcome this obstacle, please let me know.  There are several posts on community about this and we don't currently have plans to address the functionality.

At Inspire we discussed as part of Build2 the creation of new macros.  Maybe you've already created one of these macros:

  • Summary Append:  Merge the functionality of a Summary and Join tool to apply grouping logic and put the result of the summation (e.g. Total by Group) on each incoming record.
  • Record-Row ID:  Extend the RecordID tool to allow to reset to a starting value (e.g. 1) for every record within a group or set.
If you have feedback on these or other ideas, please comment in the blog or reach out to me directly.



Monday, 14 January 2019

Block All Records

Block All Records

Hold the presses!  The first Alteryx Certified Expert, Jesse Clark has contributed to the CReW macros.  There is simplicity here for all to learn from.  But first, why block all records?  I know that I’ve used the function many times, but how about you?  Have you ever wanted to stop all data from being output?  Essentially, you want to sample zero records.  Oh! That makes everything so clear.  Maybe if I suggest a use case, this will make more sense.

You have an input dataset and want to make sure that the output of your process (e.g. macro) contains all of the fields in the same order as the original file.  You could use the Block All Records macro and stream that into a UNION tool.  Then set the UNION to read #1 first.  It is then up to you whether you will auto-configure by Name or manually configure the data.  The bottom line is that the incoming data fields are in the same order on output.

Another example use case is where you have a list of files that you’ve already read.  If you read this list into a process looking for new files (JOIN with Left output), you might one day want to ignore all read files and rerun the whole set of data.  If you Block All Records, then you’ll end up processing all data as new.

Thanks Jesse for the contribution!