Combo Box Query: Where Clause

Permanently deleted user

8. Februar 2012 02:05

Hello,

I am trying to do a cascading search that has three combo boxes.  I have been able to successfully use the input from combo box 1 in the where clause of combo box 2, but I'm not sure how to use the values from combo box one and two as the where clause for the third. i.e.

ComboBox 1  - where - 1=1

ComboBox 2 - where - field 1 = {0}

ComboBox 3 - where - field 1 = {0} AND Field 2 = {1}

It blows up on the {1}, hardcoded values work.  Any ideas?

 

thanks-

Jake Brown

0

• 

  Permanently deleted user

  8. Februar 2012 02:35

  Hi Jake,

       You can only get the value from the immediate parent in a cascading chain. Make sure your data can be uniquely identified from the parent value.

  Cheers,

  Christian.

  0
• 

  Permanently deleted user

  8. Februar 2012 03:13

  Thanks for the quick response, I will do a workaround.

  0
• 

  Permanently deleted user

  27. August 2013 14:14

   

  I face the same problem. How do we cascade multiple combobox ? 

  Dear Jake.

  Have you find a work arround for this problem ? 

   

  this is not nice from  Geocortex 

   

   

  0
• 

  Permanently deleted user

  28. August 2013 13:17

  Mr. Edmond 

  This is brilliant and thank you very much for guiding me and giving correct syntax. I was struggling to find the correct syntax. 

  CITYID=‘{1:ComboBox1}’  AND ROADID= ‘{1:ComboBox2}’ 

  saved my requirement in my case .I know I could name combobox's names better but this is just summerizing what Edmond has done as brilliantly in one line. Hope this will help many as me. 

  As Edmond said this will work only on Geocortex 3.14 and above  

  Thanks you again 

  Anjitha 

  0
• 

  Permanently deleted user

  29. August 2013 02:43

  Hi Anjithalk and Edmond

  the comment about naming of form items brings up one of the things that annoys me and that is the lack of ability to change the default Id'sof the form items. It can be done if you directly edit the xaml which is pretty ugly as far as not breaking anything.

  This issue is especially felt in the syntax used above or when using RunTimeModifications to the form

  Regards

  Ralph

  0
• 

  Permanently deleted user

  23. November 2013 08:17

  Hi Laura,

  I've spent some time with your workflow, and cannot replicate the issue. I'd suggest that you use Fiddler  - https://support.geocortex.com/use-fiddler-to-capture-web-traffic-between-a-web-browser-and-a-web-site Fiddler to see what's happening 'behind the scences.'  Look specifically at what you workflow is sending the the URL, and the json response.

   

  If you can update your sample to point at some publicly availble data that would help others try out your simple form.

  regards,

  Edmond

   

  0
• 

  Permanently deleted user

  25. November 2013 22:52

  Hi Edmond,  Thank you for taking a look at my workflow.  I discovered a couple days ago the reason it wouldnt work was because I was using a version of Essentials that wasn't compatible with cascading combo boxes.  I  upgraded  my software to the latest release and it worked fine after that.  Thank you again.  -Laura-

  0

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