This release is a hotfix release for version 3.1.  We had fixed the depth level issue in the previous version, however it created another depth level issue.

This version will resolve the depth level tag closing issue that was present in the previous version of the components when dealing with decimal depth levels.

The version 3.1 download has been pulled from the site.  All users who updated to 3.1 are strongly encouraged to download this new version.

This release has introduced one new component to simplify XML merging. The new component aptly named XML Merge Transformation allows you to take two columns of data in a row and merge them together based on certain conditions you set. This should solve the majority of the XML merging scenarios without having to write custom .NET scripting code to do the same functionality as it has been done in the past. All samples have been updated to show this functionality.

Additionally there has been a very important change to the XML Transformation and XML Destination adapters that could affect existing integrations. The change affects how depth levels are treated when you have multiple decimal depth levels that are lead elements. Be sure to read the upgrade documentation for version 3.1 to identify if it will affect your existing integrations so that you can alter the depth levels appropriately in the new version.

Lastly, due to all the related fixes and new functionality we have decided to raise the price of all components $50 dollars. This does not affect existing customers as they will receive the updates with their existing maintenance plans.

Enhancements:

• Add XML Merge transformation component and many new samples that use that new functionality.
• Merged many of the XML SSIS Toolkit examples into single DTSX packages to make reading the samples easier.
• Added Omit XML Row option to XML Transformation and XML Destination Adapter components.
• Added offline registration capability.
• Added row element name blank validation to XML Transformation and XML Destination adapters.
• Updated existing samples to utilize the new XML merge functionality.

Bug Fixes:

• XML Transformation and XML Destination adapter would not output decimal depth levels marked as lead elements at the proper level when already nested inside of a depth level at the same level.  For instance a depth level of 2.1 nested inside of a level 2 would not put it at the correct level, it would go one level deeper then it should have.
  • Important: Read the documentation on why this was done and if it can affect your current integrations.
• Fixed inconsistent metadata issue with XML formatter task that would occur when you remapped parent columns that would cause the lineage ID's to change further down the pipeline.
• Fixed depth level 1.1 issue with XML Transformation and XML Destination components.  Would receive a stack empty error when attempting to use these depth levels.
• Corrected a scenario where you reconnect a parent component which would then cause the XML mappings to get corrupted in the XML Transformation and XML Destination adapters (inconsistent meta data).
• Corrected a bug where it would remove the XML output column in the XML Transformation component when you were in the advanced editor and hit the refresh button.

• Added row element name is blank validation function to XML Transformation and XML Destination adapter components.

This release is a hotfix for the version 3.0 release a few days ago.  The following issues have been corrected in this release:

• XML Transformation adapter did not properly handle attributes at depth level 1 when attaching them to the row level element.
• The File Task did not refresh the user interface properly due to case sensitivity issues with the drop down controls.

This release has ushered in two new data flow components: XML Transformation and XML Formatter Transformation.

The XML Transformation allows you to map source data as XML within the pipeline and output the resulting XML into an XML text column (NTEXT).  It can do this for every row or if the data is sorted you can specify a primary key and on the change of the primary key it will output the row to the children pipeline components.  As you can see this would be very powerful as you can then use the join transformations that come with SSIS to then merge many-to-many and one-to-many relationships together.

During the merging process it is often necessary to reformat your XML as it will get slightly unformatted (missing indents).  The XML Formatter tool allows you to reformat your XML by adding or removing idents, and changing encoding format (UTF-8, UTF-16, UTF-32, etc).

Be sure to checkout the Family Tree examples in the XML SSIS Toolkit for a demonstration of the new functionality.

Enhancements:

• Two new components created, the XML Transformation data flow component and the XML Formatter transformation data flow component.
• Additional validation has been added to the XML Destination Adapter
• Code refactoring (some minor speed increases)

All versions of the Keelio Software products have been upgraded to version 2.42.  This release contains several important bug fixes.  Any user using a previous 2.X version of the components should upgrade to this release to avoid potential component property corruption.

Bug Fixes:

1. XML Destination Adapter may end up with corrupt component propertys in a specific scenario.
2. Attributes with NULL data would cause the XML adapter to fail
3. Installer would not properly log installed versions of .NET framework

Enhancements:

1. Dynamics GP eConnect adapters now contain more progress status messages.