Release Notes 3.2.x

Release Notes for 3.2.19

Bugfixes

• Predefined Filter: Selected values were placed 2 times in quotation marks (Predefined Filter: Sales Organizations → selected language)

Changes

• Improved reading of messages between dabExporter.Core.dll and dabExporter.SapConnection.Wrapper.exe (OutOfMemoryException while serializing extracted data)
• SAPUILandscape.xml is supported in addition to saplogon.ini when reading connection data
• The result database of an SQLite export was changed from "result.db" to <Downloadname>_<Timestamp>.db (important for PI integration)

Release Notes for 3.2.18

Bugfixes

• AX Analytic and Parameterset can be unselected
• There are not more SAP log entries in ST22
• missing filter vlaue in packagemanagement could lead to a client crash
• substring transformation in dependencies was done too late
• if the last record of a SAP packet had a ' in a primary key field it could happen that this record got extracted twice
• date / time was changed while editing a schedule if the recurrency changed
• scheduler did not start downlodas any more if there was a schedule its owner got deleted

Changes

• updated PP list
• owner of schedule is displayed
• SNC connections can be created
• timeout of SQLServer was increased
• date values can be extracted as integer in SQLServer
• if there is a PK-Violation in SQLServer a new delta table will be created and the download will be continued (this is not possible if a PK-Violation is within one SAP datapacket)
• if a SAP record contains \0 and is primary key then it will be replaced with " "

Release Notes for 3.2.17

Bugfixes

• during the export an error "connection is closed" could occur. This error was added to the automatic download retry
• the error "no data received" was added to the automatic download retry
• there was an error migrating SAP connections from previous dab:Exporter versions (connections could not be migrated)
• if there was a space at the end of the dab:Exporter server address in the client, the client crashed
• if the databases could not be loaded from the SQLServer the client crashed
• querying the SQLServer databases was case insensitive
• it was possible to save one SQLServer connection in the dab:Exporter more than once
• with the CSV export it was possible that if the header line was very large that an additional linebreak was added to the resulting file after the header line
• it was possible to add APPEND structures in the packagemanagement to a package

Changes

• updated PP list
• installation manuals for installing the SAP RFC function module were updated
• added monitoring for downloads with SQLServer. During the creation of a download you can choose in the settings for the datasink whether the progress should also be logged in the destination database. Two tables get created: dab_exporter_download_progress and dab_exporter_download_table_progress. The content of the table is equal to the Download Progress Overview which you can see in the dab:Exporter Client

Release Notes for 3.2.16

Bugfixes

• During the export to ACL AN + ACL AX unnecessary new lines were written into the FIL file

Release Notes for 3.2.15

Bugfixes

• CSV field separator display in the client was faulty

Changes

• Update PP list
• Validation of hardware was removed

Release Notes for 3.2.14

Bugfixes

• Mutated vowels were not correctly displayed for ACL AX exports
• Exports to ACL AX and ACL AN were changed to include a line break for the last record
• Fixed an issue preventing the dabFunctionModuleTester to test a SAP connection

Changes

• Added an option to remove the prefix of the data file in the ACL AN extraction options
• In the ACL AN extraction options an option was added to use the technical field names as description
• Before starting a download the scheduler will test the SAP connection again
• At the creation / changing a SAP credential will trigger a connection test
• Export option "date format" for ACL AN was removed
• Increased IPC timeouts (dab:Exporter internal)
• Updated ERPConnect to to latest version
• SAP connections can be created using the SAP Netweaver dll

Release Notes for 3.2.13

Changes

• An option was added in the export settings for SQLServer during the creation of a new download. This option "use primary keys of SAP" is checked per default and represents the previous behavior of the dab:Exporter. If the option gets unchecked a new column named "DAB_EXPORTER_ID" will be added to every table and used as primary key. The column value is the SHA512 value computed over all normal primarykey field values and the system field value. This mechanism also automatically gets triggered if the SAP table has more than 15 primarykey fields because the export would fail for older SQLServer versions which only allow 16 fields per primarykey (index). As a side effect now tables which only distinguish in trailing blanks in the primarykey field values can be exported.
• The name of the primary key was changed from PK_TABLEALIAS to PK_SHA256HASH (computation  = tablealias + timestamp of the export)
• In the SAP credentials the name of the table for the testdownload can be entered manually. Per default T000 is used. The registry key for disabling the download test on client side was removed.
• The retrieve button for getting the SAP installation number during the creation / change of a SAP system was removed. The installation number will be set automatically after the test. SAP connections can only be saved after a test.
• UI of creating / editing SAP connections was adjusted
• The automatic reconnect of SAP connection terminations was extended to include "CM_NO_DATA_RECEIVED" (this only has to be present now) and the combination of "Connect_PM", "MSHOST=" and "R3NAME="

Release Notes for 3.2.12

Features

• CSV export with SAP field descriptions instead of technichal field names
• Destination files of CSV export can be created without package prefix

Bugfixes

• Downloads did only start after a service restart if it is a first time installation
• Access rights of log folder adjusted

Release Notes for 3.2.11

Features

• Updated privacy protection list

Bugfixes

• An error caused by the table CaseSensitiveFieldList in SQLServer was fixed

Release Notes for 3.2.10

Changes

• dab:Exporter will always be installed as 64bit application
• Connection to SAP will be made via a separate 32bit process which does not require the librfc32.dll to be present as 64bit dll
• Parsing of ACL scripts will be done in a separate 32bit process

Features

• Updated privacy protection list
• Changes to the PrivacyProtection settings are logged
• In the license overview the state whether PrivacyProtection is licensed is shown

Bugfixes

