TDM 8.0 has just been released and it includes many exciting features:
Fabric 7.1 has just been released and it includes the following:
We have just released Fabric 7.0.1, which includes the following:
Code improvement and minor bug fixes in Broadway, Graphit, Common, iidFinder and integration with AWS keyspaces.
Enhancements to PubSub: the publisher and subscriber UserCode methods can now receive a Kafka interface name, a PubSub interface name or a PubSub section name. In addition, offset was added to the in-memory broker.
Batch performance improvement comparing to V7.0.
Elasticsearch driver has been upgraded to V8.5.3.
Deep-dive into Fabric’s Triggers, Events, CDC and Elasticsearch integration functionality.
An interactive session how to build, configure, and expose RESTful data services in minutes – using Graphit, our drag-n-drop, low-code/no-code, visual web-service designer.
The 4th K2View Development Meetup took place on February 23rd - addressing Fabric's Roadmap, BI solution and Web Framework.
Broadway UI has undergone a major facelift, introducing a new up-to-date coloring scheme.
In addition, several new exciting features and actors have been added, such as:
The purpose of a Sync On Demand mode is to reduce the time spent by Fabric performing the LUI sync by synchronizing only the relevant data.
In this mode, the sync is performed only on tables that are a part of the executed SELECT statement and their parent tables.
Fabric Web Services have two properties related to user role permissions:
Does the product have any built-in input filter functions for detecting potential SQL injection from user Web Service inputs?
Our recommendation is to use prepared statements and only use parameters as arguments to pre-built prepared statements.
How can I create a flow with 2 nested GET with SELECT statements per each?
When a GET & SELECT from LU1 is followed by loop on GET & SELECT from LU2, the exception is thrown:[SQLITE_ERROR] SQL error or missing database (database LU2 is locked)The exception is thrown when trying to RELEASE an instance of LU2 and it happens due to open results set of the SELECT on LU1. The exception is thrown only when running with Debug Mode = OFF.
This problem can be resolved by modifying the flow as follows:
Why is there a note in the help section of the Release Statement stating the following:
Important: When there is a use case of multiple Get in a loop on the same Fabric session, it is recommended to use the Release command (without LU name) after each iteration.
It is recommended to use the Release command without the LU name,only in case you need to release the LUIs of all LUs in the session. In case you need to release an LUI of a specific LU, you need to set the LU name in the release command.
When trying to save the Environments file from Studio, we sometimes get an error stating "Encryption error in environment
Why do we get this error? What is the logical reason behind this error message?
We assume that in such cases you use "Fabric URL" option at the environment definitions and you switched from one to another, or you just start using "Fabric URL". In such cases re-key is required. Click to read about Fabric security interfaces.
In the past, we had a strong dependency on a specific Fabric version - e.g. Fabric version 5.3 for TDM version 5.1. Is it still the case with TDM7?TDM7 release notes mention fabric 6.4.1, but now 6.4.2 is available. We are wondering whether it is OK to go ahead with the latest Fabric versions TDM projects.
You can run TDM 7.0.1 on either Fabric 6.4.1 or Fabric 6.4.2. TDM 7.1 is based on Fabric 6.5.