000029693 - RSA Archer: Reports Set To Private Disappear

Document created by RSA Customer Support Employee on Jun 15, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000029693
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Archer
RSA Version/Condition: 5.5 SP2
IssueAfter 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.
CauseA Private Report will only be visible to the user that originally created the report.
ResolutionTo save a report that has been created by another user the "Save as New Report" option can be used:
 
Save as New Report

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.
WorkaroundIf 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:
 
SELECT * FROM tblReportBase

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:
 
UPDATE tblReportBase SET create_login = <new create_login> WHERE report_base_id = <report_base_id of report that needs to be updated>

Example:
UPDATE tblReportBase SET create_login = 7 WHERE report_base_id = 8745

To update the create_login of ALL reports created by a deleted user, the following UPDATE statement can be used:
 
UPDATE tblReportBase SET create_login = <new user create_login> WHERE create_login = <deleted user create_login>

Example:
UPDATE tblReportBase SET create_login = 192 WHERE create_login = 1234

Attachments

    Outcomes