Details level
Based on SQL queries, Details level records can be filled. Consequently, these queries can results in more records with more fields. You can define more BOs to process as details level. These BOs have your own associated keys in the Aggregation properties BO, based on their corresponding BO name.
Key | Value example / Info | Extension | ||
|---|---|---|---|---|
Detail.BO.Name | Detail.BO.Name=UsrDataAggregationDetail1; usrDataAggregationDetail2 Info • System name of BO.
| ReportSX | ||
<BO name>.Data.BO.Association | UsrDataAggregationDetail.Data.BO.Association= DataAggregationDetail|DataAggregationDataRef Info • Mandatory for each system BO that is specified by the previous parameter • Association between Details BO and Data BO. • This can be obtained from Field Definer (Technical information tab, under Associations). | ReportSX | ||
<BO name>. ProcessDetailRecordsForNonUpdatableDataRecords | UsrDataAggregationDetail.ProcessDetailRecordsForNonUpdatableDataRecords=n Info • Possible values: y,n • If value is y: also for the Data level records that are not in a status for update, the Details records will be deleted and inserted again. • If value is n: for the Data level records that are not in a status for update, the Details records will not be deleted nor updated or inserted. | ReportSX | ||
<BO name>.SQL.Statement.<serial number> | UsrDataAggregationDetail.SQL.Statement.1= select CODE as PropertyCode, NAAM as PropertyName, M2BVO as GrossArea from OBJALG where SYSCODE = &PropertyRef& or UsrDataAggregationDetail.SQL.Statement.1= { select CODE as PropertyCode, NAAM as PropertyName, M2BVO as GrossArea from OBJALG where SYSCODE = &PropertyRef& } Info • SQL select query to create specific details BO and fill its fields. • You can specify more than one SQL statement for one details BO. Each identified by its own unique serial number. Example UsrDataAggregationDetail.SQL.Statement.1= SELECT ... UsrDataAggregationDetail.SQL.Statement.2= SELECT ... Records from both queries will be added, field assignment are shared, see next key. • SQL string can be given as one line without carriage returns or can be divided over more lines. In the last method, the query must start with { character and end with } | ReportSX | ||
<BO name>.SQL.Field.<sqlfield name>.<type>=<BO field name> | UsrDataAggregationDetail.SQL.Field.PropertyCode.STRING=FreeString1 UsrDataAggregationDetail is BO system name of details BO, PropertyCode is SQL select field, FreeString1 is system name of BO field that has to be filled. UsrDataAggregationDetail.SQL.Field.PropertyName.STRING=FreeString2 UsrDataAggregationDetail.SQL.Field.GrossArea.DECIMAL=FreeDecimal3 Info • Fields of details level to fill, based on the SQL. • The fields can be of all the supported types. The types of the selected fields must match with the Planon ProCenter BO fields that are linked to it. • The SQL must select the configured fields, you can define as many fields as you need. • The defined SQL parameters can be used in the same way as for the Data level. | ReportSX |
