SQL TOP / Pagination controls for designers when working with matrices

Follow

Soren Staun

• May 16, 2018 13:48
• Edited

Hi there!

I think this is a great story since it's simply, speeds up work in MooD BA and can be easily implemented without conjuring up completely new ways of working inside BA.

As a MooDler / designer

I want to get only 10,50,100,ALL (some option list) rows when working with matrix design.

So That I won't have to modify the row query for faster execution.

Benefits Faster matrix design, better experience, intact row query.

Acceptance Criteria 

1. This should be independent of the Pagination settings, strictly for the designers in MooD BA
2. The settings should be remembered across matrices (so if I last picked 10 as the number of rows I want to see / have calculated, this will be the number to use for all subsequent design sessions for matrices until I change the number)
3. This setting should not be a per matrix setting.

Customer / Originator Orsted / DONG Energy

Priority Medium

1

• 

  Peter Kristensen

  • May 16, 2018 19:23

  I think I can supply a bit more background on this one.

  When creating a matrix I may set specific elements in variables to test the matrix. However, it is bad practise to leave the elements in variables as test, because "show where used" will them show false positive results for these elements.

  Still, I want the matrix to show some results by default, so I do not get an empty matrix when using it. I accomplish this by setting variables to "ignore". The trade-off is that some matrices can then get very huge, so I have to wait for BA to "display cells", which is annoying.

  This is why I see that it would be helpful to have a global setting in BA limiting the number of row results in a matrix.

  1

  Comment actions Permalink

Please sign in to leave a comment.