Hi everyone,we have a database of 3/4 tables, which we have connected via record type relationships.
There is an interface as a user input task of a process.
It shows a list of elements of the primary table, it has 9 columns, some columns are field of the record type, some columns show the details of the related record types.
After scrolling through the first 50 pages (therefore arriving at 500 items) the Memory Circuit Breaker error appears on the screen.
Am I doing something wrong? Is it possible that record type paging doesn't manage memory allocation?
Thanks,
Dalila
Discussion posts and replies are publicly visible
Can you elaborate more on following.
>>There is an interface within a process that shows a list of elements of a table, some columns show the details relating to the related record types.
Hello Dalila Virgolino
Are you using any variables containing expression rules and paging to handle the data in the grid or is it from the recordData(). Is there any reason that you have a grid with record details and related record details of 100's in a interface that is being used in the UIT. Are you trying to let the user select the rows or something?I would say get rid of fetching so much data at least the related record data unless it is crucial information to show for the user.
My suggestion would be use a custom paging to handle the amount of data that is being preloaded. Unless the user wants to see more of the details do not pre-fetch or load the data.
Below are few reasons why it would happen
Designing memory-efficient expressions
Not sure if I will be helpful for providing you an accurate answer, but very curious why hundreds of record data in a user input task.
You need to make sure to only query the data you really need. Can you share the relevant code snippets?
What happens if you artificially set your StartIndex to, like, 475 (instead of 1) and page forward 3 or 4 pages? Does the same error occur then? This is the first troubleshooting step I'd recommend just to try and gauge whether the behavior is more related to on-form behavor or more related to a specific query at a specific data range.
Also, as others have said, it would be very helpful if you could share here the method by which you're querying the data to populate your grid.
Hi Konduru Chaitanya ,the data within the grid is loaded via a!recordData and is not saved within any local! or ri!.The related record fields are shown in the table as they are useful for the user to choose whether or not to select a row.
The only interface variable is an array that contains all the elements (number ids) selected by the user.
Hi ,I noticed that in 23.4, a!recordData has the field fields, while in 23.2 it doesn't (we are in an on-premise environment).
Do you think the new parameter can minimize the data obtained with the query?
https://docs.appian.com/suite/help/23.2/fnc_system_recorddata.html
docs.appian.com/.../fnc_system_recorddata.html
Hm ... hard to say what is going on. Can you try to do it old-style, using a local variable to fetch the data? Then you have more control with a!queryRecordType().