New feature: Include Assignment Filters in MigrationTable.json for Filtered Assignments

[SasStu]

Hi,

Currently, the MigrationTable.json includes groups used in assignments, but Assignment Filters are not part of this file. Unlike groups, Assignment Filters need to be exported as objects in the export root. Only then importing filtered assignments from a different tenant will work and an existing filter with the same name will be used.

It would be great if Assignment Filters were also included in the MigrationTable.json. This enhancement would allow importing filtered assignments from a different tenant without the risk of overriding filter objects in the target tenant.

Thank you for your work!

Sascha

[Micke-K]

Hello,

Groups do need to be export, if you need to import them.

So you would expect the same for filters? Just name and id of all Assignment Filters in the Migration json and then expect them to exist in the destination tenant? What would you expect to happen if they are not there. The assignment would not import since it has a GUID for a filter that does not exist,

Just try to understand expected behaviour.

Cheers!

[SasStu]

Hi,

you described exactly what i meant! I am using delta packages to update tenants to a newer settings release. I therefore can assume what items already exist. And I don't want to update exiting filters and groups because the content can vary between different tenants.

Currently I have to export the filters and then disable importing them. Which causes a risk of unintentionally overwriting changes.

Best regards

Sascha

[Micke-K]

Hello,

I'll see if I can figure out a good way to implement this. It should be possible, but I need to revisit how I handle the Migration file. It was a while since I did anything with that.

Cheers!