1. Tony Fahlberg
  2. SnapObjects
  3. Tuesday, 16 June 2020 02:19 AM UTC

Hi - We are exploring potential usages for your C# libraries.  We have clients who have created custom datawindows for reporting purposes and are trying determine how/if this can be supported.  We are thinking of using the PowerScript.Bridge.DataObject to load the .SRD and do the retrieve.

string path = @"C:\Temp\y_dw_custom_rpt.srd";
var syntax = File.ReadAllText(path);
// Creates a DataObject object using the SRD syntax
var dataobject = new DataObject("partdatatst", syntax);

// Creates a DataStore object using the DataObject object and DataContext object
var dataStore = DataStore.Create(dataobject, _dataContext);


QUESTION:  Is it also possible to use the ISqlExecutor to execute other queries matching the model and populate the dataStore (from above) that was created at runtime?  

string sql = @"SELECT --- FROM -- WHERE";
var listData = _dataContext.SqlExecutor.Select<TModel>(sql);


I am having issue specifying the TModel created from the .SRD.  I imagine this needs to use Reflection (and/or dataStore.DwMeta.ModelType) but am unclear how to do this (if possible).  Any help would be much appreciated.

Thank you, 



Accepted Answer
Logan Liu @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 17 June 2020 15:40 PM UTC
  2. SnapObjects
  3. # Permalink

Hi Tony,

Please try to use DynamicModel as the model type. Please refer to the following code:

// 1. Create a .NET DataStore object from .srd file.
string srdPath = @"E:\d_dept.srd";

var srd = File.ReadAllText(srdPath);

var dataObject = new DataObject(srd);

var dataStore = DataStore.Create(dataObject, _context);


// 2. Paste your SQL, which can retrieve the same columns as the dataStore created above.
var sql = "SELECT ... FROM ...";

// 3. Get a sequence of DynamicModel objects.
var dataList = _context.SqlExecutor.Select<DynamicModel>(sql);


For more details about DynamicModel, refer to:




  1. Tony Fahlberg
  2. Wednesday, 17 June 2020 18:13 PM UTC
Using the DynamicModel instead of the model from the dataSource created from the .SRD appears to be limiting. I do not seem to have access to the computed columns (DWCompute) from the .SRD. I then tried to use dataSource.evaluate to execute some of the computed expressions retrieved from the .SRD meta data and it fails (most likely because of the DynamicModel).

So, there is no way to use the model from the dataStore created from the .SRD as the <TModel> in SqlExecutor?

  1. Helpful
  1. Logan Liu @Appeon
  2. Thursday, 18 June 2020 15:19 PM UTC
Yes. If the properties of the two DynamicModel objects are different, it may cause some issues.

There still seems to be no better way to use the model from the dataStore created from .SRD as <TModel> in SqlExecutor.

I suggest to submit this issue as an enhancement request to improve the compatibility of different DynamicModel objects.
  1. Helpful
There are no comments made yet.
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 16 June 2020 20:38 PM UTC
  2. SnapObjects
  3. # 1
  1. Tony Fahlberg
  2. Tuesday, 16 June 2020 21:33 PM UTC
Hi - I did see that documentation but it is only half of what I am attempting to do. I can get that part working (as documented) but was also trying to use the ISqlExecutor to execute other queries matching the model and then adding the results to the dataStore (created from the .SRD). Something like the following...

string sql = @"SELECT --- FROM -- WHERE";

var listData = _dataContext.SqlExecutor.Select<dataStore.DwMeta.ModelType>(sql);


Where I am having issues is when executing the SqlExecutor I am trying to specify the <TModel> from the dataStore created from the .SRD and am unclear as to how to do this (if possible).


  1. Helpful
There are no comments made yet.
  • Page :
  • 1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.