Lazy loaded screens do not reset id’s that are requested by RowStates
API call.
On each master record change the child entity’s RowStates
calls request more and more rows instead of requesting just those rows that are currently loaded. This slows down the screen until it is unusable.
Example – only one record is present in the current session but the request is being called for all the previously loaded records as well:
{
"SessionFormIdentifier":"c18ab0b1-9aa6-4c45-b423-13be01526eeb",
"Entity":"ProjectEfficiency",
"Ids":[
"033a7f7c-8e8f-4e8d-85b0-fadfa1dc19a1",
"818db6af-0aa8-4104-85b0-fadfa1dc19a1",
"723b3a77-7ba2-4511-85b0-fadfa1dc19a1",
"46efdd4e-8033-4509-85b0-fadfa1dc19a1",
"86f91c3d-1779-402c-85b0-fadfa1dc19a1",
"8275b1e5-0a5f-46cc-85b0-fadfa1dc19a1",
"036f199c-6bd7-4f87-85b0-fadfa1dc19a1"
]
}
Note: Since most of the requested records are not available in the screen’s session anymore, they are being loaded from the database, which makes it even slower.