POWL: 'Define New Query' - Does it always save the last entered values?

[former_member195355]

Hiya,

From your experience how would you say user defined queries work?

Users are creating their own queries and saving them. They have noticed that when they adjust the search criteria on their query, next time they go into it, the system remembers the ‘latest’ change rather than the state of the query that was saved initially. It might be a standard behaviour, I don’t know.

Example:

Okay let's say we have a POWL and the user decides to create their own query via the 'Define New Query' button.

They create a new POWL query, with specific selection criteria, and it works great.

Uh-oh, one day they accidentally run the new query with some bogus selection criteria that the user doesn't want.

The new POWL query seems to remember the last entered selection criteria and always shows that to the user.

And there seems to be no way of going back to the orginal selection criteria of the user's POWL query?

Is this standard POWL functionality for user defined queries?

i.e. That whatever the user last enters into the selection criteria, is also what will appear hence forth, and not the criteria that was entered when the user created their query?

Thanks in advance for any help!

[Former Member · Accepted solution]

Yes this the standard POWL behaviour.

if we need to reset the query you can run the report POWL_D01 by giving application id and user name, you can delete the queries which are buffered here.

Creation of new query is nothing but applying the selection criteria so it will only filter the data, the underlying logic will be same.

Thanks,

Raju Bonagiri