Although rare in Oracle field names, when spaces did crop up they were more than irritating, because they prevented the whole table from being read or written with the Oracle Adapter. As of this version field/column names containing spaces are processed normally by the Oracle Adapter. This feature is automatically applied, no configuration change is needed to enable it.
Although the XML Adapter is still in beta, it can already be used to process some XML files. The XML processing is presently limited to relatively “flat” not overly complex XML structures with few child nodes. To illustrate the current possibilities we have assembled some simple XML import/export examples, and further will follow. General example of processing XML files
Min and Max Heaters, each of which determine the lowest or highest value for a record or row, is extended with two powerful new features.With this version the
The first of these is an option to determine the lowest or highest value for the entire process of a run, as an alternative to the existing ability to find the lowest or highest of each grouped data set. This makes it possible to add the lowest or highest value in header and footer rows of CSV text files, for example.
The second feature now makes the Min and Max Heaters also capable of delivering the highest or lowest of the FlowHeater data types Date, Time and DateTime. In so doing the Heaters automatically detect the incoming data type and process them appropriately.
Parameter feature that makes it possible to store the last used value of a Parameter automatically and restore this for use in the next run. This enables the definition of simple filter conditions or the construction of dynamic SQL WHERE clauses that only select new records.How can we setup import/export Definitions that when run will automatically process only newly added records/rows? This is something that has often been asked, yet only with a relatively complicated workaround was it possible. In this version of FlowHeater a powerful function now extends the
This version of FlowHeater introduces a significantly improved detection of DataBase NULL (DBNULL) values for Insert/Update. Previously when table fields for which no NULL/DBNULL values are assigned were empty the test run would complete without a problem, but the live import/update would break with an error report when it encountered the corresponding field in the database that had no default value defined. As of this version, FlowHeater will check during the test run whether a field may be assigned a DataBase NULL (DBNULL) value and if not issue a relevant warning.