Hide rows in Webi Table

[#1]

Hi,

   I have read many forum posts on this topic but have yet to find one that provide a proper solution.

   How can I hide rows in Webi Table, let say always first 12 rows.

   I know people have suggested using conditional formatting and make the font and border white colour to make it not visible in reading mode. This doesn't work in my case as it mean I need to hide 12 rows. It will show big blank gap on the page. Is there a function to physically "hide" first x number of rows.

    Anyone able to achieve this using Filtering or similar? Any advise will be greatly appreciated.

Regards,
Ken

[Former Member · Accepted solution]

Hi

Here i have the example to hide first 12 rows.

Below table contains country and their actual values.here i need to hide first 12 rows(Hide till china)

For that i have created one variable

Just drag and drop that variable to our table.

Apply table level filter

Hide that Filter 12 rows column using conditional formatting.

Hope this will be helpful!

[former_member188911 · Accepted solution]

maybe the function RowIndex() can help , have a try

[rishabh_singhania]

Hi Ken,

Here is a trick. Hope it works for you.

Create a variable "=RunningCount([Di])"  where Dim has a unique value.

Select the block and add a report level filter on this variable.

For eg. the RunningCount variable name is var1, then the filter can be like:

var1 GreaterThan 12 (to hide first 12 rows)

Regards,

Rishabh

[Former Member]

What is the version of BO you are using?

[Former Member]

BI 4.0 SP2

Don't believe the newer version have introduce anything new other than Folding feature.

This will not work as it will hide all rows and only show aggregated data (Total Row).

I need an ability to only hide X amount of rows. (e.g. Always the first 12 rows for example)

[Former Member]

Correct.

Try creating a Flag varaible ( eg: Running Number or Running Count ) and apply it as a block level filter.

[Henry_Banks]

If you are getting unexpected behaviour on SP02, that would be because it is unsupported due to the huge number of bugs which are now solved in the SP04 Patch4.10 and SP05 Patch5.3 codelines. You could be investigating a problem which was solved 2 year ago.