Skip to main content
Solved

Mass update xml failing to update records

  • March 11, 2024
  • 2 replies
  • 154 views

Forum|alt.badge.img+7

HI All,

i am facing an issue with below mass update xml. xml is created  to update task status as Missed and closed for  ETL  period over tasks. When  i am  running below xml if any record /task has an error  the entire xml is failing to update.it should skip error records and update other tasks but its is not working like that.

Kindly suggest the way to skip error records and update next records.

<perform_batch>
  <sequential_independent>
    <mass_update_task>
      <hierarchy_select result_name="task_update">
        <primary_table>task</primary_table>
        <attrs>
          <attr>task.task_id</attr>
        </attrs>
        <from>
          <table>task</table>
          <table>PMR_MISSED_N_CLOSED_TASK_VW</table>
        </from>
        <where>
          <join_constraint>
            <constraint>
              <left_operand>PMR_MISSED_N_CLOSED_TASK_VW.task_id</left_operand>
              <operator>eq</operator>
              <right_operand>task.task_id</right_operand>
            </constraint>
          </join_constraint>
        </where>
      </hierarchy_select>
      <task>
        <task_status>MISSED_N_CLOSED</task_status>
        <update />
      </task>
      <transaction_size>50</transaction_size>
      <synchronous>N</synchronous>
    </mass_update_task>
  </sequential_independent>
</perform_batch>

Thanks,

Durga

 

Best answer by SAMLK

Hi @Durga 

This is the default behavior of mass updates and fsm will skip the next lot of updates if there is an exception thrown, based on the transaction size to process in the mass update.  Therefore, suggesting you to change the element  <transaction_size>50</transaction_size> as  <transaction_size>1</transaction_size> which should resolve your problem

2 replies

SAMLK
Hero (Partner)
Forum|alt.badge.img+14
  • Hero (Partner)
  • Answer
  • March 11, 2024

Hi @Durga 

This is the default behavior of mass updates and fsm will skip the next lot of updates if there is an exception thrown, based on the transaction size to process in the mass update.  Therefore, suggesting you to change the element  <transaction_size>50</transaction_size> as  <transaction_size>1</transaction_size> which should resolve your problem


Forum|alt.badge.img+7
  • Author
  • Sidekick (Partner)
  • March 13, 2024

Hi Samlk,

 

Thanks for the solution its working!!!

 

Thanks,

Durga