Creating reports and dashboards | Stimulsoft community forum

Hi,

We have a question regarding the Condition Property of a CrossSummary in a CrossTable.

In your Cross-Tab-Example in the Demo.exe ("CrossTab with Highlight Condition"), you have added a Condition where the "Field is" ComboBox is set to "Expression" and you are checking if "value < 20".

The CrossSummaries in our CrossTab are filled with strings from a DataTable in a DataSet. We actually need to have the "Field is" ComboBox set to "Value" and check a certain "Column" for a certain value. The problem is, that this does not work.

I know that the CrossSummary fires the ProcessText Event and this obviously only checks each Cell in the CrossTable for its displayed value. But we need to check a value that is not displayed but belongs to a certain cell.

For example: The cells of a CrossTab are used to display supplier-names. You want the Font-Color of all Suppliers who offer less than 30 items to be red. The supplier names and the number of offered items are located in a DataTable (or DataSource) but you only display the supplier names in the CrossTable. The Problem is, that you don't need to check the supplier name but the amout of offered Items to find out, which supplier should be displayed in red.

Do you know a way or workaround to solve this problem? Its quite hard to explain, but I hope you understand, what I mean.

Thank you,

Alex

Unfortunately it is impossible to achieve this a result with a current version of the Stimulsoft Reports.Net.

Thank you.

Depending on the data you are displaying in the crosstab it may be possible to do something like this using CrossGroupHeaders and CrossDatabands. It's not the cleanest method but I managed to accomplish it for a certain report I needed to create. My Datasource had a boolean column in it that determined if a cell should be highlighted in red or not so I was able to manage this with some workarounds and crossdatabands.

I'm not sure it would work in all scenario's but if you can share some sample data and datasource columns I might be able to convert it into a sample based around my real one. I can't guarantee it would work though as mine was a special case

Brendan wrote:I'm not sure it would work in all scenario's but if you can share some sample data and datasource columns I might be able to convert it into a sample based around my real one. I can't guarantee it would work though as mine was a special case

Hi Brendan,
thanks for the help offered, I really appreciate it.

Brendan wrote:Depending on the data you are displaying in the crosstab it may be possible to do something like this using CrossGroupHeaders and CrossDatabands. It's not the cleanest method but I managed to accomplish it for a certain report I needed to create. My Datasource had a boolean column in it that determined if a cell should be highlighted in red or not so I was able to manage this with some workarounds and crossdatabands.

You are right, you can solve this issue by using CrossDataBands. The problem is, that with CrossDataBands it is not possible to display row headers (CrossBandHeader) on every page if you have an amount of columns that won't fit on one page (unlimited width property in page properties). But I need to have this functionality and this is the reason the only option I had left was to use CrossTables.

The company I work for is still evaluating if Stimulsoft will fit all its needs. That means we are only using the Demo version and don't have the source code (that would help a lot). So far we have had only good experiences with the software and the support offered, but right now we're kind of stuck with that problem. I suppose, I'll just have to find some way to make it work... If I do, I'll post it.

Ok, thanks again for your help.

Alex

Hello Alex,

We have made some changes in our report engine. Now you can use in CrossTab conditions following variables:
So, if you need check additional parameter in condition you need assign this parameter as expression to Tag property. After then you can use following expression in conditions:
Changes will be available in next prerelease build.

Thank you.