Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Save a Bizweaver Workflow • Introduction (Import/Export)
versago3:dataview_setup

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
versago3:dataview_setup [2022/09/07 12:39]
dlee 		versago3:dataview_setup [2023/07/14 12:38] (current)
dlee [Stored Procedure]
Line 61: Line 61:
  
 In some rare instances it may be necessary to use an SQL Stored Procedure as the data source. This approach is not recommended if any other option is available. In some rare instances it may be necessary to use an SQL Stored Procedure as the data source. This approach is not recommended if any other option is available.
 +
 +Store procedure parameters must be configured in the **//[[versago3:dataview_filters|Filters]]//** page.
 +
 +
 +<WRAP center round important 100% >
 +**Stored Procedure Limitations**
 +</WRAP>
 +Versago uses the view sys.dm_exec_describe_first_result_set_for_object to determine the store procedure's result set schema.
 +However, there are limitations with the system view that restricts the use of some store procedures in Versago.
 +The limitations include the use of temp tables and dynamic sql in the store procedure.
 +
 +Use the following query to determine if your store procedure will be suitable to be used as a Versago data source:
 +
 +<code>
 +SELECT name, system_type_name 
 +FROM sys.dm_exec_describe_first_result_set_for_object(OBJECT_ID(@StoredProcedureName), 0)
 +</code>
 +
  
 ====View==== ====View====
Line 69: Line 87:
  
 A Data View can be configured to display a Crystal Report. When this option is selected, the Crystal Report definition file is uploaded to the Versago site and used as the presentation method. A Data View can be configured to display a Crystal Report. When this option is selected, the Crystal Report definition file is uploaded to the Versago site and used as the presentation method.
 +
 +<WRAP center round important 80% >
 +The data source used in the Crystal Report definition **must** be the same as that of the Versago Data View connection.
 +</WRAP> 
  
   * Select Crystal Report as the data source type.   * Select Crystal Report as the data source type.
Line 75: Line 97:
 The Crystal Report source file is copied from the original location to the folder “C:\Program Files (x86)\TWBS\Versago\Websites\Versago Administration Web Site\Reports.” A number is prefixed to the file name to ensure it uniqueness. If the Crystal Report needs to be modified, you can either modify this file or modify it elsewhere and re-register the new version in Versago. The Crystal Report source file is copied from the original location to the folder “C:\Program Files (x86)\TWBS\Versago\Websites\Versago Administration Web Site\Reports.” A number is prefixed to the file name to ensure it uniqueness. If the Crystal Report needs to be modified, you can either modify this file or modify it elsewhere and re-register the new version in Versago.
  
-======Configuring Crystal Reports for Versago and Bizweaver======+--- 
 +=====**Need to review**=====
  
-=====SQL Server=====+===SQL Server===
 When designing a Crystal Report that will use a __SQL Server__ database as its data source, the report connection type must be **OLE DB (ADO)**. This connection type has three options for the data provider: **SQL Native Client**, **Microsoft OLE DB Driver for SQL Server**, and **Microsoft OLE DB Provider for SQL Server**.  Any of these options should work with Versago. When designing a Crystal Report that will use a __SQL Server__ database as its data source, the report connection type must be **OLE DB (ADO)**. This connection type has three options for the data provider: **SQL Native Client**, **Microsoft OLE DB Driver for SQL Server**, and **Microsoft OLE DB Provider for SQL Server**.  Any of these options should work with Versago.
  
-<WRAP center round tip 80%> +===HANA===
-If you have problems with one provider (e.g. being requested for login information at runtime), try one of the others to see if that resolves the issue. +
-</WRAP> +
- +
-=====HANA===== +
 When designing a Crystal Report that will us a __HANA__ database as its data source, the report connection type be **ODBC (RDO)**.  **{{ :versago:b1h_90_ht_setupdsforcrl.pdf |This document }}** explains how to configure this type of connection for use with HANA.  Two options are described in the document.  Be sure to use the **B1CRHPROXY32** option.  Here is a sample connection string to use as a starting point. When designing a Crystal Report that will us a __HANA__ database as its data source, the report connection type be **ODBC (RDO)**.  **{{ :versago:b1h_90_ht_setupdsforcrl.pdf |This document }}** explains how to configure this type of connection for use with HANA.  Two options are described in the document.  Be sure to use the **B1CRHPROXY32** option.  Here is a sample connection string to use as a starting point.
  
Line 94: Line 112:
 Replace <YourServer> and <YourDB> (without the < > symbols) with the appropriate values. Replace <YourServer> and <YourDB> (without the < > symbols) with the appropriate values.
  
-<WRAP center round important 80%> +
-Information about installing the needed HANA driver is found **//[[versago:versago_installation#hana_drivers_for_crystal_reports|here]]//**. +
-</WRAP>+
  
  
  
 ---- ----
 +**[[versago3:dataview#Add/Edit Data View]]**
  
 **[[versago3:Home|Home]]** **[[versago3:Home|Home]]**
      
versago3/dataview_setup.1662568752.txt.gz · Last modified: 2022/09/07 12:39 by dlee

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
CC Attribution-Noncommercial 4.0 International Valid HTML5 Valid CSS Driven by DokuWiki