DLR Locking

2 Minutes to read

Print
Dark
Light
PDF

Article summary

Did you find this summary helpful?

Thank you for your feedback

When two or more users simultaneously access the same DLR. For example, when the first user is accessing the DLR, a second user cannot execute the same DLR before the first user finishes the execution. A DLR lock is applied on the DLR when a user starts executing the DLR, and the lock is released after the first user finishes execution. Other users cannot execute the DLR during that time period, and a lock error message is shown to the second user. This avoids any concurrency issues that may occur when multiple users are accessing the same DLR simultaneously.

DLR Locking behavior:

In the current application setup, the data loads happen through Sync and Async loading process, and the DLR can be accessed in three different ways:

SOAP APIs
REST APIs
Through UI

DLR locking is always applicable for Sync loads. However, for Async loads, certain scenarios have DLR locking relaxation. Here is the list of DLRs that are exempted from DLR locking during Async loads:

Note
These Async loads use a temp CSV file as staging during data loads.

DLR Name	Soap	REST	UI
GL	The lock is relaxed if the Horizon flag is enabled.	The lock is relaxed if the Horizon flag is enabled.	The lock is only relaxed if the Horizon flag is enabled and the file is uploaded on the last step.
Translations	The lock is relaxed if the Horizon flag is enabled.	The lock is relaxed if the Horizon flag is enabled.	The lock is only relaxed if the Horizon flag is enabled and the file is uploaded on the last step.
Employee Allocations	The lock is relaxed if the Horizon flag is enabled.	N/A	The lock is only relaxed if the Horizon flag is enabled and the file is uploaded on the last step.
Employee Compensations	The lock is relaxed if the Horizon flag is enabled.	N/A	The lock is only relaxed if the Horizon flag is enabled and the file is uploaded on the last step.
Segment Hierarchy (Common CCOA)	If Alternate Hierarchy is selected, the locking is relaxed. If Main Hierarchy is selected, the locking is relaxed if the Horizon flag is on	N/A	The locking is relaxed if Alternate Hierarchy is selected, and the file is uploaded on the last step. The locking is relaxed if Main Hierarchy is selected, the Horizon flag is enabled, and the file is uploaded on the last step

Note

When the DLR is locked and the second user tries to access the DLR from the UI, all the UI elements of that DLR will be disabled, and the options in the DLR will be read-only. The second user cannot change the DLR definition, and the user is notified about the same while navigating through the DLR steps.

Was this article helpful?

What's Next

Overview and Cheat Sheet