Reset all filters using javascript is still remembering the filters after user login back

Prateek KumarPrateek Kumar ✭✭
edited September 3, 2019 in Questions
I have created a global Reset Action which deactivate the all model conditions and clear the search box using JavaScript Snippet. It works fine if the user is in the session.

But when user logs out from the portal and log in back it remembers the last applied filters which was already reset using the Reset Action.

I guess the Reset Action is only deactivating the condition it is not toggling the values to the cache to forget the details of removed filters.

Please suggest me what to do in this scenario.

Comments

  • edited September 3, 2019
    My first thought is to set the filters to not remember the last value. This is a filter setting in the page composer.

    The second thought is a question or two: What is the page setting for Personalization Mode? And, in your deactivateCondition() functions do you include TRUE for the optional argument affectPersonalization?





    deactivateCondition(conditionaffectPersonalization)

    Deactivates the given skuid.model.Condition() so that it will not be applied to future queries on this model.

    Arguments:

    • condition (skuid.model.Condition) – The condition to deactivate
    • affectPersonalization (boolean) – Optional. If true, and if the condition has a name, then the Skuid Personalization Framework will store the value of this condition indefinitely (if the Page’s Personalization Mode is set to Server-side) or for the duration of the browser session (if the Page’s Personalization Mode is Client-side) so that the condition’s current value will be pulled from the stored value for the running user the next time that the page is loaded.

  • Prateek KumarPrateek Kumar ✭✭
    edited January 7, 2019
    Thanks! Mike Dwyer
    It was really very helpful information.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!