0
Not a bug

Two identical transformations producing different results in same adapter

Bob Bradley 2 years ago • updated by anonymous 2 years ago 6

The following 2 identical transformations are being used to flow the same data into 2 separate CS properties being used in the FIM configuration for different purposes.

Transformations.png
The data in each property should be identical, but it is not ... there are some 1.3K users with nulls in the DEPARTMENTS field but which have values in the ALLDEPARTMENTS field, e.g.
ValuesForUser.png
3.5K have values in both.

Please advise what could be causing the null values in the second property, but only for about a quarter of the user base?

This is having a significant impact at CSODBB where the data in the original mapped value (DEPARTMENTS) is now significantly compromised. There is only one user with a null value in the ALLDEPARTMENTS property.

Note that in testing both values always had the same values present - this is only something which I have spotted since the change to introduce the second transform was promoted before Christmas.

Logged for customer against https://unifysolutions.jira.com/browse/CSODBB-536

Affected Versions:
Fixed by Version:

Answer

Answer
Under review

What do you mean by "2 identical transformations"? They are not the same, one has a string filter, whereas the other does not. Check the configuration for the filter.

Answer
Under review

What do you mean by "2 identical transformations"? They are not the same, one has a string filter, whereas the other does not. Check the configuration for the filter.

You're right of course - I didn't spot that because the only thing that is different is the transform name itself (the console shows exactly the same parameters now, although at one stage the "remove duplicates" was only on one of them). What I needed to look at was the XML transforms themselves, because the following is not surfaced through the UI:

<FilterValue>A</FilterValue>

That filter value matches a value of "HrStatus" ... so that makes total sense now.

My only question now is why doesn't the UI show the filter?

Happy to close this issue on the basis that presumably it is working fine, and I was unable to see the difference from the UI alone.

If you recreate the transformation, does the filter value show up? Curious to see if it's related to it being a legacy transformation (as evident in the old format of the name).

Hi Bob, is there any update on this issue?

Matt - this can be closed - see https://unifysolutions.jira.com/browse/CSODBB-536 which was resolved in Feb.  Looks like this got overlooked - although there is still the question of the UI bug with the filter?