Skip to content

11-1-0 GA scheduled 01/31/2024

New Or Improved Features

  1. If the search index is a Solr index, you can order your query results not only by Name, Relevance and "Updated Date" but also by other property types:

    • System attributes. Note: Only the system attributes that are stored in the search index can be used as the order by fields. Besides multi-valued system attributes such as "Data Classifications" or object-valued system attributes such as "Column Statistics" cannot be used as an order by field

    • Custom attributes. Note: Custom attributes of the Enumeration (Multi-value), Users, Rich Text, Blob or Multiline Text type cannot be used as an order by field. Order by a custom attribute of the User data type returns the results sorted by the user ids not by the usernames.

    • Profile attributes

    • Data Profiling attributes except the multi-valued attribute "Data Profiling"."Inferred Data Types"

    • Source History attributes except the multi-valued attribute "Source History"."Last Access Users"

    • UDPs

You can have more than one order by field in the Order By clause. Each field can be a property type in the above list with its own asc(ending) or desc(ending) order. For example, "Last Name" asc, "First Name" desc. This sorts everything by "Last Name" in the ascending order first and then by "First Name" in the descending order whenever the "Last Name" property for two or more objects are identical.

  1. New system attributes are added: Model, "Source System Definition", "Data Select Method", "Data Select Query", "Replication Quality", "Imported Date", "Import Bridge", Source, Destination, "Data Quality Latest Status", "Data Quality Latest Score", "Data Quality Latest Date", "Mentioned Objects", "Mentioned Users", "Source Model" and "Destination Model" etc.

  2. The system attribute "Business Name" is now a custom attribute of an imported object (e.g. Table)

  3. The system attribute "Content Name" is renamed to "Model Name", and "Content Description" to "Model Definition". The system attribute "External URL" is renamed to "Open In Tool". The system attribute "Description" is renamed to "System Description". "Description" replaces the custom attribute "Long Description" as HTML formatted text of unlimited length that can include images, tables, etc.

  4. The filter type CONTENT is converted to a system attribute Model.

  5. Support of binary complex relationships in the SELECT list and WHERE clause.

  6. Support of faceting on certain system attributes, data profiling attributes, profile attributes, and custom attributes if the search index is a Solr index.

  7. Support of subquery =WHERE() or !=WHERE() filters on the system attribute Model, "Mentioned Objects" or custom relationship.

  8. Support of count('Relationship') in the SELECT list and WHERE clause.

  9. Added "Data Profiling".Null, "Data Profiling".Blank and "Data Profiling".Zero.

  10. Added Source History attributes

Deprecated Features

Deprecated features do not require any action before upgrading to MM 11.1.0. If any of these features are used in worksheets, dashboards, conditional labels and collections created in the previous release, they will be automatically upgraded. In order to use any of these features in MQL queries in the REST API functions, you need to set the mqlVersion parameter to 1 or 2 so that they can be automatically upgraded. If you use any deprecated feature in the filters entered manually, you may get a warning about the field cannot be resolved to a valid attribute, in which case, you will need to replace the deprecated feature with the new feature by yourself.

Deprecation of features Replacements More information
"Business Description" system attribute Custom attribute Definition Naming standardization. Removal is considered for the next major release
Children system attribute Use the Parent system attribute if the query is at that level. It was experimental and never available in the MIMM Explorer
Custom attribute "Long Description" Custom attribute Description Naming standardization. Removal is considered for the next major release
"Content Name" system attribute "Model Name" system attribute Naming standardization. Removal is considered for the next major release
"Content Description" system attribute "Model Definition" system attribute Naming standardization. Removal is considered for the next major release
Term system attribute Custom relationship "Is Defined By" MQL normalization. Removal is considered for the next major release.
"Term Documentation" system attribute Custom relationship "Is Defined By" MQL normalization. Removal is considered for the next major release.
CONTENT filter type Model system attribute Naming standardization. Removal is considered for the next major release
Scope filter in the FROM clause Model=WHERE(…) in the WHERE clause MQL normalization. Removal is considered for the next major release
"Data Profiling".Empty "Data Profiling".Null, "Data Profiling".Blank or "Data Profiling".Zero No automatic upgrade is provided. Customer needs to replace "Data Profiling".Empty with one of the new data profiling attributes before it is removed from the next release.

