Created on 10 May 2019
icon_unfollowing
Login to follow
cool-data-mover

Cool Data Mover

Stable version 2.7.10 (Compatible with OutSystems 11)
Other versions available for 10
Uploaded on 16 Apr (2 days ago) by 
cool-data-mover

Cool Data Mover

Created on OutSystems 11

Version 2.7.10

Stable
Current
See documentation
Application Package
Uploaded on 16 Apr (2 days ago) by 
Compatible with:
Version 11
Database:
All
Release notes:

New features

  • Added the possibility to run certain DB CPU intensive workers as a single thread for entities containing many rows. See the following site properties in CDM_Dispatcher

    SingleThreading_Enabled
    When enabled, DB-CPU intensive workers will run single threaded meaning that when those workers run, no other workers are allowed to run. SingleThreading is to prevent that the CDM consumes high amounts of DB-CPU. Currently, single threading is available for export workers. It will be activated when the number of rows in the entity exceeds the value in SingleThreading_Threshold.
    SingleThreading_Threshold
    Only applicable when SingleThreading is enabled. When the number of rows in an entity exceeds the value of this site property, DB-CPU intensive worker for that entity will run in SingleThreading mode.

  • Added ‘Show timings’ checkbox to the WorkItem list in the Run logs. Checking this box will show
    detailed timing info regarding the creation, mediation, start and finish of the workers as well as the threading mode (normal or single).
  • This detailed timing information is also available on the WorkItems tab on the run download spreadsheet.


Fixes

  • Fixed an issue where the ‘Type’ dropdown on the StorageLocation popup incorrectly displayed the value ‘Amazone S3’ for network share locations.
Application Objects:
Cool Data Mover has 1 AOs.

Version 2.7.8

Stable
See documentation
Application Package
Uploaded on 26 Mar (3 weeks ago) by 
Compatible with:
Version 11
Database:
All
Release notes:

New features

  • Added the possibility to use any combination of filters; custom, entity and tenant.
  • Removed the logging in the general log in case of ignorable errors because of duplicate inserts into the internal export key table
  • Added Entity Filtering
    An Entity filter limits the number of exported records by applying a filter to the respective entity during Export. An Entity filter can be defined for every entity in the package by clicking the filter icon just before the entity name during package definition. The way Entity Filters are defined is similarly to the way existing custom filters are defined. An Entity Filter only applies to the selected entity.
  • Enhanced the overview of entities on the export screen to include additional information that indicates whether and which type of filtering is applied to entities. When hoovering over the icons in the overview, details on the filter are shown.


Fixes

  • Fixed an issue with using large lookup tables resulting in aborted threads because of timeouts in the database.
  • Fixed an issue in which the combination of custom filters and entity filters resulted in ignoring the entity filters.

Application Objects:
Cool Data Mover has 1 AOs.
Created on OutSystems 10

Version 2.5.5

Stable
Solution Package
Uploaded on 20 May 2021 by 
Compatible with:
Version 11
Version 10
Stack:
.NET
Database:
All
Release notes:

This version includes lots of new cool features such as 

- Data model comparison
- Performance enhancements
- Reporting of data inconsistencies
- Improved validations
- Soft key support
- Support for foreign keys to external tables
- Timezone conversion support

See the complete Release Notes at https://www.coolprofs.com/cdm-downloads-en/ 

Version 2.3.18

Stable
Solution Package
Uploaded on 25 November 2019 by 
Compatible with:
Version 11
Version 10
Stack:
.NET
Database:
All
Release notes:

New Features
·         Rewrotethe Delete functionality using (Light)BPT instead of timers. 

·         Removed the unused option ExcludeBinaries 

·         Added a package option to prevent the launch of new BPT processes during an importAlso removed the new events generated by OutSystems from the event queue. 

·         ‘Duplicateinsert’  errors are ignored when retrying an ImportFilePart worker. This accommodation the possibility to retry the inserts when during previous executions inserts were already committed. 

·         Added the generation of correct IBANs for the Netherlands, Belgium, France, Luxembourg, Denmark, and Germany.  When another country code is suppliedby default a dutch IBANis returned. 

·         Added a new delete validation warning for the situation that an entity refers to an entity in another catalog. In that case, the referential integrity is not guaranteed by the database and the data of entity B can be deleted.  

·         Added the option to Move the ServiceCenter tenant entity

·         Improved the performance of the screens on which the list of modules and the list of entities are shown.


 
Fixes

·         Fixed an issue whereby the export of binaries failed when no binaries were found with a length under the max binary size limit. 

·         Fixed a performance issue with retrieving the entities from a module that contains a large number of entities. 

·         Fixed an issue with an incorrect catalog name for the internal CDM tables when the CDM is installed in a separate catalog. 

·         Fixed an issue with replacing an attribute value during export 

·         Implemented a workaround to deal with a bug in some OutSystems platforms on MSSQL whereby the tables are not represented in the SYS.ALL_OBJECTS table. 

·       Fixed an issue with retrieving the entity definition information when that entity resided in a different catalog than the CDM itself. 

·       Fixed an issue whereby data that referred to a removed record of a static entity with a non-auto number identifier resulted in an error. 

·       Fixed an issue by preventing the deletion of the initial records in the event tables (osevt*). 

·       Fixed an issue with getting entities from the database based on System tables type = ‘U’. In some situations, user_tables have a NULL value. This prevented from opening the modules inside the packages 

·       Fixed an issue whereby inserts in the export key table resulted in an error regarding data conversions from int32 to String.