While trying to figure out a probable solution for this, I found that when I referred to fields in the Hierarchy() with a suffix of: <TableName>-NodeList, the Qualify seemed to work.
Is this an alternative or would it fail in most other scenarios?
Hierarchy([MyTable-NodeList.ID], [MyTable-NodeList.ParentID], [MyTable-NodeList.Name])
LOAD ID, ParentID, Name
[ ID, ParentID, Name
1, 0, USA
2, 0, UK
3, 1, CA
4, 3, SF
5, 2, LN
6, 3, LA
7, 4, OAK
The resulting columns get qualified as <TableName>.<TableName>-NodeList.FieldName
any inputs on the same would be most appreciated.
I am not surprised that this works, but I am not sure that I want to support this solution...
The question to me is, why do you want to rename the fields? Or rather, why not do it properly? You can read what my view is on How to Rename Fields.
Wei & Ola,
I know this is an older post, but I just came across this issue today and was able to create a work around. In my scenario I am loading data from a flat file. This file contains a meta data export from Essbase. Since I am loading a number of dimensions with the same file/field layout, I used a variable to prefix the field names during the hierarchy import. This got me around the qualifier issue. Below is an example, hopefully this helps.
Just keep in mind, the code below is only being used for demo/POC purposes. I am not sure that this would be the best scenario for a production app.