Issue Summary: Dlist Becoming Readonly & Missing Field Values

Observed Behavior:

1. In various Dlists, users notice that:
   • The Dlist becomes readonly unexpectedly.
   • Many field values are not visible by default.
   • Fields are only revealed when clicking on the Dlist checkbox.

Root Cause Explanation:

1. Each Dlist has a special field called DLISTSAVE, which serves the following purposes:
   • Controls mandatory fields by configuring relation fields in the same Dlist.
   • If a related field is 0 or null, the system removes that Dlist line after saving.
   • If the "Save Required" option is set to Readonly for any relation field, it causes the entire Dlist to become readonly.

Performance Optimization Behavior:

1. To speed up data loading, the system:
   • Initially hides detailed field values in each Dlist line.
   • Only shows field-wise data after the checkbox is clicked for that line.
   • This is intentional for performance, especially in large Dlists.

Here is one eg. of Purchase Requisition Entries Getting Readonly and Details not fetching in fields like View and Date etc.

If clicked on checkbox of dlist details getting fetched.

Purchase Requisition Entries - DLISTSAVE field and its relation field - Quantity

Reason behind dlist getting readonly and not showing value in few fields is relation field used in DLISTSAVE is readonly.