Known anomalies from FactoryTalk Edge Gateway version 1.03.00

Parallel deployment of two MSSQL applications results in incomplete data for the second application (1419407)

After creating two MSSQL applications, which in the configuration process use 2 different models, but consisting of the same set of tags (in the described case, 4 simple INT/REAL tags are included in each of the models), and then deploy the data (both applications do it in parallel) in the case of the second application, the data set that is stored in the table is incomplete - always in the first data frame (and only in it) there are missing entries in the TYPE column (mediaType/mimeType).

Thingworx models and nodes suffixes usage causes deploy error (1640770)

User cannot use the same model in two or more applications of ThingWorx. There is an issue with suffixes generated by Thingworx application to keep Thingworx names unique.

LLong is presented in MQTT payload as string (1514367)

Enabling and disabling flag for ‘Enable flat payload”, gets the LLong in string sting format.

Low Data Flow performance when deploying a large number of tags (1547719)

Tag values do not update in the Data Flow section when a large number of tags are deployed. (more than 800 in one ap) and the performance of FTEG degrades when Data Flow is enabled. For example: Stopping the application takes 2-5 minutes when Data Flow is enabled.

Sometimes populating data source is not successful using FTLD driver, when there is a big array in the controller (1542325)

On controller, if we have a project with about 3200 different tags. Additionally, we add there single tag being a multidimensional DINT array [20,100,100]After creating data source using FTLD driver and pointing to shortcut of this controller and try to populate. Population takes some time (about 15 minutes). After both processes (fteg-ct.exe and ftld-adapter.exe) become idle, we assume that population is done. However, the status is still “Loading”. Leaving it running for longer time doesn’t change it. After restarting FTEG Configuration Tool the status is presented as “Not populated”.