Null Function different behaviour from FIM 2010 to MIM 2016

Luca Tenti 20 Reputation points
2023-05-17T08:53:45.4933333+00:00

Hi,

I'm experiencing a different behaviour from Sync Rule inbound between FIM 2010 and MIM 2016 SP2

There is an inbound rule which check a boolean value and if it is true then use Null() function as "do nothing".

This is working in FIM 2010.

Insted in MIM 2016 this flow bring null value into metaverse connector.

I can't find FIM 2010 function reference to get detailed description and check if this breaking change is documented.

In MIM 2016 function reference I can see:

"The Null function is used to specify that the MA doesn't have an attribute to contribute, and that attribute precedence should continue with the next MA."

https://learn.microsoft.com/en-us/microsoft-identity-manager/reference/mim2016-functions-reference

It seems that the correct behaviour is still to skip flow also in mim 2016 but is not the case.

Can anyone confirm this result?

Thank you

Best regards.

Microsoft Security | Microsoft Identity Manager
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.