One of the challenges working with grids is validating the results. As with an Essbase calculation, Smart View reports are developed to validate results. The same happens when calculations, or data movement, is executed in Groovy via grids. When the results in Smart View aren’t accurate, where do you go? Read more
If you have used Smart Pushes, you have undoubtedly run into security issues. The PBCS development team is working on a way to bypass this, but there is no release date. If you haven’t run into this, you probably have and didn’t know it. Here is the issue. Read more
Gridbuilders are the link to moving data from BSO to ASO, and ASO to ASO. Gridbuilders can also be used to save calculated results that are executed directly in Groovy. If it jumped into your head, yes, you can completely bypass the Essbase calculation engine. I have a coworker that has done exactly that – everything in Groovy and had all the forms connected directly to ASO! There is an example of this in my presentation at KScope, Last Minute ODTUG Planning Sourvenirs. Before we get too far ahead, back to the basics. Read more
Because so many methods in PBCS require parameters that are maps and lists, it is very important to your productivity and effectiveness to understand, use, and be able to manipulate collections. Collections include lists, maps, and ranges. These are based on Java collection types and include a ton of useful methods. This article will cover lists and maps. Read more
One of the more surprisingly useful things that can be done in a Groovy calculation is querying metadata. This was discussed in Part 11: Accessing Metadata Properties, but I recently had a situation where users could load data at parent levels and have it allocated down to the bottom of the hierarchies. Read more