SSRS – Changes to Handling of SSRS Reports (301-ssrs-util)

Changes to Behavior of SQL Server Reporting Services (SSRS)

Version 6.1.2206.0142 / 6.1.1811.2019

Overview

The following contains a description of the changes to the behavior of the SSRS feature in Govern

New Features and Changes in Behavior

Parameter Setup Changes

Users should note that parameters are no longer setup in the Reports Parameters screen. This screen will display only the run options that have been configured in GNA.

Possible “Run on” options that can be displayed are as follows:

On Database – Is configured to do not pass any record that is listed in the Govern Dataset Treeview.

On Recordset – Select this option when the SSRS report is to process a set of records. *

On Current Record – Select this option when the SSRS report is to process the current record.*

Changes related to Recordsets

The Recordsets created by the On RecordSet and On Current Record options come from the DataSet Treeview and are saved into the database (Table: USR_SAVED_DATASETS).
These records are grouped by the field SAVED_SET_NAME with a name like: SSRS_REPORT_GUID, where the GUID is a random GUI text generated at runtime.

Since these new recordsets are temporary, they are automatically removed each time a new SSRS report is executed. The criteria for removal is determined by confirming that SAVED_SET_NAME is like SSRS_REPORT_GUID and the field LAST_MODIF_DATE is older than the day before the current execution. For example, if a report execution is done on 08/10/2022, then all reports created before 08/09/2022 will be removed.

Note the following:

  • The Output tab with the report result is no longer displayed for SSRS reports.
  • The report result will be displayed directly on the default browser pointing to the SSRS server that has been configured for Govern.

New Online SSRS Viewer

In the new online SSRS viewer, the end user must perform the following actions to get the Report.

  1. Select/full fill the Report Parameter fields with the desired values for the report.
  2. Click the View Report button.
  3. A preview for the report will be displayed in the bottom.

To download the report, the user must select any of the output formats for the report with a click on the Save button.

To print the report

  1. Click the Print icon.
  2. The report will not be modified and will be copied into the TEMP folder, but in order to execute the report, it will keep looking in the Custom and Standard folders configured in the GNA settings.

 

NOTE: The appearance of the online SSRS screen can vary depending on the SSRS report version installed on the end users server.

This screen will display only the parameters configured as Visible on the report. Hidden parameters are not displayed here and must be configured in GNA under the parameters section in order to map a Govern Id value to them.

Considerations when running an SSRS report

  • At least one Run on option must be selected to run the report.
  • Reports created or edited in Report Builder 3.0 (2014), and the New SSRS Report Builder (2016), are supported and will be executed in Govern.
  • The report must have the SERVER and DATABASE parameters, where the parameters must be configured as:
    • The very first parameters in the report parameters; this because they will be used to configure the datasource.
    • The parameter visibility can be configured as Visible, or Hidden (this is the preferred value).
    • These parameters will be mapped by Govern with the name and database that are to be used to process the report.
    • The DataType must be ‘Text‘.
  • For the options On Recordset and On Current Record,  the report must have a parameter like RECORDSET_{GOVERN_ID} where:
    • {GOVERN_ID} is the Govern ID that will be used to filter the records.
      For example: if the Govern profile that will use the report is configured to use Parcel Ids, then the name for the parameter will be RECORDSET_P_ID.
    • The DataType must be ‘Text‘.
    • The parameter visibility could be configured as Visible, or Hidden (this is the preferred value).
    • A new recordset entry will be created with a dataset name like SSRS_REPORT_{GUID} to store the GovernId, or set of GovernIds that will be used for the operation.
    • These datasets will not be visible to the user in Govern in the Saved Dataset(s) screen.
    • These datasets will be automatically removed from the database after 2 days, upon the next SSRS report execution.
  • The new SSRS report functionality is no longer creating copies in the TEMP folder that is configured in GNA. As a result of this change, it means that the new version is no longer supporting:
    • Add filters on execution time.
    • Display the report output or parameters at govern.

In order to create/add these parameters the SSRS Converter Tool can be used to convert the rdl reports.

See Also

301-ssrs

301-ssrs-util

 

 

301-ssrs-util

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

SSRS – SQL Server Reporting Services Report Conversion Tool

SQL Server Reporting Services Report Conversion Tool

Version 6.1

Overview

The SSRS Report Conversion tool is a Windows application developed to assist, with some minor manipulations, the conversion of a .rdl report for use in the latest versions of Govern and GNA.

User Interface

When initialized, the SSRS Report Conversion Tool displays as a utility window with input and output parameters.

 

SSRS Report Conversion Tool Parameters

Input Folder – Click to manually type in the path to the Input folder. This is the path to a physical folder that must contain at least one .rpt file that is to be converted.

[…] Select Folder – Click the ellipsis button […] to navigate to the required folder.

Output Folder – This non-editable parameter contains the path to the folder that the converted reports will be placed. This is always a folder named Converted that will be located under the Input Folder path.

