Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 396 views

    Best Practices in Cognos Report Studio

    Uploaded by

    dhanz_99
    The document discusses best practices for developing reports in Cognos Report Studio. It recommends: 1) Consistency in formatting, using report expressions, and filters with '=' instead of 'in'; 2) Using built-in calculations, proper solve order, and brackets in expressions; 3) Removing unnecessary objects and using data items instead of calculated members/measures; 4) Defining tool tips and a single chart palette. Following these practices improves performance, readability, and maintainability of reports.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Best Practices in Cognos Report Studio

    Uploaded by

    dhanz_99
    396 views4 pages
    The document discusses best practices for developing reports in Cognos Report Studio. It recommends: 1) Consistency in formatting, using report expressions, and filters with '=' instead of 'in'; 2) Using built-in calculations, proper solve order, and brackets in expressions; 3) Removing unnecessary objects and using data items instead of calculated members/measures; 4) Defining tool tips and a single chart palette. Following these practices improves performance, readability, and maintainability of reports.

    Original Description:

    Best Practices in Cognos Report Studio

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses best practices for developing reports in Cognos Report Studio. It recommends: 1) Consistency in formatting, using report expressions, and filters with '=' instead of 'in'; 2) Using built-in calculations, proper solve order, and brackets in expressions; 3) Removing unnecessary objects and using data items instead of calculated members/measures; 4) Defining tool tips and a single chart palette. Following these practices improves performance, readability, and maintainability of reports.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    396 views4 pages

    Best Practices in Cognos Report Studio

    Uploaded by

    dhanz_99
    The document discusses best practices for developing reports in Cognos Report Studio. It recommends: 1) Consistency in formatting, using report expressions, and filters with '=' instead of 'in'; 2) Using built-in calculations, proper solve order, and brackets in expressions; 3) Removing unnecessary objects and using data items instead of calculated members/measures; 4) Defining tool tips and a single chart palette. Following these practices improves performance, readability, and maintainability of reports.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 4

    1

    Running the Report in Different Format


    And Customize the Report Size




    Author: Muhammad Shakir
    Cognos Specialist
    mshakir@segmentbi.com
    www.segmentbi.com




    SEG BI Consulting Services, Inc.
    Transforming data into information




    2

    INDEX

    Introduction 3
    Best Practices-cognos report studio . 3












    3
    Introduction:
    In this paper, we will discuss we will discuss some best practices that you should following while
    working in cognos report studio.
    Best Practices-cognos report studio:
    Following are the points that the developer should use while developing reports in cognos
    report studio.
    1. Formatting:
    Consistency
    There should be consistency for the formatting options (Font, Margin,
    Border, etc.) throughout the report. This will improve readability.
    Report Expressions
    Add Report expressions above the crosstab for the selection made in the
    prompts. This will help the user know the selections made in the report; It
    would also help in the scenario, where there is no data for the selections.
    2. Filter and Prompts:
    Ensure that there should be filters for every dimension required. Due to this
    rows fetched from the database will be less.
    Use = instead of in for single value comparison in filters. Due to this query
    run time will reduce.
    Use CASE statement instead of IFELSE, for implementing conditional
    filter. This will improve performance of the filter execution.
    Delete filters which are not required instead of disabling them. This is
    required as unused Code hampers the performance of the report.
    3. Calculation:
    Use in-built calculations instead of calculating manually.
    Assign proper solve order for the calculated data items.
    Use explicit brackets for expression definitions. The calculations may give
    wrong answer if the Brackets are not used in the expressions or calculations
    of data items.
    4. Query Items:
    Remove all unnecessary objects from the report. This improves execution
    because when the report is executed, the data is fetched for all the data
    items in the report.
    Use data items instead of Calculated members and Calculated
    measures. The calculations of members should be done in data items. It
    helps to reduce the run time of calculations.


    4
    Special Characters should be avoided in the Query names.
    For the query items which are not involved in any type of calculations, set
    the Aggregate Function and Roll up Aggregate to NONE.
    5. Charts:
    Show Tool Tip for the report items displayed on the chart.
    Define single Palette for all the charts in the report. This helps to maintain
    consistency for all the charts used.
    6. General:
    Use brackets in IFELSE, CASE. and other expression.
    Minimum use of Java Script. Usage of Java script might affect the
    performance of the report.
    Use Render variable instead of Style variable to show or hide any report
    items. Style variable executes the item on the report page and then hides it
    but the render variable does not execute the item which is not to be
    displayed in the report page.
    Use Boolean variables instead of String variables unless string variables are
    unavoidable. Boolean variables get executed faster as compared to String
    variables.

    You might also like