Sometimes, you might be tempted to manually delete unwanted elements from an entity. This can be done, but it is important to consider the potential consequences this action might have.
Look at the examples below.
Let’s imagine that you have an infocube with three dimensions: customer, product and month, and you have created three different versions for that infocube:
- Version 1: Month, Customer and Product
- Version 2: Month and Customer
- Version 3: Month and Product
Now access the “view” panel of the entity customer and remove one item manually.
In the example let’s assume that you have only three customers (a,b,c - you remove the first) and two products (x,y).
Let’s analyse what happens in each of the three versions:
- Internal ID (an incremental ID generated when adding elements to the entity)
This incremental number is used by BOARD to uniquely identify every entity element in screen and procedure selections.
Assuming that an element of the Entity Test is manually deleted, a subsequent extract/clear/reload of that entity, might result in selections applied on the same entity being different from before.
Let’s consider this entity:
In a procedure, there is a selection on the “f” item, the entity item with ID = 3.
Then the member "a" is deleted:
And then an entity clear and extract and reload is performed:
The procedure selection now selects the item "x" that has the ID = 3.
Before deleting items you should:
- Check that there is no value linked to these items in all your database cubes that use that entity as dimension
- If there are values, you have to proceed to align all cube versions that use that entity as dimension with an “align all” command
- Check that the item is not used into any Rule Formula
- Review the selections after an extract and reload if you think there are Selects on such item