Creating dynamic interface dropdown tool of unique values coming from a single column

[BretCarr]

Hello all,

I am attempting to make an app interface that takes a macros incoming data stream and allows the user:

     1. uses drop down interface tool

     2. pulls the values of a single field/column

     3. summarizes values into single unique values for drop down tool

     4. presents sorted alphabetically

     5. selected value then updates a filter on the input data to pass through only selected value.

Here is what is the basic outline w/o complex interface tools so those with imagination can picture it:

Input Tool (dataType values are ones needed to feed drop down on macro interface):

Macro workflow:

[apathetichell]

Have you looked into using a batch macro? in this case your drop down would be replaced by a control parameter. You'd use a summarize tool in your main workflow - and then feed that into your control parameter.

[nagakavyasri]

@BretCarr Is this what you are looking for to select data types?

[BretCarr]

@nagakavyasri 

This community is the jam so thank you for your reply.

Unfortunately, that's what I was already trying--which only provides the field names. What I need in the dropdown are the actual values in that field. 

In your example, you have a filter for the year: I would like the first tool to provide the dropdown with year values to choose from in the dropdown tool. The dropdown tool would then update the filter to that year selected in the dropdown tool.

[BretCarr]

@apathetichell 

A very good idea, however, I have already created such an iterative process to filter one at a time into separate tables in one swipe.

The issue is that I need to be able to do one at a time upon user selection within the workflow since each datatype is fed to a specific part of the following processes in the workflow.

I feel like you all are almost there! I'm beginning to wonder if this is even possible and could just be a limitation. 😕

[apathetichell]

O.k. - so if it's user selection it should be via an app - and the values have to be set prior to executing. otherwise you are using a chained app. the standard run is:

outer app (app where selection occurs)

selection feeds to text input box. 

text input box feeds into macro (this allows app selection by user into macro). You can send this deeper into nested macros using the same process. I map via control parameter/batch macro (ie text input to control parameter to inner batch macro's text input/etc).

If you want user selection to dynamically change at run time you will need a chained app.

[BretCarr]

I'm fairly certain I'm following you and your answer is what I was trying to avoid. I get that the information has to be populated before it can selected by the user. Are you telling me to create a workflow-app-process that creates the direct selection population information that must be run first in the Gallery/locally at which time my currently built app then just uses that data for the dropdown(s)?

[apathetichell]

If you want:

1) user selects x.

2) user only sees sub-section of x and selects y

you can configure the x/y mapping either using chained app or a single tree (as shows in my workflow's second app).

if your are looking at the above with an intro step of:

base drop down is dynamically pulled at run time from an outside source (file/db) - you must use chained apps OR have another workflow/app (could be scheduled separately) which writes the results needed for the interface tools to an accessible drive location.

[BretCarr]

"(as shows in my workflow's second app)."

Were you going to attach a image or file of some sort?

[apathetichell]

oh sorry- thought this was about another process - I'm not sure where your issue is... You're trying to have a user select some field and then carry that selection over to a filter in a macro? you'd have the user selection update a text input field - and the text field update your control parameter which would update the filter value inside the macro. Where are you having a stumbling block?