What's New

Current Release
: FactoryTalk DataMosaix 1.6.0

New Features

This release includes the following new features:
  • A new beta version of the Asset Framework (PI-AF) Connector is added.
  • Extended support to Power BI as BI tools using the new egress data interface.
  • Extended support for Sequences, Events, Relationships, and Datasets entities in BI tools.
  • The FactoryTalk Optix connector extended support to Alarms and Events and Store and Forward features.
  • A new location filter capability group is added.

Fixes and Improvements

This release includes the following improvement:
  • In the FactoryTalk Optix connector, we addressed anomalies and concerns regarding network and data loss with the store and forward feature.
For more information, refer to the online help.

Known Anomalies

  • In FactoryTalk Optix, in some rare cases, the file size for the store and forward feature may exceed the maximum limit.
  • The Power BI Connector converts boolean values of true, false, 0, or 1 to TRUE only.
  • The "!=" operator does not work with timeseries datapoints.
  • Tableau continuously loads without displaying any error messages when a user tries to execute negative queries containing mathematical expressions.
  • Order by clause is not working when any query is executed from Tableau as a custom query because Tableau wraps that custom query. However, the same query works when there is no wrapping on the query from other clients like PSQL CLI. Tableau's built-in function helps to sort the data for different columns can be used as a solution to this problem.
  • Arithmetic expression exceptions are not handled and must be considered while preparing the SQL queries.
  • The user with only a Data Scientist/Application Developer role is unable to access the list of Extractors.
  • The scope assignment to a capability is currently limited to
    Datasets
    and
    All
    .

Limitations

  • In this release, we officially support Tableau (Desktop and Server) and Power BI as BI tools using the new egress data interface. Integration with other BI tools will be added in the future DataMosaix releases.
  • In mathematical queries, division by zero will result in an error.
  • The following functions are not supported in datameshing:
    • Aggregate functions ARRAY_AGG, JSONB_AGG, and JSON_AGG.
    • The cumulative distribution function CUME_DIST().
    • The string function Reverse.
    • The string function SPLIT_PART().
    • The window function PERCENT_RANK().
  • SQL Queries and functions:
    • Only select statements are supported.
    • It provides limited capability for SQL aggregations and functions.
    • Join operations between the exposed DataMosaix entities are supported.
    • Sample queries are available in the online help, refer to Sample Queries.
  • The available FactoryTalk DataMosaix entities:
    • This release currently supports 7 DataMosaix entities, and they are exposed as if they were Postgres SQL tables for BI tools to query from. Refer to the Supported Tables and Schemas.
    • The
      timeseries_datapoints
      table will only return the rows if a valid external ID or timeseries ID is provided in the where clause.  Otherwise, the SELECT query returns an empty row. In case of joining with the "timeseries" table, it will fetch the rows if where clause on external ID or timeseries ID is present for
      timeseries_datapoints
      table.
    • Time series data point aggregation functions are currently not supported.
    • While there are no hard limits on the number of rows that can be fetched from assets and timeseries tables, performance in scenarios with large datasets may result in unexpected errors or timeouts. For the
      timeseries_datapoints
      table it is mandatory to provide timeseries ID or external ID in the where clause. By default, the data points for the last 24 hours will be returned but the user can also use the timestamputc column to fetch any relevant time range data points.
    • Table constraints are not defined for the exposed FactoryTalk DataMosaix entities. However, the relationships can be easily defined by a Tableau user using the reference table defined in line with FactoryTalk DataMosaix entities APIs. For example, the asset ID is the unique (can be assumed as primary key) ID so there will be no duplicate asset ID in the table. Refer to the following Primary key and Foreign key columns table:
      Primary and Foreign Key Columns Table
      Table Name
      Primary Key Column
      Foreign Key Column
      assets
      id
      timeseries
      id
      assetid (Table: assets)
      timeseries_datapoints
      timeseriesid, timestamputc
      timeseriesid (Table: timeseries)
      sequences
      id
      relationships
      externalid
      events
      id
      datasets
      id
  • By default, the following SQL functions are supported:
    • COUNT()
    • NOW()
    • ISNULL()
    • EXTRACT()
    • MAX()
    • MIN()
    • AVG()
    • RANK()
    • CUBE()
    • CONCAT()
    • SUM()
    • UPPER()
    • LOWER()
  • If the group count goes beyond 350 (irrespective of tenant, project, or organization), the token size will exceed the limit of 8 KB, leading to the token failure.
  • Only users/M2M with the roles of Application Developer, Project Admin, Data Configuration, Data Scientist, or Application User can access the list of Applications and Extractors.
  • Special characters are not allowed when creating models in FactoryTalk DataMosaix using FactoryTalk Optix.
  • Depending on the scale of the changes made to the Optix model, sometimes the changes may not be correctly pushed to the Flexible Data Model (FDM). If this happens, it is recommended to either change the FDMSpaceName property of the FTDataMosaixStore object or increase its FDMModelVersion value.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal