What's wrong with SV in report scripts?

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 to share with everyone.

Step1) Remove the double quotes in variables (make sure there is no space between)
Step2) Add double quote to the Report Script


Now it runs beautifully! Other places using SV all work fine (ex. calculation scripts, load rules, etc), Why using of SV in reports scripts in some databases work this way and some in the other ways in a same application is still a mystery, yet need to be explained, but at least I have a work around.

In EPBCS, there is no EAS, therefore no report scripts or data export is available. You still can setup substitution variables through Variables / Substitution Variables. To export a slice of data, you would need go to Application / Overview / Action / Export Data.

Comments

Post a Comment

Popular posts from this blog

ESSBASE: When to Use FIX vs. IF

Hyperion developers love FIX and IF, both are powerful tools and interchangeable in usage in certain circumncetances. There are also differences between the two. Let's take a look. FIX...ENFIX Usages and Rules Every FIX must be ended with ENDFIX. But it is optional to end the statement by ";" FIX Mbr can be any comma-delimited list of members, or member set functions FIX Mbr argument can be a combination of members from multiple dimensions           FIX(@CHILDREN(Qtr1),"Actual")                 Calc Dim(Accounts);           ENDFIX FIX Mbr list from the same dimension means "OR", cross dimensions means "AND" FIX cannot be used inside of formulas in outline, they can ONLY be used in calc scripts Cannot consolidate a dimension that is FIXed on. Following will generate an error when run          FIX(@CHILDREN(Qtr1),"Actual")                 Calc Dim(Accounts, Scenario);         ENDFIX It c
Read more

Essbase Currently Not Accepting Connections

Image
Application is currently not accepting connection. Essbase Error(1054009) There are occasions when users receive the above error message when they try to connect to Planning Essbase cluster via SmartView. This is normally caused by one of the following activities:   a) Database is being refreshed (Classic) or deployed (EPMA). Solutions: Wait till refresh to be completed. b) Allow connects under security is unchecked.  Solutions: In EAS, from application, select edit property, and under General tab. c) Connection is disabled using MaxL . Solutions:   Code examples: alter application $4 disable connects; alter application $4 enable connects ;   d) Connection is disabled using ESSCMD. Solutions: Code examples: DISABLELOGIN; ENABLELOGIN; When all of these are checked, and users are still not able to connect to the application, then the ultimate solution is to restart all Hyperion services.
Read more

HFM: Performance Tuning on Application

Image
There are three Planning Applications (seven Plan Types) are already there in Production, all perform well. After HFM was migrated from SIT to the Production environment recently, we immediately noticed the performance of HFM is not well. Normally it takes 15 seconds to open a HFM application in SIT, in production it takes over a minute to open (if after the services are recycled, it takes more than four minutes to open a HFM application). However, the consolidation time is sort of normal. (two to five minutes to consolidate a month, which contains about 400K of records). Following is the list of tuning activities, with regards to HFM tuning - 1) From DB side      a) Ask DBA to confirm that Auto Create Statistics is enabled for the HFM schema.      b) Have DBA check how frequently the SQL Server is doing automatic statistics maintenance.      c) Ask the DBA if the indexes may need to be defraged. DBA reported back -      a) Auto Create Statistics are enabled for all the
Read more