From time to time you may find that your user’s account no longer appears to allow you to log into HFM from the web. Oh, they can log in without an error, but what the browser displays may appear to be miniature, garbled or completely corrupt. You may even get an “ADF error”. The problem follows the user from device to device, while others are able to access the same application without error.
So what is going on here?
The user has a corrupt Point of View for that application. Hyperion can save the last form and/or view users have when you log off. If that form is removed, the point of view is invalid (i.e. a dimension changes names, etc.) or for some other reason, the item and data viewed at last log off of a user becomes corrupt, the above symptoms occur.
Unfortunately, there is no quick and easy fix. There is no “reset POV” button or command utility. Instead, you must modify database tables to clear this problem and get the user working correctly again.
The example here is for MSSQL, but similar commands and steps can be used for any other database type by simply using the appropriate tools / syntax for that database.
In MSSQL, open the USERPARAMS table matching the HFM application name (i.e. for HFM application MYAPP, the table name to open would be MYAPP_USERPARAMS)
Run a query to ensure the user ID can be seen clearly and no other users are impacted. So first we’re going to “view” in such a way that ONLY this user’s entries are visible, then we will use that command to remove those entries.
In MSSQL, this would look something like this:
1) Open the top 1000 rows of the table
2) Modify the produced query to filter on the user
3) The results should only include this user
4) Once you have verified this, now you can change the command to delete these records. These are the records that are holding the bad Point Of View information for this user.
5) When you run this, you should see the rows have been deleted.
The user should now be able to load the application
Note: They may need to close the browser and clear cache.
Disclaimer: This article is intended to be a resource only and is not intended to be nor does it constitute legal product advice. Any recommendations are based on our direct experience in this environment during the time in which this was posted.