Any issues using Before Insert Business rule to abort record creation?

[Suggy]

Hello,

Today we have many sources like - Data sources, IH-ETL, Rest API calls etc which creates/udpates CI records in CMDB tables.

We got new requriemetns like if the data source is sending a record which has 'Operating system as Win 2003' then dont allow to insert the record. If the product model is 'ABC' then dont insert the CI record etc.

We are planning to write a 'Before insert Business rule' to abort such records from getting created (while I know that we have other solutions like use onBefore script to filter etc), we still wanted to go with Before insert Business rule approach because this eliminates to spend time in correcting all the data sources vs just writing a single Business rule.

Question - Is there any impact if we use this method? Like performance impact or anything else? If there is any imapact, what is the impact?

(the incoming data may be huge sometimes say 10k inccming records of which 3k records might want to be discarded)

[Ankur Bawiskar]

@Suggy 

do you want that before insert BR to run when insert happens via API or backend (data sources etc)?

If not then ensure you add interactive session check condition in your BR

OR

you can avoid insertion in the transform maps when you create data sources

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Suggy]

@Ankur Bawiskar if any 'ANY' data source out there. 

My question is mainly on our approach of using a Business rule to abort the record creation - if it has any impact or not. If yes, what is the impact.

[Ankur Bawiskar]

@Suggy 

definitely it will have impact since the BR will run everytime for each row during insertion.

I already mentioned above you can handle this in transform map and you can use onBefore script for this

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Suggy]

@Ankur Bawiskar We also have IH-ETL's. 

And IH-ETL doesnt have an option to stop running the BRs by its nature, so of we are importing milltion of records via IHETL, then all the BR's will run in ths system. In that case there is no impact is it? Just curious to know 🙂