Prevent GLTOT Cube Reload from clearing out Dimension Default Elements

andy

I've noticed that when a GLTOT cube reload (as opposed to an incremental refresh) is run in FSM, any dimension Default Elements that have been added in dEPM Admin > Edit Databases > Dimension Properties  > Advanced Properties are cleared out. Does anyone know if there's a way to prevent the dimension properties from being overwritten by the FSM cube reload action?

Jose Salinas

Hey Andy,

I've run into similar issue trying to implement cube rules and cell notes. I'm assuming that you are running into the same issue with the dimension properties since similar to what I tried to do. Our overnight cube reloads clear all notes and rules. From what I've been told by Infor support, data being cleared on reload is normal cube operation. In case it helps, see below for more details on closed incident regarding my issues. If you hear or find otherwise, please let me know! If not, you may have to try to find a workaround or other path.

Issue: FSM cubes rebuild during the night on PRD/TST environment and the “cube rule” and cell note mods the customer adds to the d/EPM OLAP cube are lost.

Resolution:
Landmark does not support cube rules so there is no way to define additional cube rules in the LPL and have the rule be populated in the d/EPM OLAP cube. The FSM LPL declares what business classes are cubes and what fields in those business classes are dimensions and measures. The Reload action does the rest of the work of taking the LPL declarations a creating an d/EPM OLAP cube. The Reload action does delete dimensions and recreates them. This is why the “cube rule” mods the customer adds to the d/EPM OLAP cube are lost.

Best regards,

Jose