Make definition query's toggle more intuitive

[Bud]

@KoryKramer Feel free to close this idea. Support is submitting bug reports for these issues.

Edited: I removed the part about hovering over the definition query.

Regarding the definition query window:

For an existing definition query that is enabled, the toggle makes it look like it's disabled.

GIF:

Could the UI be improved so that it's clear that an existing enabled definition query is displayed as being enabled? 

Thanks.

ArcGIS Pro 3.0.3; mobile geodatabase.

[JohannesLindner]

I think you're missing something.

The query has 4 states:

• active, normal
  
• active, hover
  
• inactive, normal
  
• inactive, hover
  

The grey checkmark in the inactive hover state is meant to tell you "Hey, click here to activate this query!"

You have something different going on there: The query shows as inactive, although it apparently is active. Could be that this is due to your more complex query. Try a simple one.

[Bud]

Here's the data and SQL expression -- in case someone wants to reproduce that UI behavior:

Standalone table named roadinsptable:

ASSET_ID: Text
DATE_: Date
CONDITION: Long

ASSET_ID	DATE_	CONDITION
1	2016-04-01	1
1	2019-03-01	2
1	2022-01-01	3
2	2016-04-01	4
2	2022-01-01	5
3	2022-01-01	6
3	2022-03-01	7
3	2018-03-01	8
3	2013-03-01	9
3	2010-06-01	10
3	2022-03-01	11
3	2022-03-01	11

SQL Expression:

roadinsptable.objectid IN (
     SELECT objectid
       FROM roadinsptable r2
      WHERE r2.asset_id = roadinsptable.asset_id
   ORDER BY date_ DESC, condition DESC
      LIMIT 1
            )

 ArcGIS Pro 3.0.3; mobile geodatabase.

[Bud]

Esri Canada Case number #03255222 “Definition query with subquery shown as inactive (incorrect)”

Bug number: BUG-000155660
Synopsis: Definition queries do not appear as active after enabling the query and reopening the definition query again.

Related: Modifying existing SQL expression disables definition query

[alex_friant]

From the video it's clear there is a bug with that type of complex SQL query. The bug being that when you open the DQ in Properties, it automatically disables itself. 

I can't replicate it though. I had a similar SQL query (nested, but no joins) on a mobile geodatabase and it didn't bug out like this. I'm using Pro 3.0.3, btw.