Skip to main content
Question

FSM Mass Update Throwing Error

  • September 5, 2024
  • 4 replies
  • 60 views

Forum|alt.badge.img+3

I am unable to update all the records using the below xml for mass update. Some of the records are not getting updated  if I am doing a bulk update. It is working fine up to 99 records. Is there any alternative method by which I can make it work for a large number of records? 

<perform_exec_db_edit>
<parameters>
<sql_command>update person_skill set user_def4=null,user_def5=null where person_id='@expression[person_skill.person_id]' and 
user_def5 is not null and user_def4='AD'</sql_command>
</parameters>
</perform_exec_db_edit>

The server log is giving exception: Exception Message : Cannot exceed more than 100 nested business rules, check for recursive business process.

4 replies

SAMLK
Hero (Partner)
Forum|alt.badge.img+13
  • Hero (Partner)
  • 227 replies
  • September 5, 2024

Hi @TDCANJANA ,

Could you share the entire mass update xml here if possible? The shared mpm message is a exec_db_edit message.


Forum|alt.badge.img+3
  • Author
  • Do Gooder (Customer)
  • 6 replies
  • September 5, 2024

Hi @SAMLK , 

I have created 3 rules in one Business Rule. In one I am doing mass delete, in the other mass insert for new records and in another this update is happening. This is the xml for the insert. 

<perform_batch>

<sequential_dependent>

<update_person_skill>

<person_skill>

<person_id>@person_id</person_id>

<skill>@user_def5</skill>

<insert />

</person_skill>

</update_person_skill>

</sequential_dependent>

</perform_batch>


SAMLK
Hero (Partner)
Forum|alt.badge.img+13
  • Hero (Partner)
  • 227 replies
  • September 6, 2024

Hi @TDCANJANA ,

The requirement and the context that you shared is still not clear. Where are you pointing towards the mass update/delete/insert operations here? Could you at least share some screenshots please?


JuniSihombing
Hero (Customer)
Forum|alt.badge.img+11
  • Hero (Customer)
  • 130 replies
  • October 21, 2024

Hi @TDCANJANA,

 

this could also be caused by the default recursive occurrence in SQL Server which is 100.

 

Cheers,

~Juni


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings