|Applies To||RSA Product Set: RSA Archer|
RSA Product/Service Type: RSA Archer
RSA Version/Condition: 5.x, 6.x
|Issue||After a report is set to private the user who set the report to private can no longer view the report. This will occur when the user who set the report to private was not the user who created the report. This can be an issue if the user who created the report no longer exists within Archer, as the report will no longer be visible to any user.|
|Cause||A Private Report will only be visible to the user that originally created the report.|
|Resolution||To save a report that has been created by another user the "Save as New Report" option can be used:|
This will create a new instance of the report with the current user listed as the Creator. When set to Private, the new instance will only be visible to this user.
|Workaround||If the original creator of the report no longer exists, the create_login field can be changed via SQL to assign the report to a different user.|
To view all existing reports within the SQL database the following query can be used:
In order to assign a new user as the creator, a known create_login number will need to be identified. Use a known report to identify a create_login for a user that still exists within Archer.
Note: Before issuing any UPDATE statements, please run a SQL backup in order to have a point to recover/rollback to if needed
To update the create_login for a single report the following UPDATE statement can be used:
To update the create_login of ALL reports created by a deleted user, the following UPDATE statement can be used: