What's New

Current Release

: FactoryTalk DataMosaix 1.5.1

Fixes and Improvements

A single file for Frontend and Backend third-party packages.
Security Enhancements.

Known Anomalies

There can be ambiguous column names as the result of a join query and these columns are suffixed with the numbers starting with zero. This prevents the ambiguous column name error. The projection with two columns having the same name will not work in the custom query in Tableau because Tableau wraps all custom queries. The same query works with other clients like PSQL CLI. To overcome this limitation, users can use aliases when referencing tables in the projection of select query to get the desired column names.
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.
In some cases, users may not see their existing charts.
The user with only 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) as a BI tool using the new egress data interface. Integration with other BI tools will be added in the future DataMosaix releases.
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 Configuring Tableau to connect to a DataMosaix Project.
NOW() and CURRENT_TIMESTAMP() are the supported timestamp functions. The Interval keyword is supported with NOW() and CURRENT_TIMESTAMP(), but week interval is not supported. None of the Interval keywords is supported with the current_timestamp() function if it is used in where clause of
timeseries_datapoints
table. However, NOW() function can be used in where clause of
timeseries_datapoints
table with or without interval keywords. For sample timestamp queries, refer to Configuring Tableau to connect to a DataMosaix Project.
The available FactoryTalk DataMosaix entities:
This initial release currently supports 3 DataMosaix entities, and they are exposed as if they were Postgres SQL tables for BI tools to query from. Refer to the Configuring Tableau to connect to a DataMosaix Project.

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, timeseriesutc	timeseriesid (Table: timeseries)
By default, the following SQL functions are supported:
COUNT()
NOW()
ISNULL()
EXTRACT()
MAX()
MIN()
AVG()
RANK()
CUBE()
CONCAT()
SUM()
The user is unable to assign a role with more than 60 characters to the application while editing the application in non-prod.
Getting 403 error when using a special character in OrderDirection or OrderBy while fetching GetListOfRegisteredApplication and GetListOfRegisteredExtractor API.
The user is unable to create and edit extractor with special characters in non-prod.
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.
The number of groups per project should not exceed 500. Creating groups beyond this limit results in failure.
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.

Previous Releases