Missed the Q4 Fall Release Product Update? Watch the on-demand webinar for more info on the latest in Designer 24.2, Auto Insights Magic Reports, and more!
Free Trial

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Crew Macro Add Totals: No field selected for row totals ERROR

mithily
8 - Asteroid

I am using the crew macro but keep getting this error:
No field selected for row total? Can you please help

9 REPLIES 9
echuong1
Alteryx Alumni (Retired)

Looking at the underlying macro for this tool, it will throw that error if nothing is selected for the row total label. Can you check to see if you have something selected in here? 

 

echuong1_0-1599743985706.png

 

echuong1_1-1599744043967.png

 

 

mithily
8 - Asteroid

When I look at that drop down there are no values in it, so I cannot choose anything. Should I create a dummy field to populate that. There is no documentation on how to use it. ty for your reply.

echuong1
Alteryx Alumni (Retired)

You don't actually need that option. Just uncheck the box for that section.

mithily
8 - Asteroid

I still get the error no matter what. Can you post a small sample and thank you for helpingCapture.PNG

echuong1
Alteryx Alumni (Retired)

Would you be able to upload a copy of the data you're trying to use?

 

See attached for an example. I added row totals for two columns.

 

echuong1_0-1599757282955.png

 

mithily
8 - Asteroid

Many thanks, I am attaching the file I used. it is the sample crew macro but any data I use, I get the same error. Am I using an old version of crew macros? Can you point me to the version I should use. This is an awesome community, thanks for looking into this. 

echuong1
Alteryx Alumni (Retired)

Hmm, what is odd is that it is actually still producing the output, along with the error message. Are you seeing the same thing?

 

echuong1_1-1599758059009.png

 

 

echuong1_0-1599758031793.png

 

echuong1
Alteryx Alumni (Retired)

I think the issue is because you don't have any non-numbers in the dataset. It doesn't have a differentiation as to what each row means. Adding another non-numeric column that acts as a label for each row resolves the error. I'm assuming this is just a check built into the macro since generally, you'd want some sort of differentiation for each row. However, it looks like the tool still outputs as expected without it and just throws that error message.

 

Hope this helps! 

 

echuong1_0-1599758253396.png

 

mithily
8 - Asteroid

perfect ty

Labels
Top Solution Authors