0
Answered

Support for DateRelational.Compare.String and Relational adapter transform types

Adrian Corston 7 months ago in UNIFYBroker Service updated by Matthew Davis (Technical Product Manager) 7 months ago 1

I have encountered a UNIFYBroker customer who has DateRelational.Compare.String and Relational adapter transform types configured (UNIFYBroker 5.1.0#2).  I have been asked to upgrade them to the latest UNIFYBroker release.  Can you please confirm:

1. Are these transform types still available in the latest UNIFYBroker release?

2. Has their functionality or features changed since the 5.1.0#2 release?

3. If they are available, what are they now called in the UNIFYBroker UI?

Image 6506

Answer

Answer
Answered

Hi Adrian,

The DateRelational.Compare.String and Relational are old names for the current Join transformation. This transformation was reworked back in UNIFYBroker 4.1, so it's likely this configuration was upgraded from an old 3.x or 4.x config up to 5.1.

The product still respects the old transformation names, although may not 

Between 5.1 and 5.3 there's been no changes to the way that entity windows and selections function. 

There was no changes to the join transformation functionality itself, however there was minor changes made to the overall transformation process in terms of how changes are aggregated and reported (as support for postgresql was added). I don't expect this would impact functionality as we've not had other customers report issues between the versions.

If you are migrating the configuration rather than re-creating, you may find the UI continues to report the transformations using the old name (as you see in the screenshot above). Otherwise a new transformation can be created using the Join transform.

Let me know if you've got any more questions or have issues with the upgrade.

Answer
Answered

Hi Adrian,

The DateRelational.Compare.String and Relational are old names for the current Join transformation. This transformation was reworked back in UNIFYBroker 4.1, so it's likely this configuration was upgraded from an old 3.x or 4.x config up to 5.1.

The product still respects the old transformation names, although may not 

Between 5.1 and 5.3 there's been no changes to the way that entity windows and selections function. 

There was no changes to the join transformation functionality itself, however there was minor changes made to the overall transformation process in terms of how changes are aggregated and reported (as support for postgresql was added). I don't expect this would impact functionality as we've not had other customers report issues between the versions.

If you are migrating the configuration rather than re-creating, you may find the UI continues to report the transformations using the old name (as you see in the screenshot above). Otherwise a new transformation can be created using the Join transform.

Let me know if you've got any more questions or have issues with the upgrade.