In the chapters, subchapters and sections in the index on your left you can find the information relevant to using the I-Refactory. On your right you can find links to the subsections and paragraphs of each section.
OAuth2 identity tokens can now be obtained from Azure Active Directory.
For a Generic Data Access Interface new table valued functions(TVF) are generated. These functions are created in a schema with postfix: '_oasi_bk_pit'.
The TVF requires a single argument: acm_start_dt as datetime2(7) which will be used to only retrieve records valid as of the given point in time. The result set not only contains the columns for the given table but also returns the businesskey columns (if relevant) for the related parent tables.
The query returns the i-refactory metadata for table
entity as of timestamp
The TVF function also includes the businesskey columns for related parent entities. In this example: interface_code, namespace_code, classification_code.
SELECT TOP 1
FROM acm_datadef_oasi_bk_pit.entity(CAST('2023-09-20 12:00:00' AS DATETIME2(7)))
The returned result:
You now have the ability to create a
Export Delivery. Such a delivery will export the data for each entity in a Generic Data Access model to a Parquet file.
The following features are supported:
The export has built in capabilities to limit memory resource consumption by exporting data in batches (data for a table is fetched from the database in batches of records).
|Fixed a problem where querying the history view returned rows with overlapping transaction time
|Fixed a problem where metadata could not be imported due to temporal references in logistical data
|Fixed a problem with a name collision error when registering violated records. In this particular case a logical entity column (delivery_id) collided with the i-refactory metadata delivery_id
|Auxiliary key in Generic Data Access Model
|Attributes for independent auxiliary relations were added to the auxiliary key when a dependent auxiliary reference was added afterwards. This issue is now fixed.
|Name to code conversion
|The name to code conversion was applied for key columns in a dependent anchor which were not a reference to another anchor. This results in unwanted overrules of the code convention of a column.
|Export to a temporary directory did not work as expected regarding the timestamp added and used in scripts.