Differences

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

--- versago3:dataview_setup [2022/09/07 12:04]
dlee
+++ versago3:dataview_setup [2023/07/14 12:38] (current)
dlee [Stored Procedure]
@@ Line 49: / Line 49: @@
   * If the statement is correct, the first 50 records of the dataset are displayed in the “Results” area.
-===SQL Statement Restrictions===
+=== SQL Statement Restrictions ===
   * An **Order By** clause cannot be used except in cases where the statement contains a TOP operator. The ordering (sorting) is handled by the data view's Field Display settings
   * **Computed values** in the SQL statement must be assigned an alias.
-====B1 Query====
+==== B1 Query ====
 This option should only be used with connections to SAP Business One. This option allows to select user queries built in SAP Business One.
-====Stored Procedure====
+==== Stored Procedure ====
 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.
-=====View=====
+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====
 This option allows the use of a database View as the data source
-===== Crystal Report =====
+==== Crystal Report ====
-A different data presentation option is provided through the **Crystal Report** method. In this case a Crystal Report is developed outside of Versago. The report is then registered in Versago 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.
-  - Select the Crystal Report object type.
+<WRAP center round important 80% >
-  - A dialog box is presented to select the desired Crystal Report.
+The data source used in the Crystal Report definition **must** be the same as that of the Versago Data View connection.
+</WRAP>
-{{  :versago/reports23.png?352x137  }}
+  * Select Crystal Report as the data source type.
+  * A dialog box is presented where a Crystal Report definition file (.RPT) can be selected.
-  - Click [**Choose File**] to open the standard Windows Explorer tool.
+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.
-  - Locate and “open” the desired Crystal Reports file (.RPT).
-    - The file name is displayed in the Versago dialog.
-  - Click [**Select**] to associate the Crystal Report file with the Versago report.
-    - Once the file has been selected you will see file path information displayed in the Report Data Source box.
-{{  :versago/reports24.png?166x82  }}
+---
+=====**Need to review**=====
-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 added in front of the file name to ensure it always unique. 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.
+===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.
-<WRAP center round tip 80%>
+===HANA===
-General information about configuring Crystal Reports for use with Versago and Bizweaver is found **//[[Configuring Crystal Reports|here]]//**.
+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.
-</WRAP>
+<code>
+DRIVER={B1CRHPROXY32};SERVERNODE=<YourServer>:30015;DATABASE=<YourDB>
+</code>
+Replace <YourServer> and <YourDB> (without the < > symbols) with the appropriate values.
@@ Line 95: / Line 117: @@
 ----
+**[[versago3:dataview#Add/Edit Data View]]**
 **[[versago3:Home|Home]]**

Wiki

User Tools

Site Tools

Differences

Page Tools