Removed Features

The following table lists the MQL features removed with MM 11.1.0 and the recommended MQL features to replace them. Please ensure your applications do not use any of these features before upgrading to MM 11.1.0.

Removal of features Replacements More information
"Business Name Inferred" system attribute The new Documentation system attributes Rebranding
"Business Name Inferred Origin" system attribute The new Documentation system attributes Rebranding
"Business Description Inferred" system attribute The new Documentation system attributes Rebranding
"Business Description Inferred Origin" system attribute The new Documentation system attributes Rebranding
"Hide Data" Sensitivity Labels’ hide data property Rebranding
"Data Classifications" as a related object type Export Data Classes It was experimental and never available in the MIMM Explorer.
"Data Classifications Approved" as a related object type Export Data Classes It was experimental and never available in the MIMM Explorer.
"Data Classifications Matched" as a related object type Export Data Classes It was experimental and never available in the MIMM Explorer.
"Data Classifications Rejected" as a related object type Export Data Classes It was experimental and never available in the MIMM Explorer.

11-0-0 (GA 01/31/2022 - Deprecated 12/31/2024 - EOL 12/31/2025)

New Or Improved Features

  1. Profile relationships, custom relationships, and related object relationships can be used in the SELECT list. Custom relationships can be used in the WHERE clause as well as the SELECT list.

  2. Scope Filters in the FROM clause can be used to reduce the scope of a MQL query.

  3. New system attributes are added: "Conditional Labels", "Created By", "Created Date", "Data Profiling", "Data Sampling", "Data Classifications", "Data Classifications Proposed", "Data Classifications Matched", "Data Classifications Approved", "Data Classifications Rejected", Editors, "Has Data Impact", "Has Data Lineage", "Has Semantic Definition", "Documentation", "Mapped Documentation", "Inferred Documentation", "Last Change Event", "Object Image", "Owner", "Sensitivity Label", "Sensitivity Label Approved", "Sensitivity Label Lineage Proposed", "Sensitivity Labels Data Proposed", "Sensitivity Labels Rejected", "Updated By", Viewers, Watchers, "Workflow Assignees", "Workflow State", "Workflow Deprecation Requested" and "Workflow Published".

    Note that the original profile attribute Documentation of glossary terms has been renamed to "Long Description" to not conflict with the new "Documentation" attribute described above. The Documentation system attribute applies to imported objects. For more information refer to the Documentation system attribute.

Term's workflow "Status" and "State" attributes have been changed into the different and more generic system attributes "Workflow State", "Workflow Published", and "Workflow Deprecation Requested" that now apply to any object of a user model under workflow.

  1. System attribute "My Workflow Tasks" is supported on all custom model objects which have workflow enabled.

  2. Object-valued system attributes can be used in the WHERE clause with the EXISTS or NOT EXISTS operator.

  3. Attribute notation marks #..#, [...], {...}, and <...> are no longer necessary. You can use the attribute name as is.

  4. A new ExpandedMembersOfRole function can be used to filter users and groups of the object roles.

  5. A new MembersOfRole function can be used to select users and groups of the object roles.

  6. Data Profiling Attributes can be used in the SELECT or WHERE clause.

  7. Inequality operator, <, <=, >, >= and BETWEEN, are supported on attributes with numeric data types, such as Integer, Long and Double.

  8. Inequality operator, != and != ANY(...), are supported on the category filter and the system attributes "Model Id", "Object Type", "Object Type Id", "Object System Type", "Object Id", "Object Profile", and "Object Stable Id".

  9. Order by "Updated Date" in descending order, i.e. the newest objects are at the top of the results.

  10. The behavior of Multi-valued Attribute Filter in Where is better defined.

  11. The system attributes "Certified By", "Endorsed By", "Commented By" and "Warned By" are now an array of Grantee objects instead of an array of strings that represents user names. The Grantee object provides more information than just the user name and is consistent with other system attributes which value represents an array of users or groups.

