Creating a textual information object

Use the Actuate SQL text editor if either of the following conditions is true:

The graphical information object editor does not generate the desired Actuate SQL query, so you must edit the query. For example, if the query includes OR or UNION, you must use the Actuate SQL text editor to edit the query.

You want to type or paste an Actuate SQL query instead of creating it graphically.

If you save a query in the Actuate SQL text editor, you cannot modify the query in the graphical information object editor.

To display the Actuate SQL text editor, complete one of the following tasks:

In the graphical information object editor, choose SQL editor, as shown in Figure 3-51.

Figure 3-51

Choosing SQL editor to edit an Actuate SQL query

In SQL Preview, choose Edit SQL.

On New Information Object, select Edit in SQL text editor, as shown in Figure 3-52.

Figure 3-52

Choosing to provide the Actuate SQL query in the SQL text editor

You edit the query in the upper pane of the Actuate SQL text editor, as shown in Figure 3-53. The lower pane displays output columns or parameters.

When you edit a query in the SQL text editor, do not use table and column aliases that are identical except for case. For example, do not use both status and STATUS as column aliases.

Figure 3-53

Editing the SQL query in the Actuate SQL text editor

The following rules also apply:

Do not include an ORDER BY clause in the query.

Paths that do not begin with a forward slash (/) are relative to the IOB file, as shown in the following example:

../Data Sources/MyDatabase/dbo.customers.sma

Absolute paths must begin with a forward slash. Using absolute paths is not recommended.

Figure 3-53 shows the Actuate SQL text editor.

Copyright Actuate Corporation 2012