Hi All,
I am encountering the error mentioned in the subject whenever I try to open the summary of one of the requests.
In the record view, we have configured the following expression:
rule!summary_interface(record: rule!qry_record()).
Note: When I switched from rule!qry_record to rv!record, the error disappeared.
Initially, we suspected that the issue was caused by a large dataset. To address this, we reduced the query size to ensure it evaluates within 50ms. However, the error persists.
To investigate further, I opened the summary interface object and tested it by passing the query rule directly. When I clicked "Test Object," it loaded without any errors. However, when I opened an unnamed interface and invoked the interface using the expression:
rule!summary_interface(record: rule!qry_record()), the same error occurred.Also in error message , its specifically mentioned about one child interface which just shows grid data around 20 items. If i remove this interface from summary view, we are not getting error. Again here as well I tried to do object level test for that request and its loading without any error.
Did anyone face this issue?
Thanks,
Discussion posts and replies are publicly visible
Hi Vaishal ,Here the Issue is the Expression Rule you are returning taking much time to retrieve the data, inorder to ignore performance issues, you need to optimize the query by adding paging/limiting the data.You are also passing whole records from the previous sync into rule input of that rule as i see there is no identifier.You need to write a query rule while passing the rv!identifier as a rule input to that rule inorder to get only specific records.
rule!summary_interface(record: rule!qry_record(id: rv!identifier))
As per the error it looks like your grid containing chid rule might be causing this. Check the record configured to get data for the grid as well as the grid configurations. Without seeing the grid code, I can only guess that the record configured for grid data might be exceeding memory threshold intermittently.
Directly I dont see how the rule!qry_record() or rv!record impact this child interface. Anyway its best to use rv!record instead of querying the entire record.
For future maintenance check the grid rule and underlying code to identify if column selection, filters etc are performance effective or not.
Could you please share the content of the rule?
Have you checked that the expression rule is returning the expected data and the data is within the expected size and complexity?