Is it possible for a source to allow only CI insert but never allow to make updates using IRE?

[Suggy]

Is it possible for a source to allow only CI insert but never allow to make updates using IRE?

If not possible using IRE, I think making use of Business rule is the option. Do you knowing if there is some other solution?

[Mark Manders]

This depends on your setup. Is it the only source, or just one of many? And does it import CI's from the same class of other sources, or just one and is it the only source for this class? 

Reason why this is important: if you have servers coming in from this source and from another source and you are using IRE to prevent duplicates, your exclusion on this one source wouldn't work, since the other one still has them and it could get your CMDB to become a mess. 

Also: how is this source integrating with your instance?

[Suggy]

Hi @Mark Manders We have multiple sources  (say A,B,C) all of them updating servers tables.

But we dont want source 'C' to make any updates, but allow insert.

This source is connected via IH-ETL

[Patrick DeCarl1 · Accepted solution]

I am assuming you have reconiciation rules setup for the other two sources and this source you want to block? If not, you need to do so and make c the last source allow to update. Once you have reconciliation rules set up, you will need to create a Data refresh rule for source "c" and set the effective duration high. This will allow IRE to block data source C from updating CI as long as data source A and B are updating source withing the effective duration period. 

[Suggy]

Thank you!