Bugfix: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.8.3

• LucaNet.Cloud JDBC driver is now recognized correctly in Lucanet version 25.1.

Bugfix: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.8.2

• Problem with extending the primary key fixed. The problem occurred when a version 1.X.X was updated with version 2.8.0 or 2.8.1.

Bugfix: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.8.1

• Extracted values from table ElementAttribute are now fitered by AttributeCode = 'name'.

Bugfix: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.8.0

• The primary key of the 'Transactions' table has been extended by the column 'StatisticValueCategoryCode'.
   Attention: The change of the primary key of the 'Transactions' table is performed automatically during the first execution of the app (Only applies to MS SQL and PostgreSQL). Depending on the number of records in the 'Transactions' table and the performance of the SQL server, this process may take some time.

Bugfix: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.7.2

• FHW ID with value 0 is now possible.

Bugfix: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.7.1

• Update of an old version (<= 1.1.0) works now.

Enhancement: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.7.0

• Option added to specify whether the fiscal year for certain reporting entities starts in the previous year.

Enhancement: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.6.0

• Column DocumentDate added to the Transactions table.

Change: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.5.1

• Shrink log file when the app starts and ends (Applies only to MS SQL).

Enhancement: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.5.0

• Column LN.FWH-ID added to the Transactions table.

Bugfix: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.4.1

• In special configurations, it was possible that periods and dates to which opening balance values refer were missing in the Tables Period and Date (Foreign key error).

Enhancement: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.4.0

• Added option for exporting Transactions, Opening balance sheet values or Opening balance sheet values & Transactions.
• Handling of missing assignments moved to the Data staging tab.
• The opening balance sheet values are explicitly displayed in the Database content. 

Bugfix: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.3.3

• Drill down by contra account for SubLedgerAccount Dimension works now for a Oracle-based LucaNet.Financial Warehouse.

Bugfix: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.3.2

• Primary key violation prevented when exporting more than one year, but not up to 12th period. Legacy transactions are deleted correctly now.

Enhancement: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.3.1

• Support for LucaNet.Cloud JDBC MSSQL driver (available from LucaNet 23.1)

Enhancement: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.3.0

• Added option to apply the drill down by contra account for a custom dimension.

Bugfix: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.2.1

• Usage of a case-sensitive collation in MS SQL Server does not cause an error anymore.

Enhancement: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.2.0

• Added option to apply drill down by contra account for the SubLedgerAccount dimension.

Enhancement: #4043 - Exporting LucaNet FWH Values for BI Tools - 2.1.0

• Option for exporting element names for custom dimensions adjusted. The following options are possible:
  • ElementCode
  • Name
  • ElementCode + Name
     Attention: The configuration for the Export full names column is lost for the prefix currently chosen.
• Option added to define the number of custom dimensions (0 to 100)
• Option added to remove excess custom dimensions that have already been created in the Transactions table
• Option added to configure the contents of the following name columns of the dimensions:
  • SubLedgerAccountName
  • ProjectName
  • FunctionAreaName
  • BusinessUnitName
  • CostElementName
  • CostUnitName
  • OrderName
  • OrganisationUnitName
  • ProfitCenterName
  • StatisticAccountName
    The following options are possible:
    • ElementCode
    • Name
    • ElementCode + Name
    • Exclude dimension
      Note: When a dimension is excluded, both the name column and dimension column are no longer exported for the DimensionCode.
  • Option added to remove dimensions that have already been created from the Transactions table
  • AccountingAreaID column, which contains the OID of the respective reporting entity, added to the Transactions table
  • Added ETLProcessName and PostingCreator columns to the Transactions table

(WARNING!) Important Information:

Please make sure to read the following information before updating the App:

• This version of the app works with the following LucaNet versions or above: 
• LucaNet 22 LTS - 2111.0.78+7 - GA - 14/11/2022
• LucaNet 23 LTS - 2211.0.3+7 - GA - 14/11/2022
• Previous LucaNet versions are not supported!
   
• When using this app version (2.0.0) in combination with an SQL database that has already been filled by an older version of the app (1.X.X), irretrievable internal changes are made in the storage of the GUI-configurations in the SQL database, so that it is no longer possible to use an older version of the app (1.X.X) again.
• The app #4042 must also be updated to version 2.0.0 and executed in advance before version 2.0.0 of the app #4043 can be successfully executed.

Changes:

The following functional changes have been made:

• Saving of the app configurations in the Prefix and MetaInfoFWH tables
• Input assistance for maintaining the table for assignments was removed
• Specification of fiscal years was optimized
• Process of reading data from reporting entities with deviating fiscal years has been adjusted

Enhancements:

The following functional enhancements have been made:

• Possibility to read and delete the database contents was added.
• Possibility to add a suffix to the account name was added
• Possibility to export and import the table for assignments as a CSV file was added
• Possibility to add a column for the export timestamp in the Transactions table was added