Master data changing by year
Shuyu Kameda
Active Partner
Hello, everyone.
I am faced with a problem.
I need to create a database, but in the current system, the entity member names change every year.
Example:
2018 -> Product A
2019 -> Product A'
2020 -> Product A''
When referring to historical data, the display name needs to be changed depending on the year.
The way I figured it out is to have product A, product A', and product A'' as the root entity and its parent entity as product A.
I'm also considering creating a flag cube to control what data is displayed by year and setting it to filter.
My concern with this approach is that the cube size will increase due to the increase in entity members, which will affect performance.
The cube's axis contains at least three such entities, and the current estimate is that the number of entity members in each exceeds 100,000.
If there are other ways to solve this problem, please help.
------------------------------
Shuyu Kameda
------------------------------
I am faced with a problem.
I need to create a database, but in the current system, the entity member names change every year.
Example:
2018 -> Product A
2019 -> Product A'
2020 -> Product A''
When referring to historical data, the display name needs to be changed depending on the year.
The way I figured it out is to have product A, product A', and product A'' as the root entity and its parent entity as product A.
I'm also considering creating a flag cube to control what data is displayed by year and setting it to filter.
My concern with this approach is that the cube size will increase due to the increase in entity members, which will affect performance.
The cube's axis contains at least three such entities, and the current estimate is that the number of entity members in each exceeds 100,000.
If there are other ways to solve this problem, please help.
------------------------------
Shuyu Kameda
------------------------------
0
Answers
-
Hi Shuyu,
are all of your entity members changing?
Or is it only applicable to a certain subset of entity members?
If this is only applicable to a subset of entity members you can also use a hash function and create a root entity containing the description's hash value:
You cube would look like this if the product's name was changed in 03/2019:
This is also very interesting when entity members in your tree share the same attribute combinations.
Let's say you have 1.000 people "sharing" the same location, postal code, gender and peer group.
You will only need one row (entity member) for this entity "subset".
By the way, we didn't have any issues with 100.000+ members yet (except for MXC cubes of course).
It always depends on the MaxItemNumber combined with the number of dimensions used in your cube.
If you have 3 entities with each containing 100.000+ records, you should consider creating a root entity which combines all 3 of them (per month/week/day).
Kind regards,
Florian
------------------------------
Florian Deutsch
Berater
linkFISH Consulting GmbH
Germany
------------------------------
-------------------------------------------2 -
Thanks, Florian
I think your idea was very interesting.
Not all entities are changed.
I have three new questions.
First, do you generate the hash values in an external DB?
Second, I thought I could do the same thing by using a copy of the year entity instead of a hash value, is there any advantage to using a hash value?
Third, if you create a root entity with multiple entities combined, does the structure look like this?
Best Regards,
Shuyu Kameda
------------------------------
Shuyu Kameda
??????
ZEAL CORPORATION
Japan
------------------------------
-------------------------------------------0 -
Hi Shuyu,
sorry I didn't receive any notifications about this post.
First, do you generate the hash values in an external DB?
-> Yes. We always prefer a data warehouse in between. I don't see an easy option doing this in Board.
And as a side benefit, any other system can easily connect to your SQL database for integrations.
Second, I thought I could do the same thing by using a copy of the year entity instead of a hash value, is there any advantage to using a hash value?
-> I am not sure what you are thinking about here. Can you elaborate your idea?
Third, if you create a root entity with multiple entities combined, does the structure look like this?
-> No, the combined root entity would be directly connected to each entity as my hash value would be something like SHA1(Product + BU + Shop).
Kind regards,
Florian
------------------------------
Florian Deutsch
Berater
linkFISH Consulting GmbH
Germany
------------------------------
-------------------------------------------0 -
Hi @Florian Deutsch and @Shuyu Kameda
I have seen your post and noticed that Florian has not received a notification when Shuyu replied. To avoid this for future posts, I have two recommendations for you:
1) Update your E-Mail preferences in your profile - you can ask for daily or weekly updates and choose the forums / communities you are interested in
2) you can tag people you are refering to - in this case they should be notified directly and this accelerates the process as well :-)
I hope this helps - keep posting :-)
Kind regards
Sandra - Community Admin
------------------------------
Sandra Bartl
Communications & Customer Marketing Manager
Board Community
Germany
------------------------------
-------------------------------------------0