Filtering integers broken after October 25 2022 update?

[RobBlash]

I'm getting an error when filtering on integer fields this morning. This was working fine prior to the update yesterday. Anyone else? I'm going to submit a support ticket but also posting here to see who else is having trouble.

[AndyMcClary]

I'm seeing the same issue. Seems to be limited to integer fields but I haven't tested extensively.

[RobBlash]

After some work attempts it seems like any numeric character in the filtering will throw the error. I have a premium support ticket in already, will report back.

[TracySchloss]

We're seeing the same issue in all our surveys, and we use this functionality a lot.  Esri please fix this!  

[RobBlash]

Support has confirmed they can reproduce the issue. I'll update once I get more info.

[ZhifangWang · Accepted solution]

Hi @RobBlash @AndyMcClary @TracySchloss ,

I can reproduce the issue on the latest Survey123 website, sorry for the inconvenience.

We are looking into the details and will evaluate a hotfix to address this issue.

Thanks,

Zhifang

[JeffLegato1]

We are experiencing the same issue.  I found a temporary workaround for our issue by setting the filter in the link to be 
filter=(1.OBJECTID%20isBetween%20{OBJECTID|%20and%20{OBJECTID})

[DavidMichaels]

We are experience this issue as well but including text fields with out integers 

[RobBlash]

@ZhifangWang is there any timeline on a potential hot fix?

[GIS_Fox]

We are still experiencing the same error with both integers and other characters as of this morning 10-28-22. We've been able to get workarounds done with other filter tools or manually selecting items but field users are in need of this function. 

Thanks,