Is a Query Layer now a Dashboard Indicator Control Requirement

[MichaelVolz]

I was updating the data source feature class for a Dashboard sourced from a referenced mapservice originally built in enterprise 10.7.1.  The data source is no longer accessible from the mapservice according to error message.

Does the data source now need to be a query layer?

[MichaelVolz]

So I exported the problematic SDE roads line feature class to a file gdb and created a service from the file gdb feature class.  Now I can use a Dashboard indicator.

As such, what could cause the same SDE feature class not to work in a Dashboard indicator?

[MichaelVolz]

When adding fields to a versioned enterprise gdb feature class, do you always unversion first, add fields and the re-version to make sure evw file is created properly? 

[SteveMarkovick]

Query layers can feel a bit confusing in dashboards because they blur the line between data source and control. From what I’ve seen, they don’t automatically behave like indicator controls unless they’re exposed through a feature layer or view that dashboards can interact with. Once wrapped properly, they work fine, but expecting them to act like native controls usually leads to frustration.