[Solved inelegantly] Rebuild very slow after a datable is assigned to a dataset in the rdl

[EmanueleBonin]

I wrote this method in a my class;
public void SetDataSource(DataTable TableSource, int DataSetPosition) {
int Counter = 0;

		foreach(fyiReporting.RDL.DataSet D in  Viewer.Report.DataSets) {
			if(Counter == DataSetPosition) {
				D.SetData(TableSource);
				break;
			}
			Counter++;
		}
		//Very Slow
		Viewer.Rebuild();
	}

but even if in the table there are few records the rebuild is very slow.

[EmanueleBonin]

After many test i have found the problem, but not (for now) the solution.
The problem is that in the report there is defined a sql datasource that have a connection string used to test the report in reportdesigner. this connection sring is invalid in production, even if i passed a datatable with all data, the rebuild seem to try to connect ... if fails connection without any warning. The result is that to print a simple label it takes 20 seconds plus or minus.
NOW i tried to eliminate brutally the connection string ... but the report emit error. Any Suggestion to avoid the connection on rebuild() ?

[EmanueleBonin]

After other test. A brutal solution is setting the flag shared datasource reference and leave blank the field. Isn't elegant. So my question is there is a way to programatically do this ?

[Kernel-Klink]

Not sure I fully understand the issue. But what I do, is I dynamically pass the connection string in via a report variable. This allows me to use one connection string for testing and one for production; both stored in the web.config. Documentation is here: https://github.com/majorsilence/My-FyiReporting/wiki/Set-Connection-String---Runtime The Kernel

…

On Wed, Aug 29, 2018 at 3:35 PM EmanueleBonin ***@***.***> wrote: After other test. A brutal solution is setting the flag shared datasource reference and leave blank the field. Isn't elegant. So my question is there is a way to programatically do this ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#183 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AF32L6soRCyoeiUks53nxoeRm2wb5e9Kks5uVu0CgaJpZM4WIPZk> .

[EmanueleBonin]

First of all thanks for your suggestion but in my tests i tried to eliminate the connection string (in production i doesn't need it) but this emit error during printing. seem that the schema was deleted. ("error field is not defined" ... or something similar ... i don't remember). But if i ONLY set the check "Shared datasource definition" in my datasource (that was a sql connection) all things worked properly.
Inspecting the difference between two rdl files (before and after) you can see that datasources tag is modified:
Before

> 
>  <DataSources >
>     <DataSource Name="DS1">
>       <ConnectionProperties>
>         <DataProvider>SQL</DataProvider>
>         <ConnectString>data source=server;database=mydb;integrated security = true</ConnectString>
>         <IntegratedSecurity>false</IntegratedSecurity>
>       </ConnectionProperties>
>     </DataSource>
>   </DataSources>
>   
>   After
>     <DataSources >
>     <DataSource Name="DS1">
>       <DataSourceReference>
>       </DataSourceReference>
>     </DataSource>
>   </DataSources>