InetSoft offers Web-based BI software that includes flexible data mashup capabilities that can be your data integration solution without the need for a data warehouse. Below are articles about InetSoft's software:
Query Condition Expressions - The query condition expression grammar is based on the SQL conditions. Most of the expressions have a construction identical to their SQL counterparts. Like SQL, all reserved words are case-insensitive. However, all names, including variables and child nodes, are case-sensitive. We will cover the complete list of conditional expressions and give a few examples of advanced usage. In SQL’s conditions, the column values can be used in expressions for calculation or comparison. Similarly, the Data Modeler condition expressions can reference values on the data tree. However, since the hierarchical data model used by the Data Modeler supports much richer organization of data, the expressions support a few more types of data references. The selection node and all of its child nodes can be referenced by the conditional expression. The value of the selection node can be referenced using the reserved word, ‘this’...
Query Parameter Handling - Report queries may require parameters. Parameters are defined in queries to retrieve user input at runtime. In addition to the parameters defined in the queries, data sources used by queries may also require parameters to establish connections to the source. For example, an RDBMS data source may require a user ID and password to login to a database. Query parameters are handled in the same way as replet parameters. A list of all variables used in queries in a template is returned as...
Query Performance Considerations - For performance reasons, you should avoid using too many large queries in one report. In addition, you should only run a query from script in cases where you cannot directly bind the query. In general, it is more efficient to use the 'Data Binding' dialog box to bind the query to an element, which allows the query to automatically run as part of report generation. There are two complimentary methods for controlling and improving the performance of a report. • Size limit: You can limit the number of rows that the query returns. • Time limit: You can limit the amount of time a query may execute. For example, if you only use the first few rows of a query, you should set a tight limit on the query size. You can make these settings at the query level or data binding level. See Advanced Toolbar Buttons in the Data Modeler to limit at query level, and Precautions and Safeguards in the Report Designer to limit at binding level...
Query Traps - A Query Trap refers to a construct in a data model that can generate undesired query results. This can confuse end users or even give incorrect results. Loops refer to the multiple possible paths from entity A to B in a data model. Loops can exist in different forms: a self join or multiple join path. The Data Modeler in InetSoft's business intelligence software automatically highlights these loops in red. An employee table containing a “manager id” column that points to itself to indicate an employee’s manager is a self join loop. This self join must be resolved to allow end users to find employees and their respective managers. Self join loops are most easily resolved by creating a table alias. The multiple table loop has the potential to create results that are too restrictive. An order table (A) joins to the “ship to” table (B) and the “bill to” table (C), which in turn joins to a “company” table (D). If end users select data from all four tables, only orders that have the same company for “bill to” and “ship to” will be returned. Multi-table loops can be addressed using aliasing or auto-aliasing. Additionally, these loops can be addressed using a weak join which will not be included in the join path of the resultant query...
Copyright © 2024, InetSoft Technology Corp.
