MicroStrategy ONE
Collecting Data during Page Execution
After events in the request have been processed and custom logic that affects data collection has been applied, the bean (that is, the report or document, for example) is ready to be executed and the data can be fetched from MicroStrategy Intelligence Server.
Click on any box in the diagram to see a detailed explanation of that step in page execution. Click here to return to the Overview of Page Execution.
Problem solving at this step in page execution
There is no user customization at this step in page execution. Errors can occur, but they are based on actions performed in other steps in page execution. For example, if you specify the wrong report ID, collectData will fail. The application makes its call based on the information that it is asked to retrieve.
When an error occurs in a WebBean, no exception is thrown. Instead, the WebBean is set to an Error state, and the error information is stored as a WebError in the bean. Execution continues. The transform that renders the bean, and not the application, is responsible for checking the state of the WebBean and displaying the error. The transform will also be responsible for logging the error and writing the error's stack trace and debug information (depending on the debug flags that are set) to the HTML output as a comment. You can use all of this information to help resolve problems that you encounter when you perform customizations. The error message is displayed on the screen, the logging information can be viewed in the log file, and the stack trace and debugging information can be viewed in the HTML source for the page. See Error Handling for a more detailed discussion of error handling in MicroStrategy Web products, and see Logging Architecture for more information about error logging.
Next step in page execution
The next step in page execution depends on whether any custom logic needs to be applied after the data is collected.
-
If custom logic needs to be applied after the data is collected, the next step is applying custom logic.
-
If custom logic does not need to be applied after the data is collected, the next step is selecting the template to be used for the page.
See also
-
Report Execution and Data Retrieval (for details about data collection)
-
Saving State for Later Restoration (for details on persisting beans)