max item number blocked

Hello,

We had an entity set on max item number no =auto. It worked well until one day the systèm blocked it to auto(471) and it didn't let us modifiy the value.

So we did the following steps:

1.Runan "Extract all Cubes" action

2. Runa clear all Cubes

3. clear the concerned entity and the associated tree

4. Change the Max item No to a fixed value

5. load the entity and the associated tree

6. Open the summary tile and unload the database

7. Run the "Import all Cubes" action

After performing the steps, it looked like the db lost all its indexes. Example: we had a layout fixed on Country Entity=France. After the change, the layout displayed "Germany". The Country Entity was not the one concerned by the Max Item problem.

The solution we found to solve the problem was to redo all steps on a backup and when performing steps 2 and 7, we've done them only on cubes that contain the Entity with the Max item problem.

Have you encountered this situation ? Do you know how to explain it or have another solution to solve it ?

thank you!

Find more posts tagged with

Accepted answers

Robert Barkaway

Hi Catalina,

When reloading an entity which has hard-coded selects on it as Gadjeg says it's vital to ensure you load the members in the same order as before, this is because the internal index is determined by the order in which values are loaded. To ensure you load the values in the same order the easiest way is to set the entity sort to None and extract it to file, that will extract the values in the same order in which they were loaded allowing you to use that to reload the entity after resizing it. Just make sure you set the entity sort back to whatever you need it set to afterwards.

All comments

Gadjeg

Hello Catalina,

I think that you do not need to :

3. clear the concerned entity and the associated tree

in order to perform a change on a max number entity.

In fact your issue coming because you clear the entity and relaod it (apparently, you not loaded the entity the same way that you loaded it the first time.). You should have the same issue on all entity you cleared (depending if you load the entity exactly like the same way as the first laod, through csv file for example)

You can follow all your step without the 3rd one, and everything will be fine.

Tell us if it's well the case or not

Thank you

Gérald

Catalina

Hello Gérarld,

Normally we don't have to clear the entity for the max item number indeed, but the system didn't let us modify the auto value which the system fixed to auto(471), I don't know why. That's why we were forced to clear the entity. Did you encounter this situation ?

What you are saying, for the situation for which we need to clear the entity, is that we need to load exactly the same file we used for the creation of the entity ? Is there a way to extract it and make sur the indexes are the same when loading again ?

thank you,

Gadjeg

Hello,

You need in that case to Extract all trees and cubes and realod them (make sure to make a backup before :) ) :

Extract all trees (and cubes) through the procedure step (the path is not required):

3) Empty the entity and change the max item number (just the entity you want, not the tree -if Board allow you to do it-)

4) Relaod all entities (and cubes) throught procedure (the path is not required):

Let us know if it's works

Gérald

Bettina Clausen

Hi,

you might want to check out this article.
It explains how the max item number works and how it is linked to sparsity causing your encountered issues.

https://community.board.com/discussion/16439/auto-max-item-number

Robert Barkaway

Hi Catalina,

Catalina

Hello Gérald,

Thank you for taking the time to write in detail. That's what we deed indeed but at the reload all data was misplaced. I think Robert's answer above explains the situation.

Catalina

Thank you, Robert! I wasn't aware of this solution to keep the order at the reload. We will keep it in mind for the next time :).