cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Analytics Cloud (SAC) - empty rows in Table appear for no reason

M_Fuchs
Explorer
0 Kudos

Hey all,

i copied a story Table to keep some of the formatting and my styles within the designer panel. All of a sudden i realized (i think after transporting between tenants) that there is empty rows below my table entries. When i enable the pagination feature on the table it gives me 5 pages, whereas the first page is the casual table and the last 4 pages are just the header & empty rows. If i disable the pagination, there will just appear a scrollable table, which is unreasonably long & scrollable. Obviously i could just redo my table but i wanted to post this here to save me some work of remodeling a lot of stories, since this is happening to a lot of my tables. 

fyi: I am using a BW live model within unified Stories, no coding.

To summarize : My tables looks totally fine, but underneeth i have these empty rows which are not supressable through common available options within SAC - i think its a bug but im happy to find a solution.

m_fuchs1_0-1709814792786.png 

or not paginated :

m_fuchs1_1-1709814866547.png

Thanks for taking the time,

Mirko

 

SAP Analytics Cloud #SAC

 

Accepted Solutions (0)

Answers (1)

Answers (1)

lucasborges
Explorer
0 Kudos

Hi Mirko, one possible reason that you have empty rows at the end of your table is that it was added manually (and accidently) during development. The UI is a bit tricky and one can easily do it without realizing it. So, if that's your case you would need to remove them manually clicking the minus ("-") button at bottom of the table. Cheers

lucasborges_0-1709888875665.png

Hint: by showing the grid, it is easier to identify any empty rows/columns.

lucasborges_1-1709888934571.png

 

M_Fuchs
Explorer
0 Kudos

Hi lucas,

Thank you so much for the holistic answer, unfortunately i considered all your aspects in my analysis - i actually rebuilt all the stories since every single one of my approaches did not work - i am pretty sure this was a bug occuring by cloning stories and transporting them.