Environment:
- ArcGIS Enterprise 11.4 ArcGIS Dashboards
- Feature service published from ArcGIS Pro 3.6 referencing registered data (not hosted)
- Source: SQL Server 2022 enterprise geodatabase; the layer is a database view (point geometry, SRID 4326, ~62,000 rows)
Problem:
In a Dashboards element (Indicator), adding a Filter on a string field shows "No matching options" in the value dropdown — the list never populates, even when typing to search.
The interesting part — it depends on the field's unique-value count, on the same layer:
- kategori_lesen — 12 unique values → dropdown populates fine, including counts
- subkategori_lesen — 322 unique values → "No matching options"
- Both fields are esriFieldTypeString, length 255
What I've verified (browser dev tools):
The dropdown fires a query with groupByFieldsForStatistics=subkategori_lesen and the server responds 200 OK with the complete, correct list:
{
"fields": [
{"name": "subkategori_lesen", "type": "esriFieldTypeString"},
{"name": "countOFsubkategori_lesen", "type": "esriFieldTypeInteger"}
],
"features": [
{"attributes": {"subkategori_lesen": "KATERER MAKANAN", "countOFsubkategori_lesen": 5}},
{"attributes": {"subkategori_lesen": "LESEN BAYARAN PENDAFTARAN LESEN", "countOFsubkategori_lesen": 3}},
...
]
}
So the service answers correctly, the widget receives the data and displays nothing.
Also verified:
- Layer's Advanced Query Capabilities are all true: Supports Distinct / Pagination / Statistics / OrderBy / Count Distinct
- Count queries and the element's Data table work perfectly
- Typing the full value manually ("enter new value") creates a workggestion list fails
- An equivalent hosted feature layer populates the same high-cardinality field without issue
Questions:
1. Is there a documented unique-value limit for filter value lists on non-hosted feature layers in Dashboards? If so, what is the threshold?
2. Is this a known bug in Dashboards for referenced feature services, and is it fixed in a later Enterprise/Dashboards release?
3. Any workaround to get the value list to populate for high-cardinng exact values or driving a Category selector from a separate small hosted lookup table?
Any pointers appreciated - happy to provide more traces.
