Forum Discussion

Eric93's avatar
Eric93
Frequent Visitor
10 months ago
Solved

One user error

Hi all,   I'm encountering a strange case : we have an app where, on one slicer for one page on one of the reports, a single user gets an error of this type : the usual "error picture" preventing f...
Need Help
ibarrau's avatar
ibarrau
Super User
10 months ago

There is a reset filter button on the UI outside the report canvas. Once the user click on Corriger and it gets fixed. If the user refresh the browser, is the error back again everytime?

 

Eric93's avatar
Eric93
Frequent Visitor
10 months ago

Hi,

After new tests, here are the answers :

-After the user clicks on "Correct this" and it does correct the issue, the error is back when the browser is refreshed.

-Curiously, the user only sees the error on the app : when the user opens directly the report, there is no error.

-The reset filter button is deactivated on this app.

However, when the error appears, the user can click on it to reset filters, and it does solve the error. After that, the user can see the message about the reset button being deactivated.

If the browser is refreshed, everything is back : the error, and the possibility to use the reset filters button.

  • v-aatheeque's avatar
    v-aatheeque
    Community Support
    10 months ago

    Hi Eric93 

    Thanks for sharing these details. It seems the issue reappears after a browser refresh, which suggests that the fix applied through “Correct this” or the reset filters option is only temporary.

    Could you please confirm a few things to help us investigate further?

    1. Does this behavior occur for all users or only specific ones?

    2. Are there any bookmarks or personal views applied in the app when the error reappears?

    3. Can you share a screenshot or the exact error message that shows up after the refresh?

  • Eric93's avatar
    Eric93
    Frequent Visitor
    10 months ago

    Hi, thank you for the reply.

    1. This behavior occurs for only one user.

    2. There are bookmarks applied in the app, but not by the user for whom there is this behavior : all the user's bookmarks were deleted to be sure the issue wasn't caused by them.

    3. After the resfreh, the error message is the same than before :