cb52ffa8df7e5871cf086da18c7b306e07f2a671
Virtualdatasource.md
| ... | ... | @@ -1,6 +1,20 @@ |
| 1 | -If you wish to use one of the reports already created as a data source instead of existing tables. Virtual Data Sources can be used with direct database connections and with direct fusion connections against datasources (MsSql, MySql, Oracle, etc.). This feature is NOT compatible with OData datasources. |
|
| 1 | +[[_TOC_]] |
|
| 2 | 2 | |
| 3 | -1 -- Set AdHocSettings.AllowVirtualDataSources = true; |
|
| 3 | +##Question |
|
| 4 | + |
|
| 5 | +What is a virtual data source? How do I create one, and what is it used for? |
|
| 6 | + |
|
| 7 | +##Answer |
|
| 8 | + |
|
| 9 | +A virtual data source is an Izenda report which can be used as a data source. You can think of it as creating a simulated view, in Izenda. It can be used for multi-level calculated fields |
|
| 10 | + |
|
| 11 | +Virtual Data Sources can be used with direct database connections and with direct fusion connections against datasources (MsSql, MySql, Oracle, etc.). This feature is NOT compatible with OData datasources. If your environment is using VisibleDataSources to define or trim datasources, you might also experience difficulty getting virtual data sources to appear in the data source menu. Virtual data sources do not automatically update, they are cached based on the behavior of the underlying report - to update a VDS, you must update the report which is used to construct it. When VDS is enabled, data sources will appear as links on the data source menu. Each link shows a popup that displays the name of every report which is built using that data source. |
|
| 12 | + |
|
| 13 | +###Step 1: Enable Virtualdatasource |
|
| 14 | + |
|
| 15 | +To use virtual data sources, you will have to change a setting in the global.asax. Set AdHocSettings.AllowVirtualDataSources = true; |
|
| 16 | + |
|
| 17 | +####Code Sample |
|
| 4 | 18 | |
| 5 | 19 | ```csharp |
| 6 | 20 | //main class: inherits DatabaseAdHocConfig or FileSystemAdHocConfig |
| ... | ... | @@ -21,14 +35,17 @@ public class CustomAdHocConfig : Izenda.AdHoc.DatabaseAdHocConfig |
| 21 | 35 | } |
| 22 | 36 | ``` |
| 23 | 37 | |
| 24 | -2 -- Create a report as usual |
|
| 25 | -3 -- In Misc. Tab, near the bottom click the checkbox that says, "Expose as data source." |
|
| 38 | +###Step 2: Create Report |
|
| 39 | + |
|
| 40 | +A virtual data source is simply a typical Izenda report, except the output is used as a table for one or more other reports. Once the virtualdatasources setting is toggled to true, any report you already have or create has the potential to be used as a virtual data source. |
|
| 26 | 41 | |
| 42 | + |
|
| 43 | +###Step 3: Enable report as VDS |
|
| 44 | +On the Misc Tab, above the drilldown key dropdown there is a checkbox labeled "Expose as Datasource". Checking this box then saving the report will cause the report to appear in the data source menu. |
|
| 27 | 45 |  |
| 46 | + |
|
| 47 | +###Step 4: Use VDS in new report |
|
| 28 | 48 | |
| 29 | -4 -- Make sure to save the report. |
|
| 30 | -5 -- Create a new report. The data sources will include the saved report preceded by the folder you saved it under. You will also notice some Data Sources have become links. When you select one, a popup will appear, displaying all of the reports that currently use that data source. |
|
| 49 | +When you create a new report, the data sources menu should include the full report name of the report which you just saved as a VDS. You may now build a report based on the output of the VDS report. |
|
| 31 | 50 | |
| 32 | 51 |  |
| 33 | - |
|
| 34 | -6 -- Continue as usual, except that your column choices will be limited by the columns you chose in the previously saved report. |
|
| ... | ... | \ No newline at end of file |