Quantcast
Channel: Microsoft Identity Manager forum
Viewing all articles
Browse latest Browse all 7443

Attribute created as non-indexed string now needs to be a Filter criteria attribute. Best way to change type non-indexed to indexed without destroying the system?

$
0
0

We have a FIM solution that is in use.

A custom attribute "CustomExt9" was created to hold a piece of information. At the time there was no need to maintain an index for it.

We now realise that the attribute needs to be part of a Set criteria for Notification purposes.

This custom attribute has been added happily to the Filter Permissions allowed attributes (no check made there for indexed or not), it exists in the RCDC forms and Synchronization Engine flows, sync rules etc.. Basically its everywhere.

What dangers are there if I simply delete the non-indexed string attribute in FIM in Administration/All Attributes then recreate it WITH SAME NAME but as an indexed string?

I realise after this I must reload  schema  on the FIMMA on the Synch Engine.

Can I get away with just the delete / readd of the custom attribute without it affecting all other existing MPRs and stuff???????


Viewing all articles
Browse latest Browse all 7443

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>