Crosstab bind border-style with group change

[Benedikt]

Hey,

I'm currently trying to use the crosstable in a new Report.
In it I have 3 Row Groups and 1 Column Group.

I now want, bigger lines when the row groups change.
So a 3pt Line when next day and a 2pt line when next "Lager".

The problem is I dont get it done as soon as I have a column group.

I tried a lot of different variatons of the example with Previous, I tried Exec.
But still not even a bit achieved what I want.

With this: Exec('value', 'group0', Fields.Ladetag) I get the value of the Ladetag of the current row group.
But to achieve what I want, I would also need the value of the Previous row of the group. 
And here I'm lost.
I cant combine Previous and Exec.
I read abous user functios but what could I pass it...

Maybe someone has an idea.

Greetings,

Benedikt

[Todor]

Hi Benedikt,

You are correct that the Previous and Exec data functions cannot be embedded within each other in Expressions. Note that the Previous function supports the 'scope' argument.

Here are the options I suggest:

• A. Known Workarounds for modifying Crosstab/Table cell appearance based on the incoming data:
  
  • Show Borders Only Around A Group in Crosstab
  • How to Merge Cells from Different Groups in Table/Crosstab

• B. Custom User Function:
  If your grouping logic is complex or you need to evaluate previous values across both row and column groups, you can implement a custom user function.

  • Pass the required fields as parameters. For example, pass the current and previous group values (if you can determine them in your data source or via calculated fields).
  • The user function can then return the desired border thickness based on your logic.

• C. Preprocessing Data:
  As an alternative, preprocess your data before binding it to the report. Add a field indicating whether a group change occurs on each row. Then, use this field in your border expression.

If the problem persists, consider opening a Support Ticket where to share your runnable report with sample data for preview purposes. We will investigate it and try to suggest a more specific workaround.

Regards,

Todor
Progress Telerik