Deprecated Features

Deprecated features do not require any action before upgrading to MM 11.0.0. If any of these features are used in worksheets, dashboards, conditional labels and collections created in the previous release, they will be automatically upgraded. In order to use any of these features in MQL queries in the REST API functions, you need to set the mqlVersion parameter to 1 so that they can be automatically upgraded.

Deprecation of features Replacements More information
Attribute notation marks Improve the usability. Removal is considered for the next major release
"Semantic Types" system attribute "Data Classifications" system attribute Rebranding. Removal is considered for the next major release
"Business Name Inferred" system attribute The new Documentation system attributes Rebranding. Removal is considered for the next major release
"Business Name Inferred Origin" system attribute The new Documentation system attributes Rebranding. Removal is considered for the next major release
"Business Description Inferred" system attribute The new Documentation system attributes Rebranding. Removal is considered for the next major release
"Business Description Inferred Origin" system attribute The new Documentation system attributes Rebranding. Removal is considered for the next major release
Used system attribute "Has Semantic Usage" system attribute Rebranding. Removal is considered for the next major release
Endorsements system attribute "Endorsed By" system attribute Rebranding. Removal is considered for the next major release
Comments system attribute "Commented By" system attribute Rebranding. Removal is considered for the next major release
Certifications system attribute "Certified By" system attribute Rebranding. Removal is considered for the next major release
Warnings system attribute "Warned By" system attribute Rebranding. Removal is considered for the next major release
"Workflow Actions" system attribute "My Workflow Tasks" system attribute Rebranding. Removal is considered for the next major release
"Last Modified Date" system attribute "Updated Date" system attribute Rebranding. Removal is considered for the next major release
Stewards system attribute in SELECT list MembersOfRole function Steward is replaced by object roles
Stewards system attribute in WHERE ExpandedMembersOfRole function Steward is replaced by object roles
steward filter ExpandedMembersOfRole function filter Steward is replaced by object roles
object_type filter "Object Type" filter Deprecated with MM 10.1.0 to reduce the number of reserved words
last_modified filter "Updated Date" filter Deprecated with MM 10.1.0 to reduce the number of reserved words
label filter Labels filter Deprecated with MM 10.1.0 to reduce the number of reserved words
semantic_type filter "Data Classifications" filter Deprecated with MM 10.1.0 to reduce the number of reserved words
endorsed_by filter "Endorsed By" filter Deprecated with MM 10.1.0 to reduce the number of reserved words
certified_by filter "Certified By" filter Deprecated with MM 10.1.0 to reduce the number of reserved words
commented_by filter "Commented By" filter Deprecated with MM 10.1.0 to reduce the number of reserved words
warned_by filter "Warned By" filter Deprecated with MM 10.1.0 to reduce the number of reserved words

The Stewards system attribute used to be a related object type and related object property. For example, you could use #Stewards#.[Email] or #Term#.#Stewards# in the SELECT or WHERE clause. This feature is no longer available. You cannot use MembersOfRole('Steward') or ExpandedMembersOfRole('Steward') as a related object type or related object property. MembersOfRole('Steward').[Email] or Term.ExpandedMembersOfRole('Steward') etc. is not a valid syntax.

MQL Version in REST API functions

The current MQL version is 3. MQL version 3 matches the MQL syntax and system attributes of MM 11.1.0. MQL version 2 matches the MQL syntax and system attributes of MM 11.0.0. MQL version 1 matches the MQL syntax and system attributes of MM 10.1.0.

A new mqlVersion parameter is added to the REST API functions that take MQL query fragments. A new mqlVersion field is added to the QueryInput schema which is the schema of the input body of the POST /entities/executeMQLQuery function. You can set the mqlVersion parameter or field if you have deprecated syntax and/or MQL system attributes in your query. A new function POST /entities/upgradeMQLQuery is added in MM 11.1.0 to allow you to enter a QueryInput that uses deprecated syntax and/or MQL system attributes and output an upgraded QueryInput.