Skip to main content

Hi Experts,

Can anyone help me to sort the following problem?

Customer is facing a issue whenever they tried to inactive some users.

In FSM Client, they cannot change some person records in FSM due to an error that we get everytime when attempting to save the changes. For some users, whenever saving changes made to the person record, we receive an error "row ____ was changed after it was selected." 
 

I have tried the following solutions from the community post, but unable to sort the issue.

https://community.ifs.com/business-rules-305/error-row-request-2444-was-changed-after-it-was-selected-reselect-and-try-again-2815

 

There are 2 user_def fields defined in the person custom metadata and they are both set to force select = Y. There is a relationship with cb_weekday table to the person metadata and cb_weekday has fields that also updated to force_select = Y.
 

Note :- This happens if customer attempt to change anything on the person screen..

They are able to circumvent the error by updating the person record using a t-table update."

 

What could be the possible way to sort this issue?

 

 

Thanks & Regards,

Dilushkumar

Hey @Dilushkumar Vasudevan 

This is a common error.

It usually means that another person or process updated the record.

The common flow will be to refresh the record and update again. Unless there is a more fundamental issue that needs to be troubleshoot.

Cheers!

It is also possible that you have one or more active Business Rules which make redundant updates to the same record within the same transaction.  Check your active Business Rules acting on the PERSON table, and any related extension tables.

@Dilushkumar Vasudevan 

Check the metadata for the user def fields, if they are marked as mask type UPPER but the records were created before that was enforced, then FSM will think a change has been made and report an error just like what you are getting. So check the value for mask type, and check the values in the database for those user defs. If that turns out to be the issue, you will need to update the database values to be all Caps or change the mask type to none.

 

Cheers!

Reply


Terms & ConditionsCookie settings