Consolidated node to child node
Posted: Thu Apr 20, 2017 8:28 am
Hello
In one of the dimensions I have, I had a consolidation with 2 simple nodes. I have deleted those 2 simple nodes and turned the consolidated node into a simple node. All my export and import data TI's worked well, the dimension and the security cubes showed the change, the subset that was used for the Webapp also reflected the change. With everything being fine, I uploaded the new security file onto Web App via Manage Rights and it was all ok.
I tried to open the node within Web App to test it, but it didnt let me, it still appears to think it is a consolidated node. Now I looked into performance Modeler to see if I could see the change and that looked fine in PM too. I was advised to go to manage right, re-apply and save rights to see if it would make a difference but it didnt.
As an alternative, I had to re-create a new node to get round the issue. But Im still curious to why that would have happened for future reference.
Has anyone come across this issue or could anyone shed some light to what could have gone wrong or what I could try to do if the issue reappears?
Thank you for your time
Mithun
{Admin note: Please post to the CORRECT forum. This does NOT belong in Enhancements.}
In one of the dimensions I have, I had a consolidation with 2 simple nodes. I have deleted those 2 simple nodes and turned the consolidated node into a simple node. All my export and import data TI's worked well, the dimension and the security cubes showed the change, the subset that was used for the Webapp also reflected the change. With everything being fine, I uploaded the new security file onto Web App via Manage Rights and it was all ok.
I tried to open the node within Web App to test it, but it didnt let me, it still appears to think it is a consolidated node. Now I looked into performance Modeler to see if I could see the change and that looked fine in PM too. I was advised to go to manage right, re-apply and save rights to see if it would make a difference but it didnt.
As an alternative, I had to re-create a new node to get round the issue. But Im still curious to why that would have happened for future reference.
Has anyone come across this issue or could anyone shed some light to what could have gone wrong or what I could try to do if the issue reappears?
Thank you for your time
Mithun
{Admin note: Please post to the CORRECT forum. This does NOT belong in Enhancements.}