Pushing Report Data to the Application Database

If you need to leverage your security report data outside of your system database, you can push the data from the system database to an application database of your choice. This allows you to work with this data in MRI Property Management—for example, to export the data to PDFs from the Communication Center.

Note

The Audit History Report typically requires a begin and end date, so pushing this data to an application database will result in all data from the database's entire history being included.

The Login History Report is currently not included in the list of reports that can be pushed to an application database.

To push your report data to the application database, follow these steps:

1. Go to Reporting.

2. In the Report field, select Push Data for MRI Web Reporting.

3. In the Database field, select a database.

4. Click Run. While the utility is running, you can click Work Requests to check the status of each report.

5. After the reports have finished running, the Send Data window appears. Click OK.

Report Tables

To facilitate moving data between databases, the information is stored in the tables described below. Tables follow the naming convention of SecurityReport_(ReportNameWithoutVowels), sometimes followed by one of the following suffixes:

Table names that end in "_H" are header tables. In the Excel file, this is the information in the white cells at the far left.
Table names that end in "_D" are detail tables. In the Excel file, this is the information in the yellow cells (as well as a few identifiers to link to the associated header table.)

Report	Table	Items	Notes
Additional Access Report	SecurityReport_AddtnlAccss_H	ID, Description, ApplicationID
Additional Access Report	SecurityReport_AddtnlAccss_D	ID, Name, SecurityType, Access	In the SecurityType column, U = user and R = role.
Audit History Report	SecurityReport_AdtHstry	UserID, ModifiedUser, FirstName, LastName, Email, Field, ChangeType, OriginalValue, ChangeDate
Menu Access Report	SecurityReport_MNAccss_WbMn	ID, Title, ParentID, RoleID	The ParentID column determines the level at which the menu exists (i.e. whether it is a child of another menu.) If ParentID is null, the given menu is at the top layer; if ParentID is not null, the given menu is a child of the menu with that ID.
	SecurityReport_MnAccss_WbMn_R	ID, RoleID, Description, Access	MRI Web Menu Access - By Role. This table is linked to the first sheet shown in the report.
	SecurityReport_MnAccss_BlckdUsrs	ID, UserID	MRI Web Menu Access - By User. This table is linked to the second sheet in the report and all sheets that begin with "Role Menu Access -". Although the report shows each individual item the user is blocked from, this table only shows the top level at which the user was blocked, and it can be assumed that they are also blocked on all children of that item.
	SecurityReport_MnAccss_UsrRlMppng	RoleID, UserID, FirstName, LastName	User Role Mapping. This table is linked to the third sheet in the report, and is independent of other reports.
Record Access Report	SecurityReport_RcrdAccss_H	ID, TableID, Description
Record Access Report	SecurityReport_RcrdAccss_D	ID, TableID, UserID, Access
Report Access Report	SecurityReport_RprtAccss_H	ID, Description, ApplicationID
Report Access Report	SecurityReport_RprtAccss_D	ID, Name, SecurityType, Access	In the SecurityType column, U = user and R = role.
Table Access Report	SecurityReport_TblAccss_H	TableName, FieldName, Description, ApplicationID
Table Access Report	SecurityReport_TblAccss_D	TableName, FieldName, Name, SecurityType, Access	In the SecurityType column, U = user and R = role.
User Security Report	SecurityReport_UsrScrty_H	UserID, LastName, FirstName, EmailAddress, SiteID, SiteDescription, Disabled, Locked, NamedLicense, LastLoginDate, EntityClass, ProjectClass, PropertyClass, VoucherProjectClass, WaitingListClass
User Security Report	SecurityReport_UsrScrty_D	UserID RoleID, Access
	SecurityReport_History	ReportName, UserID, LastUpdated	This is a special table which shows the last time report data was pushed from the Web Security Console for each report.