community
cancel
Showing results for 
Search instead for 
Did you mean: 

Alteryx Designer Ideas

Share your Designer product ideas - we're listening!

In-DB Detour and Detour End

I think it would be extremely helpful to have an in-DB Detour so that you could filter a user's information without having to pull it out of DB and then put it back in for more processing.  A time where this would be useful is if you have a large dataset and don't want to pull the entire dataset out of the DB because it will take a long time to pull it.  This would be applicable for filtering a large dataset by a specific state chosen by the user or possibly a region.  The Detour in the developer tools actually seems like it would do the job necessary, it just needs to connect to the In-DB tools.  

6 Comments
Alteryx
Alteryx

Could you not do this currently by making an In-Db macro which had an In-Db filter updated by a question?

If I am understanding what you are saying, that wouldn't really be a solution.  Let me double check though.  So if I make an In-DB macro that is updated by a question I would still have the same issue.  Below is a picture of what I am trying to do.  Everything else is In-DB, so I don't want to have a data stream out and another one back in.  InDB_Detour.PNG

Alteryx
Alteryx

So in your picture what is the detour doing?  Is it that sometimes you don't want to filter and sometimes you do?

Yeah, so I am building an application and I want my users to be able to select or deselect certain filters.  So I am using detours to accomplish this.  

 

example.PNG

Alteryx
Alteryx

OK that makes sense.

 

I have a couple of workarounds for you that would get you the result you wanted

 

1.  Shortcircuit the filter tool when you want all the data

 

FilterShortcircuit.png

 

So the formula updating the filter tool is

 

iif([#2], "CID=" + [#1], "1=1")

 

and the filter is set to 1=1 when the checkbox is-unchecked

 

2.  Build the detour by hand using a union tool and delete tool actions

 

DeleteToolDetour.png

 

In this method we use a union tool to act as the detour end and then delete tool actions to choose which route we take.

 

Obviously an In-Db detour tool would be better than both of these solutions, but this gives you something you can work with right now.

 

I don't seem to be able to attach modules here, but hopefully the above description makes sense.  If not let me know and I'll think of a way to get you the modules.

Ok, those both seem like decent ways to do it.  I will try implementing both of these and let you know how they work.