There have been some cases where the expression had been altered by the pretty print operation prior to 11.1.4. You can have the expression editor attempt to automatically format your expression. If not, the calculations in the expression will execute first and the results will be then aggregated. If it is set on, then the calculations in the expression will be executed after the values of the query items are aggregated. You do this using the calculate after aggregation control. You can control the timing of aggregation. In the illustration below, auto-completion is suggesting the query item Discontinued Date and some functions and operators. The suggestions will be from the functions list and of query items which exist in the module. You can use the arrow keys to navigate up and down the list of suggestions and press enter to choose an item. You can press escape to not accept any of the suggestions. The expression editor will attempt to suggest auto-completion of what you are typing. You can increase the font size of the expression. You can view the expression with a high contrast view without setting your computer to use its high contrast accessibility functionality. More information about the validation errors will be displayed than was displayed in the previous Modelling expression editor. Like the old expression editor, you can validate the expression. The collapsed elements of an expression will not remain collapsed in the next session of the expression. In the illustration below, our expression has been collapsed. You can move elements of expressions out of the way by collapsing them. You can add comments to the expressions, which will aid you or other people in understanding your expressions when they are reviewed.Īs you can see in the illustrations, you can add two types of comments using the // and /* */ operators. If you had much experience with the Framework Manager expression editor, you will appreciate how helpful this will be. The function’s syntax help will be available to you to refer to until you no longer need it. This helps when you are building up your expression. The function help text will stay visible as you work in the expression until either another function is selected in the function tree or in the expression itself or if the preview or validate buttons are pressed. The formatting of your expression is preserved in the module and you can layout the expression in a manner that you find suitable. Since the expression handles for nulls in the source values, the current date has been substituted and then processed into the key. One of the values shown in RECORD_END_DATE is null. The preview results are those of the entire expression. The second column has the values of the source column, RECORD_END_DATE. The first is the result of the expression. In the illustration below, you will see two columns. The expression has no pretentions to elegance it exists to illustrate the functionality of sub-expression preview. You could have something like 29991231 instead, if it is your preference. It handles for null values by substituting the current date. The expression casts RECORD_END_DATE to a character data type, extracts substrings from it and concatenates them into the key. The intention was to use it as a key in a relationship. Here is a fairly simple expression which takes the RECORD_END_DATE column from the Cognos sample data base table EMP_EMPLOYEE_DIM, which is a timestamp data type column with null values, and then converts it to a numeric value. You can isolate the parts of an expression, view their results, and identify where problems originate. Previewing sub-expressions is useful for troubleshooting expressions. You can select a sub-expression in your expression and preview the results.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |