Workflow cascading combobox

Permanently deleted user

15. Juli 2011 09:37

Hi,

I have a display Form activity with 2 combobox controls in my workflow, I am populating these comboboxes using the input DataItem collection. The second combobox is dependent on the selected value of the first combobox. I would like to get the DataItem collection to populate the second combobox based on the selected value of the first combobox. Is it possible to have a cascading dropdown when using the input DataItem collection to populate comboboxes?

 

0

• 

  Permanently deleted user

  15. Juli 2011 23:34

  You'll probably find the answer to your question by watching the video of Configuring Workflow ComboBoxes and ListBoxes at

  http://support.geocortex.com/workflow

  It's the second one in the list. 

   

  0
• 

  Permanently deleted user

  18. Juli 2011 04:54

  Sonia,

  Thank you, I have watched the video of Configuring Workflow Comboboxes and Listboxes, and  in this video the cascading dropdown uses the Query task and Query Cascading ID to populate the combobox. In my workflow, the first combobox displays the subtypes from a feature service and the second combobox displays the domains based on the selected subtype from the first combobox from the feature service. I couldn't use the Query task to get the domains and subtypes, so I am using the DataItem collection populated in previous activity  to populate the comboboxes. Is it possible to get the cascading dropdown functionality when populating the comboboxes using DataItem collection instead of using query task?

  0
• 

  Permanently deleted user

  25. Juli 2011 13:41

  I have two other questions related to the cascading combobox.

  1. How do you limit the combobox to unique value only?

  2. Is it possible to do cascading combobox with 3 or more levels? 

  0
• 

  Permanently deleted user

  23. September 2011 13:29

  We've been struggling with this issue as well and contacted support for help:

  Right now you can only have the value of a cascading combobox depend on the value of one other combobox, so what you want is not easily possible.

  It could be possible to do this in three different steps/forms. This would involve performing the query manually and then populating a list of DataItems to place in each combobox. You would also be able to remove duplicates, something that is not currently possible from within the form. It could be possible to do this in three different steps/forms. This would involve performing the query manually and then populating a list of DataItems to place in each combobox. You would also be able to remove duplicates, something that is not currently possible from within the form.

  0
• 

  Permanently deleted user

  27. September 2011 01:04

  We are currently gathering requirements for the next release of Forms. I will add the following 2:

  - Display unique values only option

  - Cascading Dropdowns of more than 2 levels

  Of course, we'll need to prioritize all the requirements, but it most likely that those would make it in.

  Cheers,

  Christian.

   

   

   

   

   

   

  0
• 

  Permanently deleted user

  12. April 2012 03:45

  Christian,

  Can you please provided status on this enhancement request? We are running 3.8/1.5 and cascading still seems to be limited to only one item. I would prefer to not have to alter my underlying data to accommodate how the cascading combo boxes are designed. Having the ability to dynamically create robust Where statements based on  the multiple combo box values is very important.

  Thanks,

  Aaron

  0
• 

  Permanently deleted user

  12. April 2012 04:49

  I second that request.

  In the mean time Aaron, we did a workaround for his using query layers to dynamically build the composite keys.  When you publish the query layer in a map document you can interact with the table much like you can a feature class.  Anyway - worth a look of you're stuck. 

  0
• 

  Permanently deleted user

  12. April 2012 05:15

  Hi Aaron,

        The feature described in my post have been implemented. You can have more that 2 levels in a cascading chain. But you can only refer to the value provided by the immediate parent. We have no plan to support getting the values from more than the parent.

        I know it's not what you'd like to hear but there are technical limitations with having multiple values from multiple drop downs and unstructured queries. Again, the recommended way is to have a unique key in the parent.

  Cheers,

  Chris.

  P.S. We may expose an API on the client in the future so that a selection event would be exposed. This would allow someone to modify the where clause of the child drop down with whatever query they want. But this is not in the near future.

        

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.