Answered

Join with Priority on Date field is picking the older entry

8 years ago in UNIFYBroker/Aurion • updated by 8 years ago • 6

I have multiple Aurion Employee records for each Aurion Person. I joined on the Person Number and then selected Priority and the Date_Commenced field (which is a Date data type in the connector schema). Based on the comment in the UI saying the highest value is picked I expected the record with the latest Date_Commenced to be joined, however it picked the older record. Is this how it's supposed to work? It seems wrong to me.

I have switched to using a status field and telling it to prioritise 'ACTIVE' - however I've been told that status is manually managed in Aurion so had thought the Date_Commenced filed would be a safer option.

Vote

Answer

Answered

8 years ago

No, the use cases have always required it the other way. The recent selection is the only one that prioritises closest to the window. If you'd like me to add this to the backlog please let me know. In the meantime check to see what other implementations are doing and/or do the selection in the solution.

Thanks.

Replies 6
Oldest first
- Newest first
- Oldest first

Under review

8 years ago

Hi Carol,

This can't be the first time this issue has come up as it's mentioned here. Have you checked the configuration for other sites? It might be worth mentioning this issue on Yammer.

Thanks.

8 years ago

My question is specifically on specifying a Date field as the Priority attribute when making a join in an IdB adapter - shouldn't it choose the record with the latest date and not the earliest?