Guides/Fusion.md
... ...
@@ -51,7 +51,7 @@ fusionDriver.AddConnection("OrclNW", FusionConnectionType.OData, "http://www.pro
51 51
52 52
The Izenda Fusion Driver has several additional settings:
53 53
54
-####1) VisibleDataSources
54
+####a) VisibleDataSources
55 55
56 56
This is setup the same way as for a single connection. Only data sources with the specified names will be available:
57 57
... ...
@@ -59,7 +59,7 @@ This is setup the same way as for a single connection. Only data sources with th
59 59
fusionDriver.VisibleDataSources = new string[] { "Orders", "Customers", "Order Details" };
60 60
```
61 61
62
-####2) Constraints
62
+####b) Constraints
63 63
64 64
This is setup the same as for single connection except that you are able to specify separate constraints for each connection by using connection nicknames. Note that you can use wildcard characters to set up constraints:
65 65
... ...
@@ -68,7 +68,7 @@ fusionDriver.AddConstraint("SqlNW/Order.Id", "SqlNW/*.OrderID");
68 68
fusionDriver.RemoveConstraint("OrclNW/Account.Id", "OrclNW/User.AccountID");
69 69
```
70 70
71
-####3) ReportingConnectionString
71
+####c) ReportingConnectionString
72 72
73 73
If reports are stored in the database you should specify connection string to that database. Note that in addition to this, you should also use FusionAdHocConfig instead of DatabaseAdHocConfig. The following example sets up the connection string to the database using the reports table. If you store reports in the file system then skip this step(use FileSystemAdHocConfig if you do this).
74 74
... ...
@@ -76,7 +76,7 @@ If reports are stored in the database you should specify connection string to th
76 76
((FusionAdHocConfig)AdHocSettings.AdHocConfig).ReportingConnectionString = "server=(local);database=Reports;Trusted_Connection=True;";
77 77
```
78 78
79
-####4) Set up cache
79
+####d) Set up cache
80 80
81 81
Getting data from several data source providers may take a lot of time and resources when many connections are added. This will result in a slow connection to the providers due to large amount of data being transferred, etc. That’s why the cache is enabled by default for the Izenda Fusion Driver. By default, cache expiration time is set to 12PM on Saturday. This means that every Saturday, the cache will be cleared and all data will be requested from the providers during the next session.
82 82