2023.3.6

Extraction

Splitting the Extract File by Posting Date Attribute

We implemented a change that facilitates the possibility of splitting data into separate extract files according to the Posting Date attribute. This functionality will assist you with your daily reconciliation. For each extracted file a dedicated manifest file and an extract log will be created (they will have the Posting Date attribute in their names). The functionality can be enabled by clicking the Split per Posting Date check box on GUI while configuring an extract configuration.

For more details, refer to Splitting Data into Separate Extract Files by Posting Date.

Disabling the Scheduler while Creating an Extract Configuration

We developed a possibility to disable the scheduler while defining your extract configuration. This means that to extract data using the configuration for which the scheduler is turned off, you will have to run it manually by clicking the Run now button.

For more details, refer to Extracts Configuration.

Journal Mapping Traceability

We implemented a new feature for the View History section of the Journal Mapping screen. You can now trace the changes for a particular item as the screen will maintain the state across versions. E.g. when you view a mapping for a particular field in a historical version, if you switch to a different version the mapping links for that field will still be open and you will be able to see if there were any changes.

Bulk Upload - Mandatory Ingestion ID Attribute

We implemented a change for the Configuration Data JSON file. Previously, the Ingestion ID attribute was mandatory only when configuring the Journal Line Definition on the screen.

Now, the attribute will also be mandatory when creating a configuration using the Configuration Data JSON file.

IF you already had the Ingestion ID Systemic Field defined, this change does not affect you.

IF you didn’t have the Ingestion ID Systemic Field in your Journal Line Definition the upgrade will not have adverse effect on you configuration. However, if you choose to change the configuration using the Configuration Data JSON, apart from any other changes you will have to add Ingestion ID before you reupload it, otherwise the file will be rejected.

1
{
2
 "label": "Ingestion Id",
3
 "name": "ingestionId",
4
 "type": "text",
5
 "role": "ingestionId"
6
}

For more details on the structure of the Configuration Data JSON file, refer to Configuration Data.

IF you want to upload a Configuration Data JSON file without the Ingestion ID, Journal Line ID and Journal ID attributes to a clean instance of Fynapse, the attributes will be added automatically. This is an enhancement of the support for Configuration Data JSON files created prior to adding the Journal Line ID and Journal ID attributes and will be deprecated in the near future.

Preview

Support for Multiple Currencies - Simple Exchange Rate Conversion for Functional Currency

We are implementing a POC of simple FX rate conversion. If support for multiple currencies is enabled and no Functional Amount is provided, Fynapse will perform currency conversion by applying one of the hardcoded exchange rates to the Transaction Currency. This is part of an ongoing implementation of FX rate conversion. The next stage of the implementation will allow you to define the exchange rates.