check-in records

[Former Member]

Hi,

Has anyone come across performance issues in MDM while using the check-in out processing.

What will be the alternative of using this feature to improve performance.

Appreciate all responses.

Thanks,

Kris

[Former Member · Accepted solution]

Hi Kris

If you are trying to do mass checkin or check out it will surely have performance issues.

CHeck in or check out should be done record by record either through defined workflow or properly authorized roles and users.

BR-

Ravi

[Former Member · Accepted solution]

Is Recording Locking an alternative solution to this, to solve the performance.

[Former Member · Accepted solution]

Hi KP,

Did you mean Locking --> Protect option in data manager?

But am not sure you can edit the protected record except its relationship.

where check-out automatically protected by editing by others.

where exactly you facing the performance issue:

• taking more time to check-out ( number of records)?

• Check-in back (more number of records)?

do write to us.

thanks

Alexander

[Former Member · Accepted solution]

Actually the performance is slow due to check-in out in the custom based portal application. So trying to work around whats better to introduce to improve the performance.

Thanks for all responses.

KP.

[Former Member · Accepted solution]

Hi Kris

If you are trying to check in from Portal check for all MDM validations defined. A record when checked in MDM triggers all validations set ofr automatic execution.

Try remove the trigger action for the validations to None and performance will be faster.

BR-

Ravi

[Former Member · Accepted solution]

RAvi, however when trying to check-in the records, we need the validation to trigger to make sure they are entering the valid data right...so if I turn the validation to 'None' then I am bypassing the validations.

[Former Member]

Hi Kris,

No we have not come accross any issues in chec out & check in records even when we are using huge number of records. As you are aware Check out option will create a record in the temporary layer (not present in databse), will not be able to delete these records.

Regards,

Pramod