After BR causing duplicate entry in audit history

[revathy muruga1]

Hi Team,

I have "Primary interface" field with same backend name on two table(custom extended attributes and business application).

1. after br - update :

if primary interface changes in custom extended attributes table , this script updates the primary interface field on business application table.

2. after br - update:

if primary interface changes in business application table, this script updates the primary interface field on custom extended attributes table.

history list on custom extended attributes table.:

[Laszlo Balla]

It sounds like one BR is triggering the other - you can verify this if you do a BR debugging.

Try adding .setWorkflow(false) to the the BRs to prevent this, i.e.

bapp.setWorkflow(false);

in the first BR just before your bapp.update(); line, and

customE.setWorkflow(false);

in the second BR, just before your customE.update(); line.

[Sagar Pagar]

Hi @revathy muruga1,

There may be another after update business rule is running after this business rule. Hence it adds two updates record in audit.

Thanks,

Sagar Pagar

[Saurabh Gupta]

Hi @revathy muruga1 

Your code 

customE.update()

and bapp.update()

should be within "If" blocks.