hi,team.Our team upgraded the project from 0.8.45 to 0.9.6.1, and after merging, I found that the interface parameters have changed during the verification of the GMS service graphql interface. for example,The filter in the search parameters is no longer supported。After I rebuilt the service, I found that my service did not take effect and the original parameter interface can still be used. Do we have any mechanisms or suggestions from everyone？

@famous-waitress-64616 would love your input here!

Which graphql query are you making here? @big-carpet-38439 any ideas?

The latest version of my GMS service's parameters are in effect, but after starting Frontend, I found that the old version's parameters can still be used. I don't know where I made a mistake

Is this a

search

or

searchAcrossEntities

query? If so, the

filters

field is deprecated but not removed, which is likely why you can still use it. However, to prevent issues in the future, use the field

orFilters

instead. Note that

orFilters

has a slightly different interface. To get the old behavior, do:

"orFilters": [
  {"and": [<your filters here>]}
]

@famous-waitress-64616 thankyou,i got it