• During the creation of  a new SAP system the credential was not checked again after a test if it is changed
• The SAP connection test in the settings SAP Systems only checks in the second step whether the installation number can be read
• Validation during the creation of a new SAP system rewritting in order for the client not to crash
• Creating a new download with PrivacyProtection level Pseudonymisation enabled could lead to an error if no password was set
• Activation of E-Mail notifications was disabled if the dab:Exporter server was restarted
• E-Mail notification settings required a username / password
• A support package could not be created if a download was running
• The dab:Exporter server crashed if the termination date of a schedule was reached
• A hint is shown that a " can't be used in SAP credential password
• Changed PrivacyProtection settings migration from 3.1 to 3.2
• If a download to AX crashed and the destination file was still present the extracted data was appended to this file

Release Notes for 3.2.9

Features

• Installation manual contains description how to change the dab:Exporter to 32-/64-bit
• Setup installs the dab:Exporter as 64-bit application as default

Bugfixes

• Rework of the ACL™ Analytic Exchange settings test because it did not show erros correctly
• Pressing ESC during editing of dab:Exporter server connections crashed the client application
• The setting "show no warning if no download directories are present" worked the other way around
• Log-Archive service created huge amount of zip-archives if access rights were missing
• Displaying/editing filters in the packagemanagment could crash the client
• Previous downloads in the SQL Server target format were not displayed in the history

Release Notes for 3.2.8

Features

• Language of the UI can be changed in the settings without restarting the application

Bugfixes

• In the filteroverview during the creation of a download the filterpreview for a Python script filter displayed not the real result of the script evaluation
• Client crashed if in the packagemanagement in a dependency the transformation type substring was selected

Release Notes for 3.2.7

Features

• New splash screen and new dab:Logo
• Remake of login dialogue
• Remake of dialogue for dab:Exporter server addredsses
• Communication of dab:Exporter Client and Server is now completely via WCF by using TCP
• Communication of dab:Exporter Clietn and Server can be secured with SSL

Bugfixes

• After logging in it could happen that an empty packagemanagement was shown instead of the start screen
• During the creation of a download not all fields of dependent tables were selected if "select all fields" was clicked

Release Notes for 3.2.6

Features

• Executing ACL Scripts after an extraction works for ACL AN 11 and ACL AN 12. In order to get the script execution working the user of the dab:Exporter Server has to be set to a user which has a working ACL AN and has logged in into the launchpad on the dab:Exporter server with that account. Moreover it is recommended to use the aclscript.exe and not the aclwin.exe for the script execution.
• Included a new program called dabFunctionModuleTester.exe in the setup (00_sap_rfc) in order to test the SAP RFC function module just like the dab:Exporter does without the need to have a working dab:Exporter. The program requires .NET 4.5.1 or later and SAP Logon 720 or later
• Added batch files in the setup for installing the dab:Exporter Server and Client silently. The batch files must be run as administrator

Bugfixes

• A dependency could fail because the dependency value was not properly escaped
• A dependency could fail because of misplaced linebreaks in the SAP query
• Migration of schedules using the SQL Server target format from previous versions could fail
• The client could crash if a deleted SAP connection was used in a schedule and the client tried to load all schedules
• History of progressoverview could not be filtered by date properly
• History of progressoverview displayed administrators only their own downloads and not all
• Deleting messages of SAP connections and credentials showed wrong messages
• The client could crash if the management user clicked on greyed out sections of the application

Release Notes for 3.2.5

Features

• Extended installation manual for dab:Exporter to include URL reservations and download directories

Bugfixes

• ACL Import in the packagemanagement handles tables with _ correctly and table user_addr was added
• Error message at adding a new windows user was corrected concerning \\
• ACL script execution after download did not start (still version 10 supported only)
• Cryptographic error after changing the user of the windows service was fixed

Release Notes for 3.2.4

Features

• In the settings there is a new category named log archives. With this category you can tell the dab:Exporter when the log files should be archived and when the archived logs should be deleted

Changes

• In the packagemanagement did adding a table directly to a dependency not automatically apply the dependency fields
• In the settings of the download directories you can set whether users get displayed a warning if they have no download directories assigned when they create a download

Bugfixes

• Users which are not currently present (got deleted) but created credentials or schedules caused an error in the migration at the update from 3.1 or 3.0
• One could log in with wrong client versions
• Invalid AX settings of previous dab:Exporter versions caused during an update that the migration failed
• Not setting the option "overwrite existing tables" in the AX data sink could cause the dab:Exporter to download all data but not to write the table information into the AX database
• In the predefined filter "plants" a filter was removed which used the language setting of the credential
• Broken schedules states did not heal themself (e.g. SAP password expired and then get reentered)

Release Notes for 3.2.3

Changes

• Removed 64bit installation option from setup
• Testing of donwload directories shows success message. For testing you don't have to enter the edit mode any more

Bugfixes

• Filtering on user / SAP systems in the download history did not work
• Cloning SAP connections did not clone user credentials
• Predefined filter values were not included in the setup
• Migration of 3.0 packages with multiple dependencies failed
• At once failing downloads were not properly displayed in the donwload progress
• Loading of the SQL Management settings could cause an error if certain authentification types were used
• Editing MsSQL Mappings did not correctly fill the editing mask with already entered data
• First time installations could cause a license invalidation after entering the serial number

Release Notes for 3.2.2

Changes

• Pageloading of download history optimized
• In the schedules overview the size of tree of the schedules can be adjusted

Bugfixes

• Corrected errors in the setup
• Corrected errors during migration
• Adjusted default configuration
• User could not access download folders
• Download folders were not displayed in the current tab of the download history

Release Notes für 3.2.1