Deleting Entity Elements

Document created by ggallo Employee on Jul 13, 2017Last modified by ggallo Employee on Jul 13, 2017
Version 2Show Document
  • View in full screen mode

Deleting Entity Items: which consequences?

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.

 

Cube Version Alignment Check Failure

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:

  1. Version 1: month, customer and product;
  2. Version 2: month and customer;
  3. 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:

 

 

 

Version 1 (by Month, Customer, Product)

 

Deleting the item "a" deletes all the infocube version cells for that item for all products and months. It would be like cutting off the red slice of the infocube version.

The infocube version ground total is decreased accordingly to the customer total amount.

 

Version 2 (by Month, Customer)

 

Deleting the item "a" deletes all the infocube version cells for that item for all months. It is the same as if I cut the red slice of the infocube version. The infocube version ground total is decreased accordingly to the customer total amount.

 

Version 3 (by Month, Product)

 

Deleting the item a has no effect on such version since it doesn’t have the customer dimension. The infocube version ground total is the same.

 

 

 

Screen or Procedure Selection Failure

Every entity member is made of 3 attributes:

  • code
  • description
  • internal ID (an incremental ID generated when adding elements to the entity)
you can understand the loading order of the entities elements by sorting by ‘none’

 

This incremental number is the used by BOARD to uniquely identify every entity element in screen and procedure selections 

Imagining 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:

code

description

id

s

sample1

1

a

sample2

2

f

sample3

3

x

sample4

4

 

In a procedure, there is a selection on the “f” item, the entity item with ID 3.

Then the member “a” is deleted:

 

code

description

Id

s

sample1

1

 

 

 

f

sample3

3

x

sample4

4

 

And then an entity clear and extract and reload is performed:

 

code

description

Id

s

sample1

1

f

sample3

2

x

sample4

3

 

 The procedure selection now selects the item “x” that has the ID 3.

 

Conclusions

Deleting items can have different effects with severe consequences on the accuracy of your reporting and/or procedures.

Before deleting items you should:

1         Check that there are no values linked to these items in all your database infocubes that use that entity as dimension

2         If there are values, you have to proceed to align all infocube versions that use that entity as dimension with an “align all” command

3         Check that the item is not used into any Rule Formula

4         Review the selections after an extract and reload if you think there are Select on such item

9 people found this helpful

Attachments

    Outcomes