RegData access properties not on Report

Сonversation on different topics
Post Reply
robinpearce
Posts: 38
Joined: Thu Apr 02, 2009 5:54 am

RegData access properties not on Report

Post by robinpearce »

Hello,

In our code we do the following.
1. We call RegData on the StiReport passing in an object
2. We load the report from a path.

I have noticed that when I call RegData it gets the values of all the properties in the object. I know I can stop it doing this for specific properties by using the browable attribute like [Browsable=false], however the default behaviour seems strange to me.

If I have an object with 100 properties in, but I am only including 3 on the report, I do not want it to access the other 97 properties. Similarly if that object is being used on another report which accesses a different set of properties I would expect it to only access the properties that report needs. Is it possible to do this ?

Thanks
Robin

Jan
Posts: 1265
Joined: Thu Feb 19, 2009 8:19 am

RegData access properties not on Report

Post by Jan »

Hello Robin,

I agree with you, but main question - how report engine can detect which properties can be used and which no?

Thank you.
robinpearce
Posts: 38
Joined: Thu Apr 02, 2009 5:54 am

RegData access properties not on Report

Post by robinpearce »

I suppose I may expect the RegData method to use Reflection or something to get a list of all the properties, but not to actually access them (i.e. I would not expect it to call their "get" methods). I would then expect when the report is run for it to only access the properties which are actually included in the report.

I suspect that the way it works now (i.e accessing all properties) is fundamental and will not change. If this is the case can you just confirm it.

Many thanks
Robin


Jan
Posts: 1265
Joined: Thu Feb 19, 2009 8:19 am

RegData access properties not on Report

Post by Jan »

Hello Robin,
robinpearce wrote:I suppose I may expect the RegData method to use Reflection or something to get a list of all the properties, but not to actually access them (i.e. I would not expect it to call their "get" methods). I would then expect when the report is run for it to only access the properties which are actually included in the report.

I suspect that the way it works now (i.e accessing all properties) is fundamental and will not change. If this is the case can you just confirm it.
I confirm this behavior. During RegData report engine convert business object to Ado.Net DataSet. Report engine check all properties and its types during business objects examination.

Thank you.
robinpearce
Posts: 38
Joined: Thu Apr 02, 2009 5:54 am

RegData access properties not on Report

Post by robinpearce »

OK Thanks Jan.

As long as we are aware that is the case that is fine.

Thanks for your time
Robin

hadisaadat_du
Posts: 35
Joined: Tue Nov 09, 2010 2:43 pm
Location: iran

RegData access properties not on Report

Post by hadisaadat_du »

Hi every body.
I sea allmost all topic in forum and seem int all of them posit that we know what is our tables and columns in dataset of our reportbut allways not thus
1-sometime we may want to edit the report in webdesigner that we dont know any thing about its data set but we sure it works with our data base , so befor call the design() function we pass what data set to our report via regdata(//what_dataset) ??
2- or we may want to set full access to data base to one user to create the every report that need to design well we pass a full data base to designer dictionary and he/she design every report by every columns in every tables or viwes in database and save it , in viwe report mode namely after load our report and we want to pass it to stiwebviewer we pass what data set to it since we cant pass all data base to our report ??!
Post Reply