Recordset – This combo-box is a GovernId that will be used to group records in Govern. This should be the same GovernId that is configured for the Profile that will be using the SSRS report.

Convert – Click Convert to run the conversion process.

Files to process: – The Files to process area will display all reports within the Input Folder. After a click on Convert, the report names with their status will be listed along with an indication as whether files were converted successfully, or if any issues were encountered during the process.

About the Conversion Process

Users should note the following about the conversion process:

  • The original .rdl file will not be modified.
  • The output file will always add the Parameters SERVER, DATABASE.
  • The parameters RECORDSET_{GOVERNID} will be added if the value for RecordSet is not empty.
    • For example, if the selected value is p_id, the parameter to add will be RECORDSET_P_ID.
  • The datasource connection string will be overridden with the following:
    =”Server=”+ Parameters!SERVER.Value +“;Database=” + Parameters!DATABASE.Value
  • The reports generated in the Output folder are the ones that should be submitted/replaced in the SSRS Server Folders.

 

See Also

301-ssrs

301-ssrs-changes

 

 

301-ssrs-util

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

Database Extraction Tool

Database Extraction Tool

Overview

The purpose of the Database Extraction tool is to create a new database that contains only specific, required information. This database is smaller and therefore easier to manage. Performance is better than the original.

The new database is created from data extracted from an existing Govern database. It contains the same schema as the original database but the data, property records, Profiles, and functions it contains are restricted to one or more modules, one or more years, and a saved dataset. A saved dataset is a predefined set of records that is created in Govern. Note that all the dependencies that are required for those records are also copied.

An extracted database can be useful in troubleshooting, testing, or training. For example, you may want to create a demo on a laptop computer and need only the data from the previous assessment year. You may want to test a new tax rate and need all the tax and CAMA tables but only specific property records. You may need to do some troubleshooting and want to send a portion of the database to a team working in a remote office.

The new extracted database is used in a deployment, as any other standalone Govern database. Once it is created, it is independent of the original database. It needs to be updated and maintained separately. It is designed for temporary use. Whenever you run the Database Extraction on it, the existing data are deleted and replaced with the selected data from the source database.

The new extracted database is:

  • Reduced in size
  • Easily transferred to another computer or to another team
  • Contains only the data essential to a specific purpose
  • Provides better performance due to the small size

The database extraction tool:

  • Reduces the time required for creating a new database
  • Reduces downtime over a full backup and restore
  • The source database operates independently of the extracted database.

 

Read More...

 

Documentation

For a comprehensive pdf of this page, see the following document:
103-UT-110-DatabaseExtraction.pdf

Prerequisites

Access to the:

  • Source database and deployment
  • Destination database.
    This can be any SQL database, such as an empty database, or a database from any Govern version.
    All existing data and tables are removed from the destination databae at the beginning of the process.
  • Destination deployment, if one exists
  • Connection keys for both databases

 

Recommendations

  • Complete a successful database verification on the source database.
    For details on running a database verification, refer to the GNA documentation.
  • Back up your source database before beginning.
  • If you need to retain any data in the destination database, back up the database.
    The process clears all data from the destination database.
  • Ensure that a saved dataset exists in the source deployment and that it contains all the required records.
  • All dependencies are copied along with the records in the saved dataset.
    For example, the A/R records that are associated with the tax records in the dataset are copied. These include the property control records that are associated with the CAMA records.The only records extracted are those in the saved dataset and the dependencies of those records.

References

  • For details on creating on a saved dataset, see Saved Dataset
  • For details on creating a new deployment, see Deploy EZ

Extracting a Database

The Database Extraction Tool:

  • Deletes all data in the destination database.
  • Copies the Govern database schema from the source to the destination database.
  • Copies the parameters and settings, for the selected years, from the source database for the following options if they are selected:
  • Billing: All parameter tables beginning with AR_, MB_, or UB.
  • Land Management: All parameter tables beginning with PM_,
  • Mass Appraisal: All parameter tables beginning with MA_ and TX_
  • Tax: All parameter tables beginning with AC_, AR_, BT_, MV_, NA_, PP_, ST_, and TX_
  • Fiscal years
    Data from all tables for the range of years, selected in the From and To drop-down lists for the selected Saved Dataset.
  • Saved Dataset
    All Profiles and user forms required for the records in the dataset, as well as all dependencies, are copied.

A full list of all the tables that are copied can be viewed in the following file:

MSGDatabaseStructMods.xml

This file is accessed from the SystemFiles folder for your deployment.

