Dear visitor, welcome to Palo Community Forum.
If this is your first visit here, please read the Help. It explains in detail how this page works.
To use all features of this page, you should consider registering.
Please use the registration form, to register here or read more information about the registration process.
If you are already registered, please login here.
Parent element attribute loss
Hi all.
If you create element (B)(child) subordinate element (A)(parent), which was originally element A (basic element without childs), loss attribution of element A. It is somehow possible to maintain the element of attribution?
This post has been edited 1 times, last edit by "vesi" (May 21st 2010, 1:03pm)
I can not reproduce this in version 3.1 Build 4161
Do you have a bug report number?
Not yet, I wanted to ask first on the forum if anyone has the same problem.
I have also Palo build 3.1 Build 4161
The problem have in latest ETL Server, when I use TreePC function.
f.e.
Original structure
lvl1/lvl2/attribute
A/ /elem name A
A/B/elem name B
A/C/elem name C
A/D/elem name D
ETL - TreePC - view
parent/child/weight/type/attribute
B/B1/1/N/elem name B1
B/B2/1/N/elem name B2
B/B2/1/N/elem name B3
C/C1/1/N/elem name C1
C/C2/1/N/elem name C2
after update original structure with ETL
lvl1/lvl2/lvl3/attribute
A/ / /elem name A
A/B/ /{after update attribute is empty}
A/B/B1/elem name B1
A/B/B2/elem name B2
A/B/B3/elem name B3
A/C/ /{after update attribute is empty}
A/B/C1/elem name C1
A/B/C2/elem name C1
A/D/ /elem name D
This post has been edited 2 times, last edit by "vesi" (May 21st 2010, 4:22pm)
Hello!
I handled this problem by exporting all attributes to a file and re-imported them into the attributes cube after the dimension update.
Hi,
the problem appears, when you import your dimension using the mode "update" on consolidations in your load. This will delete all C-elements in your dimension an recreate them. Therefor all values on these elements (there can only be string values on C-elements) are lost.
Regards.
The problem is that in the example the TreePC contains element B with an empty attribute value. The Dimension-Load overwrites on element B an existing attribute value with this value.
For a furthcoming release we've planned to avoid this by setting in Dimension Load under Attribute mode "add", so that the old attribute value remains. Mode "insert" will work as now.
I don't see any better workaround as the one proposed.
