2023.4.3

Bulk Operations - Migration from Old to New File Format

In Fynapse 2023.4.3 we are simplifying the JSON file format. We will be supporting the old format for a short period of time. A feature flag that allows you to switch between the supported file version has been implemented on the Configuration Data screen. By switching this feature flag you will be able to choose to either upload or download the JSON file in the new or old format. By default, the toggle is set to the old format.

The enhanced Configuration Data Bulk Upload functionality has more extensive validations to ensure integrity of the system structure:

• Upon upload the file will be validated against the prescribed structure and a list of errors will appear on the screen if the configuration is incorrect.
• If you make changes in the screen, which cause the configuration to break and then try to download this configuration, Fynapse will inform you in that you’re trying to download a broken configuration. The list of errors will be added at the end of the downloaded JSON file.

Versioning of File Structure

The new Configuration Data file format supports versioning of the Configuration Data file structure. This means that the system structure governing Fynapse at any given time will be identified by a hardcoded version number. This version number will change with new updates to the governing structure.

When you download the file, it will contain information about the governing version:

1
{
2
    "version": "v20230211",
3
    "downloadTime": "2023-11-03T10:04:05.819900999Z",
4
    "downloadedBy": "john.doe@myaddress.com",
5
    "configuration": {
6
        "businessCalendars": [

We will be supporting older formats for a period of time. If you try to upload an older file which e.g. is missing a mandatory field, Fynapse will add this field to the configuration you’re uploading.

Comparative list of differences in the JSON structure:

Old JSON File

1. Configuration started with the first item, i.e. Entities:

1
{
2
    "entities": [
3
    

2. Each configured item required a UUID ID:

1
"businessCalendars": [
2
          {
3
              "id": "58466584-7b8a-48c6-9998-0d9ae02ce56b",
4
              "name": "MyBusinessCalendarWeekends"    

This UUID id was used when the item was referred to in other items:

1
 "accountingConfigurations": [
2
          {
3
              "id": "68691ce0-4c5b-4cde-9e06-cd71a2ce01cf",
4
              "name": "US_GAAP",
5
              "fiscalCalendar": "3fc60494-5390-4199-ac08-d2dafb228b07",
6
              "businessCalendar": "55b54307-bacb-4cb7-b92c-67d77456210e",
7
              "dimensionSetId": "63580f70-ad15-43a0-b6bf-dd99096870b8"
8
          }
9
      ]

3. Some items, i.e. Business Calendars, Business Event Definition, Journal Line Definition, Business Event Types, required a “version” property:

1
"businessCalendars": [
2
          {
3
              "id": "58466584-7b8a-48c6-9998-0d9ae02ce56b",
4
              "name": "MyBusinessCalendarWeekends",
5
              "status": "ACTIVE",
6
              "version": 1,
7
              "effectiveFrom": "1900-01-01",
8
              "effectiveTo": "2099-12-31"

4. When the file was downloaded, no information was added at the beginning:

1
{
2
    "entities": [                                      
3
    

5. In the old download file, each item had information when it was created and/or updated:

1
"businessCalendars": [
2
        {
3
            "id": "e6ef80ba-7e87-4526-b469-3ce32b3c993b",
4
            "name": "MyBusinessCalendar",
5
            "status": "ACTIVE",
6
            "version": 1,
7
            "effectiveFrom": "1900-01-01",
8
            "effectiveTo": "2099-12-31",
9
            "created": "2023-10-16T11:46:06.648262Z",
10
            "updated": "2023-11-18T10:16:09.648434Z"
11
        }

New JSON File

1. “configuration“ was added at the beginning of the configuration and the order has been rearranged to start with Business Calendars:

1
{
2
    "configuration": {
3
        "businessCalendars": [

2. The UUID ids have been removed:

1
"businessCalendars": [
2
          {
3
              "name": "MyBusinessCalendarWeekends"
4
                  

Now when the item is referred to in other items, the “name“ property is used:

1
 "accountingConfigurations": [
2
          {
3
              "name": "Test Accounting Base 1",
4
              "fiscalCalendarName": "Test Fiscal Calendar",
5
              "businessCalendarName": "Test Business Calendar",
6
              "dimensionSetName": "Test Dimension Set"
7
          }
8
      ]
9
      

3. The new structure no longer requires the “version“ property:

1
"businessCalendars": [
2
          {
3
              "name": "Test Business Calendar",
4
              "status": "ACTIVE",
5
              "effectiveFrom": "1900-01-01",
6
              "effectiveTo": "2099-12-31"
7
              
8
              

4. Now the downloaded file contains information about the version number of the file structure, which user downloaded the file and when:

1
{
2
    "version": "v20230211",
3
    "downloadTime": "2023-11-03T10:04:05.819900999Z",
4
    "downloadedBy": "john.doe@myaddress.com",
5
    "configuration": {
6
        "businessCalendars": [

5. The new file doesn’t export this property:

1
"businessCalendars": [
2
            {
3
                "name": "MyBusinessCalendar",
4
                "status": "ACTIVE",
5
                "effectiveFrom": "1900-01-01",
6
                "effectiveTo": "2099-12-31"
7
            }            

There are two possible scenarios of how to migrate your existing JSON file.

To migrate existing configuration into the new file structure:

1. Go to Bulk Operations > Configuration Data.
2. In the Bulk Configurator section, switch the feature flag to New.
3. Download your existing configuration. Your configuration will be downloaded in the new file structure. You will now be able to re-upload the configuration with the new structure.

If you have an old configuration file saved locally, you can easily update it to the new structure:

1. Go to Bulk Operations > Configuration Data.
2. In the Bulk Configurator section, switch the feature flag to Old.
3. Upload your local file.
4. Switch the toggle to New.
5. Download your configuration. Your configuration will be downloaded in the new file structure. You will now be able to re-upload the configuration with the new structure.

For more details, refer to Configuration Data.

Support for Multiple Currencies

ISO-defined List of Allowed Functional and Reporting Currencies

As part of the on-going implementation of support for multiple currencies, we implemented an enhancement that will ensure functional and reporting currencies used in Fynapse will be consistent with an ISO-defined list of currencies built into the system.

For more details, refer to Multiple Currencies Configuration.

Documentation

Fynapse Release Policy has been published in Fynapse Releases section.

For more details, refer to Fynapse Release Policy.

Microsoft Dynamics 365 Integration

As part of the on-going implementation of Microsoft Dynamics 365 integration with Fynapse, we implemented functionalities that allow you to:

• Add new configurations that enable you to establish connections between Fynapse and particular Microsoft Dynamics 365 instances.
• Extract processed Journals automatically according to schedules defined by you to eliminate manual extractions.
• View Journals in Fynapse, i.e. a functionality that provides you with the backward traceability from General Ledger in Microsoft Dynamics 365 to Subledger in Fynapse.

For more details, refer to the section Microsoft Dynamics 365.

Video preview:

Part 1: Adding a New Configuration

Part 2: Creating a New Extract

Part 3: Extraction Logs

Part 4: Backward traceability from General Ledger in Microsoft Dynamics 365 to Subledger in Fynapse