Auto-cache the default query for dropdown population against static entities

By Justin James on 16 Nov 2014
Use case:

* Have a drop down bound to a Static Entity ID.
* Do not specify a "Source Record List".

Result:

* The system queries the Static Entity by default.

Suggested change: those queries should be cached, they are not going to change unless a new version is deployed, which clears the caches anyways.

Why: When the dropdown occurs multiple times on a screen (like inside a ListRecords) it gets run multiple times even though it is impossible for it to ever return a different result set. On one of our slow screens, the default queries for 2 dropdowns represented 25% of the connections to the DB.

J.Ja
This idea has no comments yet. Be the first to comment!