Support cascading select (Dropdown filters options in related dropdown)

[aparveen]

[aparveen]

@CTLocalGovTeam could you please assess this enhancement request for 9.4?

[sumitzarkar]

@aparveen @skrishn @chris-fox

We checked this enhancement and on analyzing this we have the following observations:

• If the layer has subtypes defined in the layer definition then this enhancement will work with the field defined for subtypes
• As mentioned above, this enhancement should be not limited to the hard-coded domain, then we need to do the following changes:
  • In the configuration, we need to provide a mapping source field with target fields and their value
    • For instance, Textbox for source field name, a textbox for source field value, a textbox for the target field name, and another textbox for its value (as shown below)
    • Also, the user has to create the above combination for all the values of the source field
  • With the template app config limitations, all the values will be static i.e. number of fields and text boxes will be limited for value and for the number of target fields

The below image is the example for specifying only 1 value mapping, this group will be repeated for the combinations of values i.e. if there are 3 users for the name field then a total of 3 groups have to be added

As discussed on the call yesterday, the forms in Reporter apps are based on GeoForm and it is dependent on the Feature Layer. So adding such enhancement in the report app will have a major impact on core code.

[aparveen]

@sumitzarkar the team decided to go with this enhancement in 9.4 release and preferred the csv input as solution, could you please start working on this issue? We would like to have a separate pull request for this so if we need we can pull back the changes. Thanks FYI @skrishn @chris-fox

[ashutoshverma-ct]

Points discussed during the call:

• CSV settings will be introduced under the "Forms" section for CSV
  • A textbox to specify URL
• Schema of the CSV should be in lines with the schema of excel sheets in the Survey123 i.e. first row will be a header with "Source Field", "Name", "Label", and "Source Value" columns
• All the fields specified in the CSV will be displayed as a dropdown in the application
• This enhancement will be applicable for layer geo form not on the comment form
• Date fields will be skipped for custom dropdown
  • Domains type fields should be modified based on the CSV inputs
• CT will explore more options to link CSV with the application

[ashutoshverma-ct]

@aparveen @skrishn @chris-fox

We are planning to provide settings for this ticket and the #512 as shown below:

• Both settings will be available under the "Forms" tab, at the bottom
  • Import field values for the CSV URL
  • Autofill values for the firstname, lastname and email values
• Strings are for demo purposes only, let us know if we need to change them

Please let us know your views on this. Thank you.

[aparveen]

@ashutoshverma-ct could you please change the strings to 1) Import choice list for cascading select 2) Autocomplete field information 3) autocomplete 4) First name 5) Last name 6) Email

[aparveen]

@ashutoshverma-ct instead of autocomplete please use autofill as you suggested previously. Thanks

[ashutoshverma-ct]

@aparveen @skrishn @chris-fox

We are clear with the string changes except for points 2 and 3. Just to be on the same page, we understood from above as follows:

• For point 2: The new string will be "Autocomplete field information". Here we do not need to replace "autocomplete" with the "autofill" word.
• For point 3: The new string will be "Autocomplete" only

Please confirm

[aparveen]

@ashutoshverma-ct all autocomplete should be replaced by autofill.

[aparveen]

Test case? @skrishn

[aparveen]

@sumitzarkar I noticed that csv file needs to be shared publicly to be able to get url for that item, wondering for the users who wants to use the cascading select within the org, how they are going to access the csv?

[sumitzarkar]

@aparveen

We tried different scenarios and here are the details of our alaysis:

CSV URL will work for the following scenarios only:

• If the URL is public and accessible for all using the link

• If the CSV is secured and its domain is same as the logged in user (same AGOL org for hosting CSV and logged in user)

Application will not able be to access the CSV data if:

• CSV is private or needs credentials to access item (Securely hosted CSV data using any custom domain. for e.g CSV shared from Sharepoint which is secured )

• CSV URL is from different AGOL organization than the logged in users organization

[skrishn]

verified in qa