The Groovy API provides a privileged function to update metadata properties using business rules. Since it’s a privileged function, only administrators are allowed to execute the same. Of late, I have been using the function to rename the members, change the parents, etc. This helps in many ways, as UDAs get a little better since…
This sounds more like controlling a specific product or entity read only from the planning unit hierarchy. This post is for those who don’t use planning unit hierarchy but use a webform to control whether planners are supposed to edit a certain product or entity during the planning cycle. Below is how groovy can help…
I am sure most of us are familiar with the conventional data export from Essbase using the DATAEXPORT option. However, we cannot perform a precondition to export only the required data. But this doesn’t allow us to perform a conditional check to see whether we are exporting valid data or not. In short, we cannot…
Although input at higher level intersections in ASO is not possible, the combination of groovy and EPM APIs helps us to achieve the same. Let us make use of instant aggregation in ASO along with groovy grids. Here is the link to the article I published on LinkedIn.- Click Here for full post.
For the existing grid spread functionality to work, a webform needs to meet certain conditions, such as the entire hierarchy of YearTotal (IDescendants) must be available on the form; otherwise, the natural spread doesn’t work. The ability to input at the YearTotal and hide the Q1..Q4, H1..H2 members from the form are general requests. The article was…