Skip to main content
January 9, 2022
Solved

Record type Memory Limit

  • January 9, 2022
  • 6 replies
  • 0 views

I have this error message in the record  type, I tried to change the number of row per page but not worked

And the source data around 6500 raw.

Anyone know the solution?

Thank you

Best answer by mikes0011

By any chance is the entity here tied to a complex view?  I've had a few occasions in the past where a complex view can perform so badly that even relatively small queries start intermittently failing, especially as the table(s) the view is sourced from grow in total rows.  Often this can be resolved by troubleshooting the view definition itself to see if there are any inefficient joins or other operations that can be removed or simplified.

6 replies

stefanhelzle0001
Brainy
January 9, 2022

What kind of record is this? Synchronized? Entity backed? Cloud DB? Can you query data outside the grid?

January 10, 2022

record type list, not synchronized, azure database and I can query data from the record by using "queryRecordType" up to 5000 only

stefanhelzle0001
Brainy
January 10, 2022

If this works "sometimes", I would investigate any possible timeout or latency issues.

January 9, 2022

Seems it is Entity backed record.

May i know what is batch Size ? queryRecordType can not have more than 5000 and cannot -1 batchSize.

Can you check this first and if it is ok, can you please share more details?

January 10, 2022

I'm using the record directly in the site, I tried to minimize the rows per each page but I get the same error. 

sometime the record it's working but when refresh the page have the same error.

mikes0011
mikes0011Answer
Brainy
January 10, 2022

By any chance is the entity here tied to a complex view?  I've had a few occasions in the past where a complex view can perform so badly that even relatively small queries start intermittently failing, especially as the table(s) the view is sourced from grow in total rows.  Often this can be resolved by troubleshooting the view definition itself to see if there are any inefficient joins or other operations that can be removed or simplified.

The Expression Guru