Hyperion Kernel, From Alpha To Omega

Substitution Variable (SV) is a powerful tool, used developers in calculation scripts, business rule, load rules, partition, formulas and report scripts.It seems like a pretty simple task, right? But in this case, SV used in report scripts - working in some cases, not in others, caused me many hours of headache and eventually figured it out an end. I started by adding SV this way (which is not uncommon, right?)   Report Scripts in some databases run successfully, which is what I expected. However, in some databases of one same application, report script just don't work.Here is an example, validation is fine, but wont produce any data (if I change to hard code variables, it will produce data)   Go to the log file, try to find out what is wrong - It complains about the variable is Unknown! Why? Check the administration guide, I am clearly using the correct syntax! After hours and hours of trying different ways and combination, I finally figured out the way. Here is

In PBCS, you no longer have access to Hyperion servers, this is different from the your on-premise environment. Automated backup with job scheduler and archived them for days or weeks in case when a restoration or roll back is needed becomes un available. This post s a clear challenge to Hyperion administrators . However, there is a good news. PBCS comes with a backup routine called Daily Maintenance. This will allow you to setup a time and automatically run backup, called snapshot. Well, the bad news is that you have to download them to you local computer/server then save them for archive purpose. See the following steps for setup. Setting Up S ervice M aintenance Time -  1) From Navigator, Tool, Daily Maintenance 2)  Select Start Time, then click Apply. Th e daily backup will go to Artif act S napshot under S napshot 3 )  You can check the st atus from the M igration S tatus R eport. It will show green Completed status when it ran successfully . You can then downlo