Skip to end of banner
Go to start of banner

Changing reports Database source to new Single Database Source

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Purpose

To provide step by step instruction on how to manually assign a new Database source to an existing custom report 

Responsibilities

  • Reports Developers
  • School System Administrators

Pre-requisites

  • SA equivalent Access
  • Access to Synergetic Reports Site Folder
  • Crystal reports Editor

Procedure

  1. Open up the Customised report in Crystal reports
  2. Select Database, Set Datasource location
  3. Select the Reports Data Source location (currently SynergyOne or SynergyOneFinance)
  4. In My connections you should have a "Synergetic" Data Source (Please note in Single Database there should only be a need for one Database ODBC Connector)
  5. Click Update
  6. Enter the Password for SA then Click Finish
  7. Repeat the process for each Subreport
  8. Once each Datasource has been corrected, ensure "Use DSN Default Properties" is set to true (Including Subreports)

Testing

  1. Run the report as usual
  2. Possibly make some test changes to the new Single Database instance to confirm that data is been pulled from the correct source.

Known Problems

  1. SA users unable to see all Tables, Views and Stored procs

    1. This is due to a 8000 object limit imposed by Crystal Reports which can be increased by modifying a registry key as described in https://apps.support.sap.com/sap/support/knowledge/public/en/1215994 

      Increasing this to 20000 should resolve this issue.
    2. Untick the Views, Tables or Stored Procedures depending on what you want to see in Crystal Options, Database Tab
  2. Confusion of how single Database works with a single ODBC Connector.
  3. There might be a separate ODBC connector called Synergetic_Finance this is actually the same as Synergetic (this possibly adds more confusion to the problem)
  • No labels