How to remove cache and cookies?

Durgesh_Kumar_Rai · January 4, 2023, 9:55am

Let say a user just logged in into the application and then searches in list filter for a customer in the Customer list with mobile number and now he log out from the application. Then if he comes again and login, he is seeing that filter in list same as he searched last time. Is it happening because of the cache or some other thing is causing the issue? How can we prevent this issue?

ankush · January 4, 2023, 11:59am

List views remember last filtered values and reload that page as often users come back and apply same filters.

There are couple of ways to store multiple filters:

Saved Filters in sidebar (v13 and v14)
Bookmarking URLs (v14)

You can override this behaviour with client scripts

github.com

frappe/frappe/blob/b78452dc00e6a6f5b836e63b6c4684b8953e93da/frappe/public/js/frappe/list/list_view.js#L7-L22


      
          	static load_last_view() {
          		const route = frappe.get_route();
          		const doctype = route[1];
          
          
		if (route.length === 2) {
          			const user_settings = frappe.get_user_settings(doctype);
          			const last_view = user_settings.last_view;
          			frappe.set_route(
          				"list",
          				frappe.router.doctype_layout || doctype,
          				frappe.views.is_valid(last_view) ? last_view.toLowerCase() : "list"
          			);
          			return true;
          		}
          		return false;
          	}

github.com

frappe/frappe/blob/b78452dc00e6a6f5b836e63b6c4684b8953e93da/frappe/public/js/frappe/list/list_factory.js#L23-L26


      
          		if (view_class && view_class.load_last_view && view_class.load_last_view()) {
          			// view can have custom routing logic
          			return;
          		}

jpatdu · July 23, 2023, 10:10am

Hi, can you kindly clarify what you mean by overriding this behavior with client scripts?

In my case, load_last_view() will always return false since route.length is 3. Yet, the last used filters are still fetched. I do not know which part of the code I should modify to disable remembering the last filtered values.

And a note on UX:

“List views remember last filtered values and reload that page as often users come back and apply same filters”

During UX testing in our firm, however, this “optimization” just leads to confusion. At best, users won’t see records and get confused. At worst, users forget to reset the filters and act on the wrong documents. It may be annoying to keep on re-applying filters, but I’d rather have users be mildly inconvenienced than make hard-to-trace mistakes that could severely impact the accuracy of data on the ERP.

guimorin · July 23, 2023, 1:57pm

+1
This default behaviour is very confusing for new comers.

However with the recent addition of the clear all filters button, it’s much easier to clear.
And you could tweak css to make it more obvious to users that some filters are applied. We highlight in orange filter fields having a value set.