0
Answered

Identity Broker - join transformation priority calculation for decimal types

Matthew Dayne 1 year ago • updated 1 year ago 8

I have a solution in which we are trying to select a "position" record for a given employee. The method that we a putting in is to check the position end date with the priority option within the join transformation. The timestamp type is not suitable because it would select the closest date not necessarily the further most, however I have access to the value in decimal format (see image)



However this appears to not be selecting the expected record, in this case the expected one is the lower record. Rather it is selecting the top record which seems contrary to the "largest value is selected" description of the priority.

Are you able to explain how IdB choose which record to join on when a decimal value is selected for priority?

Affected Versions:
Fixed by Version:

Answer

Answer

The solution to issue that we were experiencing was to remove the priority selection and instead rely on using a rolling window filter set to type "Relevant". The description from the documentation: "A sliding date window which takes the first matching entity inside a window. If no entities can be found inside that window, the first entity after the window will be selected. If still no entities can be found, the first entity before the window will be selected." As seen Here.

GOOD, I'M SATISFIED
Satisfaction mark by Matthew Dayne 1 year ago

Connector schema for reference
Under review

Hi Matt,

How have you currently configured the join transformation? Could you please attach the configuration?

Hi Matthew, could you please provide an update?

Answer

The solution to issue that we were experiencing was to remove the priority selection and instead rely on using a rolling window filter set to type "Relevant". The description from the documentation: "A sliding date window which takes the first matching entity inside a window. If no entities can be found inside that window, the first entity after the window will be selected. If still no entities can be found, the first entity before the window will be selected." As seen Here.

Under review

Perfect, thanks! Any thoughts how we could make that clearer or have got to the solution more quickly?

A link to the documentation might have let me discover the various types of Sliding Window filters much faster. In this particular case I was also initially distracted by the description being "Filter" where in fact not all options are strictly filters but rather selection criteria.