Skuidward Tentacles (Raymond), Champion
-
18,336 Points
Posted 3 years ago
Skuidward Tentacles (Raymond), Champion
-
18,336 Points
I deleted each condition one by one to see if that would help. It did not. I deleted each agg field one by one. That didn't help. I deleted each grouping one by one. That didn't help. I removed the Having statement I injected into XML. That didn't help.
I have a condition based on a date field. I had that condition set to filterable default off. I changed it to filterable default on and set it to show records from last month. This fixed the issue. No errors. I want to see records from at least a year back so I set it to show records from the last 2 Years. Then I got a 404 error in the console on page load. So I set it to 1 year and the page worked again with no error. Out of curiosity, I set the condition to the last 365 days. That worked. Then I set it to the last 600 days. That gave me a 404 error.
So it seems in this agg model that is set to have no max records, if I try to query beyond 1 year back on page load. I get one of two errors. If I confine the query to within one year, the page works. If I set the page to not load data on page load, but then query it after page load, the page works regardless of how far back I query.
Long story, short, Records from 1 year back is sufficient for my needs upon page load, so this is not an urgent issue for me. Would be nice to know what is up. It is a relatively new object. There aren't more than a few thousand records.
Mark DeSimone, Official Rep
-
12,352 Points
Skuidward Tentacles (Raymond), Champion
-
18,336 Points
I'm not getting the User Context error now. I get the following:
On Screen Error:
null argument for JSONGenerator.writeString()
An unexpected error has occurred. Your solution provider has been notified. (System)
Console Error:
Failed to load resource: the server responded with a status of 404 (Not Found)
Again, if i set the model to not load data on page load, then query following page load with the condition completely turned off, it successfully queries all 1446 records without error.
Weird..
Mark DeSimone, Official Rep
-
12,352 Points
As a reminder, Salesforce does not allow reverting back to prior versions of managed packages. Skuid always recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment. We also recommend that you update out of date themes when you upgrade.
Skuidward Tentacles (Raymond), Champion
-
18,336 Points
Pat Vachon, Champion
-
45,310 Points
Skuidward Tentacles (Raymond), Champion
-
18,336 Points
Skuidward Tentacles (Raymond), Champion
-
18,336 Points
Unfortunately, the queries are exactly identical with or without load data on page load.
Pat Vachon, Champion
-
45,310 Points
Skuidward Tentacles (Raymond), Champion
-
18,336 Points
I did that for one of the two secondary models, but forgot for the other one. So, it was the fact that I had a condition on a secondary model that referenced an object field on an aggregate model instead of the alias that was causing the load data on page load issue. Weird....
Related Categories
-
Skuid on Salesforce
- 2745 Conversations
- 225 Followers