Normally this will only appear if the value is performanceLimited, in which case the correspondng "tips" resource should give any relevant details. If this element is absent, "ok" is assumed. Each functionSubType (function, operator, summary and literal) can have a context defined. The application can specify the context for which function metadata is to be retrieved. If no context information is defined, then it is valid to all contexts. Each functionSubType (function, operator, summary and literal) can have a queryMode defined. The queryMode can be specified to indicate which functions are supported by the query mode of the application. If no queryMode information is defined, then it is valid to all queryModes. Besides using explicit enum values, the values @1, @2 and @3 are also allowed. This latter case is used for return type specification, which then is equivalent to the datatype of the first or second argument respectively. Defines a group that contains one or more groups and/or function definitions. Properties of this group are inherited by child groups and functions, although each may be overridden by attribute on the child elements. Identifier for the group. Groups with the same identifier in the same position of the tree are merged. When specified, then this object will not be shown in the Expression Editor UI. Defining a context here, restricts the visibility of this group when the application specifies a particular context. Restricts the visibility of this group when the application is running in a particular queryMode. Identifier for the vendor, this restricts the visibility of this group when the application specifies a particular vendor. This property defines a function as possibly supported by other interface ids, not documented in FDS. Besides using explicit enum values, the values @1, @2 and @3 are also allowed. This latter case is used for return type specification, which then is equivalent to the datatype of the first or second argument respectively. When specified, then this object will not be shown in the Expression Editor UI. This is used internally by QECL and RQP to represent the dimensional functions. This property indicates that the function requires the members to be in a predictable and defined order regardless of any related fact data. (MRF). This is the name that shows up as the function name and that will get dropped into the text when selected. This should not be translated. Identifier for the vendor, this restricts the visibility of this function when the application specifies a particular vendor. This property defines a function as possibly supported by other interface ids, not documented in FDS. This property indicates that the function requires the members to be in a predictable and defined order regardless of any related fact data. (MRF). The name of the shared library. File extension is usually omitted so that platform-specific extension may be appended; however, if a file extension is provided, appending platform-specific extension will be inhibited. Literals and keywords can be defined here. Examples are (, ), FOR, IN etc. There is no need to define a canonical name for these, since these are hard-coded in the parser(s). Their id and name should be exactly the same. These can not have arguments. When specified, then this object will not be shown in the Expression Editor UI. This is the name that shows up in the Expression Editor tree controls. It can be overridden by an entry in the language sensitive file. This is the text that will be dropped by the Expression Editor. Identifier for the vendor, this restricts the visibility of this literal when the application specifies a particular vendor. This property defines a function as possibly supported by other interface ids, not documented in FDS. A name. Context depends upon whee this type is used. Operators can be defined here. There is no need to define a canonical name for these, since these are hard-coded in the parser(s). Their id and name should be exactly the same. There is also no need to document their arguments. When specified, then this object will not be shown in the Expression Editor UI. This is the name that shows up in the Expression Editor tree controls. It can be overridden by an entry in the language sensitive file. This is the text that will be dropped by the Expression Editor. Identifier for the vendor, this restricts the visibility of this operator when the application specifies a particular vendor. This property defines a function as possibly supported by other interface ids, not documented in FDS. Operations/Features are defined here for the purpose of making the quality of service value available. ors can be defined here. There is no need to define a name or canonical name for these, since these are operations are accessed by client software using the id only.hard-coded in the parser(s). When specified, then this object will not be shown in the Expression Editor UI. This is an English description of the operation/feature. Identifier for the vendor, this restricts the visibility of this operation when the application specifies a particular vendor. maps a formatspec identifier used by the _format function to a format specification The id should reflect the format conform to format specification Summary functions can be defined here. These are almost like regular functions, but are usually shown in different panels in the Expression Editor UI. The summary functions can not be defined in a dll. When specified, then this object will not be shown in the Expression Editor UI. This is the name that shows up as the function name and that will get dropped into the text when selected. This should not be translated. Identifier for the vendor, this restricts the visibility of this summary function when the application specifies a particular vendor. This property defines a function as possibly supported by other interface ids, not documented in FDS. Each group and functionSubType (function, operator, summary and literal) can have a vendorID defined. It is normal that the application specifies one or more vendorIDs, also known as FunctionSetIDs. The application would base the specification of the vendorIDs on the content of the model. If no vendorID information is defined, then it is valid for all vendorIDs. This information behaves much the same way as the context information. FDS will use the vendorID as an index into the language specific strings. Cognos starts all provided values with the 2 character sequence V_. Each group and functionSubType (function, operator, summary and literal) can have a datasourceQueryType defined. It is normal that this is specified at the group level. It identifies the underlying datasource access technology. E.g. relational, multi-dimensional. In CRN/FM context, this information is read from the centrally managed datasource definitions in the model and passed on to the accessor for FDS. Groups and functions will be filtered based on the function matching the fields that were provided to FDS. Implied inheritance takes place, because a group is only returned if it matches, thus making all child groups and functions potentially visible. (This works the same way as with context and vendorId). This filter is used in 2 contexts. The first one is in defining quality of service levels and the second is in defining the underlying technology (Oracle, Informix) that supports functionality. In the case of relational datasources, the interface id will indicate that a certain database supports the functionality even though UDA processes it locally. The value is stored in the model in dataSource.type.interface. This is the descrition of the enumeration values. NOTE: these interface id's are listed as a union of 3 seperate simpleTypes, each a set of enums. These 3 simpleTypes are identified as "relational", "multidimensional" and "special". Relational interface id's are enumerated under the "relational" simpleType Multidimensional interface id's are enumerated under the "multidimensional" simpleType All other id's of special nature (such as "all_rel" and "all_olap") are enumerated under the "special" simpleType Relational: all_rel: all the relational datasource interface IDs in this list CS: Composite CT: CTLib CT15: CT-15 D2: IBM DB2 JD-D2: IBM DB2 via JDBC (DQM only) IF: Informix OL: SQL Server via OLEDB OR: Oracle JD-OR: Oracle via JDBC (DQM only) EC: SAP BW for Planning R3: SAP R/3 - ECC for Adaptive Warehouse XML: XML OD: generic ODBC 3.5 gateway IQ: Sybase IQ via ODBC 3.5 RB: Redbrick via ODBC 3.5 SS: SQL Server via ODBC 3.5 JD-SS: SQL Server via JDBC (DQM only) TD: Teradata via ODBC 3.5 JD-TD: Teradata via JDBC (DQM only) PG: Progress via ODBC 3.5 OD25: generic ODBC 2.5 gateway (not officially supported in Bering) D225: DB2 via ODBC 2.5 (not officially supported in Bering) IQ25: Sybase IQ via ODBC 2.5 (not officially supported in Bering) SS25: SQL Server via ODBC 2.5 (not officially supported in Bering) RB25: Redbrick via ODBC 2.5 (not officially supported in Bering) TD25: Teradata via ODBC 2.5 (not officially supported in Bering) VM: IBM Cognos Virtual View Manager datasource (replaces Composite datasource from Bluesea release, WO2838) NZ: Netezza JD-NZ: Netezza via JDBC (DQM only) ERP-SFDC: Salesforce.com (DQM only) ERP-SIEBEL Siebel (DQM only) ERP-SAP SAPR3 (DQM only) JDBC all generic JDBC (DQM only) ** The following databases can be connected via ODBC: CT, CT15, D2, OR, IF, IQ, RB, SS, TD, PG. Multidimensional: all_olap: all the multidimensional datasources interface IDs in this list BW: SAP BW CL: Finance CR: Contributor DO: DB2 OLAP EB: Hyperion Essbase (supported through the DO gateway so all EB entries should match DO entries) ** The EB datatype is being phased out in 8.1MR2 so that all new connections use DO; however EB is kept for backward compatibility with existing pre-MR2 reports IS: IBM DB2 InfoSphere Cubing Services WO2803 MO: MS Analysis Services (no longer supported) XO: Cubics (documented entries should match MO settings) PC: Power cubes YK: MS Analysis Services 2005 (documented entries should match MO settings, no longer supported) M8: MS Analysis Services 2008 (only supported in XQE) M12: MS Analysis Services 2012 (only supported in XQE) M14: MS Analysis Services 2014 (only supported in XQE) M16: MS Analysis Services 2016 (only supported in XQE) M17: MS Analysis Services 2017 (only supported in XQE) M19: MS Analysis Services 2019 (only supported in XQE) MAZ: Azure Analysis Services via OLEDB (only supported in XQE) X5: MS Analysis Services 2005 via XMLA (only supported in XQE) X8: MS Analysis Services 2008 via XMLA (only supported in XQE) LA: Lava (Cognos Now - Celequest) WO2568 TM: TM1ODP (Applix TM1 data source) WO2689 TMR: TM1 REST API Provider (only supported in XQE) XI: IBM DB2 Cubing Services via an XMLA Provider WO2828 RO: Cognos ROLAP