Actuate Tips & Tricks

1. Header Label Not Visible properly in the management console Noted By : Krishna Prasad If the header is truncated or looks unaligned in the management console which looks good in the local environment, then do check the Multiline property of the TextControl (TextPlacement property.).Set this to true & in most of the cases, this works out to solve the problem. 2. LinkExp not working properly Noted By : Pradeep G If the LinkExp in the report does not work as expected, then check the spaces in the URL, i.e the LINKEXP property. There should not be any space befor or after the = or any where in the whole string which is going to be the actual URL, (There can be spaces in the appending strings , but the final URL must not have any spaces.It is clear with the following example.) for Ex Ex1.rox?pLegalEntity= &pLegalEntityId& & pUserName=&pUserName (ERROR) Ex1.rox?pLegalEntity= & pLegalEntityId & &pUserName=&pUserName (PERFECT) 3. Graph not showing the proper intervals in y axis & formatting the y axis labels. Noted By : Deepa A S If you want the y-axis to display the intervals in a specified way & also want to format it, then set the following properties. YLabelFormat = #,##0 YLabelStyle = ChartIntervalYLabels YTickIntervals = <Interval> ex: 1000 We cannot format the label if it is Auto generated, i.e if YLabelStyle = ChartAutoYLabels 4. Library not getting included Noted By : Deepa A S Actuate might not show some error message when it is not able to include some libraries into the report. The first thing you are to check is for some duplicates. If there are some objects or variables or parameters in the report that conflicts with the library object, then rename those objects & then try to include it again. 5. Statement Handling Err Noted By : Deepa A S & Staline

While executing the report, if you get a database error that which says that Statement Handling error, then check for the stored proc or the query. There must have been a change in the input or the output parameter which has not been synchronized with the report.You have to get the stotred proc in sync & recompile the report. The other possibility is that , there must be a assignment in a select clause which is throwing a no record found exception which is not catched. i.e For Ex. Select date_value into v_BusDate from D_DATE were Date_id = 5676. Where v_BusDate is a local variable to the proc. If there is no record with that filter criteria, it will throw an error.We need to handle this using the exception handle as follows.
BEGIN SELECT LEGALENTITY_ID INTO V_INTLEGALENTITYID FROM D_ACCOUNT WHERE ACCOUNT_ID IN (SELECT ACCOUNT FROM TMP_GBL_ACCOUNTS) AND ROWNUM = 1; EXCEPTION WHEN NO_DATA_FOUND THEN NULL; END;

6. Oracle how to use a comma separated string in the in clause directly Noted By : Staline When there are more than one value to be passed to the query for filtering , we use the in clause. If this value comes as a string we cannot use it directly as it will be considered as one string & not as comma separated many strings.We usually try to parse this & put it in temp tables & then use them in the in clause. There is a short cut method for these, though this might not be efficient always. We can append the incoming string with commas on both the side, so now each string is surrounded by comma on both the side & use the instr function to search in that string the value from the table which should also be appended by comma on both the sides. For Ex:
SELECT A.ACCOUNT_ID,B.ACCOUNT_ID,C.ACCOUNT_ID FROM D_ACCOUNT A,D_ACCOUNT B,D_ACCOUNT C WHERE INSTR((','||ParameterPassed||','), (','||A.ACCOUNT_ID||',')) > 0 AND B.SOURCE_ID = A.GLOBAL1CPTYID AND C.SOURCE_ID = A.ONLOAN_COUNTERPARTY_CODE;