Alteryx Designer Desktop Discussions

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

Transpose Tool Resets after blank data flow?

Aviator0807
8 - Asteroid

So it seems unlike a select tool that remembers missing data, the transpose tool doesn't remember the selected key columns and data columns. I set up a workflow to run automatically on the gallery once a week. And well sometimes on of my branches in my workflow will be blank and this week happened to be the second time. The Alteryx errored because the nothing was selected in the transpose tool, when this happened last time I assumed I forgot to set it up but now it im sure I did set it up before. Is there any way to get the transpose tool to remember your selections even if the data flow is blank? 

7 REPLIES 7
PhilipMannering
16 - Nebula
16 - Nebula

What's the exact error message you get?

Aviator0807
8 - Asteroid

@PhilipMannering 

The key columns selections is reset to have none checked. So it throws me the error that at least one field must be selected. 

Aviator0807_0-1639579961676.png

 

PhilipMannering
16 - Nebula
16 - Nebula

Ah, I see. Yes this is annoying. So I'm guessing this happens when any of the key fields aren't in your dataset?  

 

You can accommodate the pivoted Data Columns by selecting Dynamic and Unknown Columns

PhilipMannering_0-1639580542928.png

 

Key columns are more difficult. One way is to have a text input with headers of all the key columns you expect and then to union this with the dataset before the Transpose Tool. See attached example.

PhilipMannering_1-1639580822181.png

 

 

Aviator0807
8 - Asteroid

@PhilipMannering That would work if the Key column was missing, but if the whole data flow is missing then the union will also come out blank no? Thus giving the same error. 

PhilipMannering
16 - Nebula
16 - Nebula

@Aviator0807 Hmmm... not sure. What causes the whole data flow to be missing?

Aviator0807
8 - Asteroid

@PhilipMannering The first financial week of a month is calculated different than the rest so in my workflow I use a T/F to split the first week. So depending on the week either of my branches could be empty, and cause this error. 

PhilipMannering
16 - Nebula
16 - Nebula

I think the unioning solution posted above should still work in that case. Perhaps add another filter tool to simulate not records getting passed downstream to see if it would work.

Labels
Top Solution Authors