To create an extracted database from an existing database:

  1. Log on to the server where the source database resides.
  2. Launch GNA.
  3. Select Utilities > Database Extraction.The Database Extraction tool opens:
  4. Select the connection key to the destination database from the Temporary SQL Database Connection Key drop-down list.
  5. Select the saved dataset from the Include Data from Saved Dataset drop-down list.Note: You can select only one dataset.
  6. Select the modules for the parameters that you want to copy from the source to the destination database.
    Tip: If you hover your mouse over the option for the parameter, a tooltip listing all the tables appears.
  7. Select a range of years for the selected parameters from the From and To Years drop-down list
  8. Click the right arrow to start the process.
    A confirmation message appears.
    This message warns you that the process deletes all data in the destination database.
  9. Click Yes to continue.

 

Using the New Database

Once the database extraction process is complete, the newly extracted database is ready to use. You can make it available to a remote team via ftp, or open it in any deployment, with the correct version number. You are ready to begin testing, troubleshooting, or training. The extracted database is the same as the source database.

Maintaining the Extracted Database

Once the procedure is complete, the extracted database is a standalone database that can be used as any other Govern database. You can run ad database verification, update the database or make modifications as you would to any other database.
There is no synchronization between the source and destination databases, once the process is complete.

 

 

 

103-ut-010

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

103-UT-001

Active Directory Integration Tool

Overview

Active Directory (AD) is an implementation of the Lightweight Directory Access Protocol (LDAP) directory services by Microsoft. LDAP provides central authentication and authorization services for Windows based computers. AD is available in Windows Server 2000 / 2003 / 2003 R2 / 2014. The Active Directory Govern Integration Tool will allow you to import users from Active Directory into Govern’s user database. This administrative process is unidirectional in that users are copied from Windows™ Active Directory to Govern’s user table (Table: USR_USERFILE); in addition their group designations within Active Directory will be carried over and used to determine which one of the four Govern access groups they will be assigned to. Once imported into Govern, you can then manage which forms and functions users will have access to through Govern’s Administration program. The import Active Directories process can be run periodically for synchronization purposes, e.g. in instances when there have been changes in roles or personnel within the organization.

Managing Import of Multi-role Active Directory users

In the Govern New Administration (GNA), there is a method of processing imported accounts in place to manage Active Directory users with multiple access roles.
In instances where a user being imported is in multiple roles in Active Directory; this could be a user that is in an Administrator group, as well as a Regular group. After this user is imported into Govern, in the Govern USR_USERFILE table, this user will appear once as an Administrator. This the role that they are a member of with the highest permission level.
The Permission hierarchy in Govern, highest to lowest is as follows:

  • Super User
  • Administrator
  • Regular
  • Read Only

To display the Active Directory and MS Govern Integration Tools:

  1. In GNA click to select the Utilities tab on the ribbon, Click Active Directory Integration Tool.

Parameters & Command Buttons

Command Buttons

Process: Click Process to begin importing Active Directory users into Govern.
View Log File: Click View Log File to display the contents of the log file.
Exit: Click Exit to close this window.

Parameters

Active Directory Path: This is the Active Directory path.
Log File Path: This is the path to the Active Directory Integration Tool log file.
Import Active Directory Users into MS Govern Database: Select this option to import Active Directory users into Govern’s database.

 

 

103-ut-001

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

 

OpenForms Reference

OpenForms Reference

Overview

The following is listed for information only. When there is a discrepancy, refer to the List of Changes Tables section of the Govern Database Diagrams page for the latest information and changes in the database structure or forms.

EMT Tool (Import Export)

XML files are located in the system library under:

  • FormReference.xml
  • DynamicSearch.xml

List of OpenForms Standard Forms

The following are links to the list of OpenForms standard forms that are found in the OpenForms release reference database.

Changes

Read More...

Changes made to the OpenForms supported items (forms, models, system tables, etc.) will be listed by date and version on this page (100-ofr-new). We suggest you setup a notification if you are in an implementation project or just to be informed.

Tables deleted or obsolete

OFR Product Catalog Codes

System Module Type Version Name OFR
101 ma ofr 1 [v6.0] CAMA Building Drawing ma001
101 ma ofr 14 [v6.0] CAMA Property Info ma014
101 ma ofr 15 [v6.0] CAMA Sale info ma015
101 ma ofr 17 [v6.0] CAMA Land ma017
101 ma ofr 21 [v6.0] CAMA Value Override ma026
101 ma ofr 26 [v6.0] CAMA Buildings (contains BSE) ma026
101 ma ofr 71 [v6.0] Combined CAMA Prop Info (014) + PC Area (017) + PC Legal (018)
101 na ofr 1 [v6.0] Name & Adress na001
101 na ofr 2 dash [v6.0] Name Summary na_sum
101 na ofr 35 [v6.0] Name Linking na035
101 pc ofr 1 [v6.0] Property Parcel Information pc001
101 pc ofr 2 dash [v6.0] Property Summary pc_sum
101 pc ofr 17 [v6.0] Property Area pc017
101 pc ofr 18 [v6.0] Legal pc018
101 pc ofr 38 [v6.0] Deed pc038
101 pc ofr 39 [v6.0] Combined PC Parcel (012) + PC Property Location (004)

 

 

100-ofr

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...