What's New

Current Release
: FactoryTalk DataMosaix SaaS 1.07.00

New Features

This release includes the following new features:
  • Microsoft®
    Excel®
    and
    Microsoft
    SQL Server Reporting Services (SSRS) are supported tools with the virtual PostgreSQL data interface.
  • Labels and Files are now exposed as tables in the virtual PostgreSQL data interface.
  • More granular permissions management in the
    FactoryTalk® DataMosaix
    SaaS Management Console with the introduction of additional capabilities (Raw, Location Filters). Default roles have also been changed to include the new capabilities.

Fixes and Improvements

This release includes the following improvement:
  • The
    FactoryTalk® Optix
    connector has been enhanced with the following features:
    • Support for
      FactoryTalk Optix
      string and Boolean data types in
      FactoryTalk DataMosaix SaaS
      time series.
    • Streamlined mapping of
      FactoryTalk Optix
      Alarms and Events attributes to
      FactoryTalk DataMosaix SaaS
      Events attributes.
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 'Order By' clause does not work when a custom query is executed from tools like Tableau,
    Excel
    , SSRS, or Power BI because these tools wrap the queries in ways that disregard sorting. To work around this problem, refrain from employing 'Order By' statements in manual queries and instead use the built-in functions provided by the tools to achieve sorting.
  • Arithmetic expression exceptions are not handled and must be considered while preparing the SQL queries.

Limitations

  • In this release, we support Tableau (Desktop and Server), Power BI,
    Microsoft
    Excel
    , and
    Microsoft
    SQL Server Reporting Services as BI tools using the new egress data interface.
  • The Power BI connector converts boolean values of true, false, 0, or 1 to TRUE only.
  • In mathematical queries, division by zero will result in an error.
  • The following functions are not supported in the virtual PostgreSQL data interface:
    • 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
      FactoryTalk DataMosaix SaaS
      entities are supported.
    • Sample queries are available in the online help, refer to Sample Queries.
  • The available
    FactoryTalk DataMosaix SaaS
    entities:
    • This release currently supports nine
      FactoryTalk DataMosaix SaaS
      entities, and they are exposed as if they were Postgres SQL tables for BI tools to query from. Refer to the Supported Entities in the Virtual PostgreSQL Data Interface.
    • 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 SaaS
      entities. However, the relationships can be easily defined by a Tableau user using the reference table defined in line with
      FactoryTalk DataMosaix SaaS
      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
      datasetid
      (datasets)
      timeseries
      id
      assetid
      (assets),
      datasetid
      (datasets)
      timeseries_datapoints
      timeseriesid
      ,
      timestamputc
      timeseriesid
      (timeseries)
      sequences
      id
      assetid
      (assets),
      datasetid
      (datasets)
      relationships
      id
      datasetid
      (datasets)
      events
      id
      datasetid
      (datasets)
      datasets
      id
      labels
      id
      datasetid
      (datasets)
      files
      id
      datasetid
      (datasets)
  • 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.
  • Time out issue while executing join query with datasets and events.
  • 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 SaaS
    using
    FactoryTalk Optix
    .
  • Depending on the scale of the changes made to the
    FactoryTalk 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