You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 27, 2021. It is now read-only.
What behaviour I'm expecting and which behaviour I'm seeing
ALRC draft 5 site. Have configured two attribute search Queries on the uploaded GeoJSON layer. The City search should populate a drop-down but instead I see:
Minimal example reproducing the issue
Launch the ALRC draft 5 site and look at the City query.
The text was updated successfully, but these errors were encountered:
The saved query didn't have any choices provided. I added an option (called Test), and the dropdown is displaying correctly.
@qqnluaq can answer better for this on the client side behaviour, but I don't believe the client auto-populates for vector dropdowns, only MPCM and WMS layers. Vectors require you to define the dropdown values/descriptions.
@NicoledeGreef We've just deployed an update to the Admin UI that exposes two options for the Query Dropdowns. More information is available in the documentation, but basically:
You can select "Dropdown" which creates a standard dropdown selection that you must supply values for
Or you can select "Autofill Dropdown" which will automatically poll for values from the source data (Vector, WMS, or DataBC) and populate the selection options from that.
How to reproduce
What behaviour I'm expecting and which behaviour I'm seeing
ALRC draft 5 site. Have configured two attribute search Queries on the uploaded GeoJSON layer. The City search should populate a drop-down but instead I see:
Minimal example reproducing the issue
Launch the ALRC draft 5 site and look at the City query.
The text was updated successfully, but these errors were encountered: