Show TOC

Function documentationLogic Debugger Locate this document in the navigation structure

 

The Logic Debugger allows you to test and run your logic files and to debug logic before you run it against live data. This applies to both default logic and other logic files; default logic files are in the default.xls workbook for each application and other logic is in workbooks with user-defined names.

  • You can run logic against live data while using the debugger by using the Simulation option on the General tab.

The debugger has four tabs that define how you want to run your logic files.

  • General

    This tab determines if you want to simulate expected results where changes do not affect the database (Run in simulation mode (do not post results)), or if you want to send differences to the database (Run logic and post results). The results of the logic execution can be viewed in the log files that have been generated by clicking the Show log button. You can calculate the difference using logic or a posting engine. You can view and modify the log file setup by clicking the Browse button. Actually executing the script needs to be audited, but auditing is not required for simulation.

  • Region

    This tab allows you to set up the member set to run the logic against. You can choose all members or allow the logic system to base the region on the members used in a data file. If you choose members, you can leave a dimension blank to select all members, but you must choose at least one member of one dimension.

  • Dynamic Formula

    This tab allows you to enter a logic formula that is combined, at the beginning, with the logic file you are testing. This is helpful if you want to set up certain conditions, but do not want to save those conditions in the logic file after testing.

  • Optimize option

    This tab allows you to set advanced logic optimization options. You can set the memory management and the MDX Query type. There are three types of MDX queries that can be generated by the logic engine:

    • Mulit-axis - Builds the MDX query based on the number of dimensions in the member set that have more than one member. An axis is assigned to each dimension that has more than one member in the member set. The subcube for the query therefore can have many axes depending on the member set or region of data against which the query is run.

    • 2-axis, crossjoin - Queries that are "flattened" so that they have no more than 2 axes by nesting multiple dimensions in the rows of the query. For the cross-join type, the query first checks that a value exists in each cell in the application (MSAS) database. If data exists in any of the cells referenced by the query, those cells are included in the query, otherwise they are ignored.

    • 2-axis, nonemptycrossjoin - Queries that are "flattened" so that they have no more than 2 axes by nesting multiple dimensions in the rows of the query. For the nonemptycrossjoin type, the query checks that a value exists both in the fact table (SQL) and application (MSAS). If data exists in both the fact table AND the application database, those cells are included in the query, otherwise they are ignored.

To use the logic debugger

  1. Open the Admin Console and go to the Script Logic menu and select the logic file. You can then see the Logic Debugger menu on the action pane.

    Note Note

    If you run the Logic Debugger without a logic file open, you are asked to open a logic file first.

    End of the note.

  2. Select each tab and choose the options you want. On the Dynamic formula tab, you can choose to use the Logic Assistant to paste logic functions in the Dynamic Formula area.

  3. Select the Run Logic button.

  4. When finished, select the Exit button.