More control over FIMService MA
FIMService MA being treated as a special one (no transforms, MRE control etc)
In some cases we need more control on FIMService MA where we can do controls like any other MA. We have seen reverse joins also not working very well and in a DR scenario FIMService MA caused issues for us..
Thanks for your feedback! — David Steadman | MIM Lead & PM Identity governance and administration engineering team
Ian Bassi commented
It would be nice to have an option to prevent the FIMService connector writing back changes in the Sync Engine when portal sync rules are not being used.
Agree with carol, hit that limitation multiple times, also portal is for modifiying data either manually or by activities.
Carol Wapshere commented
In addition remove precedence restrictions. Sometimes I want to flow an initial value from one MA, then let a manual value get set in the Portal, then flow a final value from a third MA. There is nothoing wrong with wanting to do this and every other MA handles it fine!