Selection in Screen after Reload of Entities

Dear all,

we wanted to clean up our database from entities, that are not needed.
I decided to do it from scratch. Therefore we are extracting the cubes, clear the entities, reload the entities and reload the cubes.

Looking at some reports I noticed, that the selection in the capsule/screen has changed (see screenshot).

Is there any way to "avoid" or correct this problem? What is the main cause of the issue? We thought the selection would remember the code value of the selection.

Thank you and kind regards

The upper image is after clearing and reloading the entities

------------------------------
Steve Pankrath
BI & DWH Specialist
JOST-Werke Deutschland GmbH
Germany
------------------------------

Find more posts tagged with

Accepted answers

All comments

Bettina Clausen

Hi Steve,

when extracting entities please make sure that the sort by setting is set to "None". This way, the list will be exported in the order they have been uploaded (exception: if you have deleted manually some members, than the order will vary).

Please note that Board remembers for selections the internal id for each entity element and not the code!
That means, that the first uploaded elements gets the internal id 1, the second one the internal id 2 and so on. If one element has been deleted the internal id remains blocked and will not be filled up with a new element.

I hope this helps

Best regards
Bettina

------------------------------
Bettina Clausen
Consultant
Board
Germany
------------------------------
-------------------------------------------

Steve Pankrath

Dear Bettina,

thank you for your response.
It does help to understand, but unfortunately we are not extracting the entities. We are reloading them from the data warehouse, in order to only load those that are needed in the Board database.
Is there any chance for a work around? Do you have any ideas?

Kind regards

------------------------------
Steve Pankrath
------------------------------
-------------------------------------------

Bettina Clausen

Hi Steve,

hm, there are different ways to cope with this issue.
Maybe one of these can help you:

Integration (manually or per datareader) of the entity elements that are used for selections. This needs to run before the full upload from the data warehouse runs. In this solution only the "top" members (that are integrated from the first step) of the entity should be selected.
Using dynamic selection in the screen. Here you can calculate a selection cube automatically based on the code (e.g. by using an if-statement in the dataflow). Using this method, the selection is not depended on the order of the elements since the if-statement goes on the code like if(or(b="A",b="B"),1,0).
Using a "reporting" entity above the original entity. The "reporting" entity is used for the frontend (in selectors/pagers/axes/...) and only contains the needed elements. The entity beneath (the original one), however, cannot be cleared since selections are made on this one.

Best regards
Bettina

------------------------------
Bettina Clausen
Consultant
Board
Germany
------------------------------
-------------------------------------------

Steve Pankrath

Hi Bettina,

thank you.

The dynamic selection sounds like a lot of work and a lot to do. We have about 40-50 capsules (not sure if all are used), that contain several screens and all of them have some kind of selection (not considering the time selection).
A reporting entity would be the opposite of what we are trying to accomplish. This would mean more entities with more entries. So this does not seem like a solution for our case.

Can you go a bit into the detail concerning your first point about Integration? I did not understand the idea behind it.

Kind Regards
Steve

------------------------------
Steve Pankrath
------------------------------
-------------------------------------------

Bettina Clausen

Hi Steve,

if you have an entity for example where there are 5 elements always relevant for selections and 50 elements not, then you can upload/manually integrate the 5 elements into the cleared entity so they have the internal ids 1-5. The other 50 elements will be included by the datareader from the data warehouse. That way you can clear the entitiy as much as you want, but with the two datareaders you can make sure that the order of the selection-relevant elements stays the same. Of course it depends on the entity, if this might make sense.

Best regards
Bettina

------------------------------
Bettina Clausen
Consultant
Board
Germany
------------------------------
-------------------------------------------

Steve Pankrath

Hi Bettina,

thank you. We will take a look into the topic and decide, what we will do.

Kind Regeards

Steve

------------------------------
Steve Pankrath
------------------------------
-------------------------------------------