Advent of Code is back! Unwrap daily challenges to sharpen your Alteryx skills and earn badges along the way! Learn more now.
Free Trial

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

INDB record counts popup

Dear Users, Fans, Compatriots, and Fellow Alteryx Nerds:

One of my favourite parts of using Alteryx is that in all the in-memory tools, there is a quick-and-dirty count in each of your tools' output nodes. You know, you use these all the time and when you switch back into SQL, you get frustrated with having to run the query two or three times just to see the count in each of your join outputs. 

One thing I'm missing as an INDB user is that I have to employ a manual workaround to see what is happening. INDB tools are a bit black-box in that we don't see the counts.

All I want...All I want...

 

 

I've been using this workaround for a little over a year now and I haven't found it to be incredibly taxing on my resources, so I'm wondering if Alteryx may be able to look into doing this on the back end to make the INDB experience that much closer to the in-memory experience. I just want those numbers above; I don't need to know the byte count, just the record count.

What I need to do to get itWhat I need to do to get it

 

Now, I imagine this is not implemented already for a Very Good Reason. But, enough is enough! Let's shoot for the moon and make this tool all that much better!! Anyone with me?

 

-Cedric Justice

Cambia Healthcare

 

12 Comments
thedr9wningman
8 - Asteroid

I understand the potential concern, @simonaubert_bd, but I’m doing this anyway on the side, and the cost seems to be minimal. It seems to me it would be nice to have the option (in the tool itself) and if there was too high of a cost, then there could be a global means to turn off the counts.

I’m not angling for it to be a default, but just an option. I understand it requires rendering the query; perhaps I have a fast DB environment, but I have found that the impact is minimal on the time it takes for me to report these metrics out versus running it without the count. Either way: I’m after the visibility while I’m developing a workflow—after development, I likely don’t need this. It is just a weird workaround I feel I need to do to do something that is very natural in Alteryx.

AlteryxCommunityTeam
Alteryx Community Team
Alteryx Community Team
Status changed to: Accepting Votes