AccountedPro - Limits and troubleshooting
The limits, with their reasons
| Limit | Value | Why |
|---|---|---|
| Drill-down depth | 10 links | Each level is one query; past that it is a report, not a list. |
| Fields in a tab's order | 4 | Read left to right; past a handful nobody can say what the order is. |
| Sorting by a linked field | first 5,000 matching records | A list query cannot join, and the framework refuses functions in an order clause, so the order is worked out separately. Plain fields have no such limit. |
| Related records scanned | up to 20,000 per page of rows | Applies when a related block compares against each row. |
| Rows shown by a related block | 100 | The count above them is the true total. |
| Names carried by a resolved filter | 5,000 | An OR/NOT/hop condition resolves to a name list; past this it stops being a filter and starts being a table scan. |
When a cap is reached the app says so rather than quietly truncating — the sort response reports that it was capped, and the builder states the number under the setting.
When something is not right
The list looks like an ordinary Frappe list
Two switches, both required:
- Enable Advanced Listview ticked in Advanced Listview Settings.
- The DocType listed under Governed DocTypes.
Then reload the Desk — the governed list is read when the Desk boots, so a change made in another tab will not apply until then.
A change in the builder has not appeared
The header says Unsaved changes until you save; from Customize Form the save is its Update button. After a deploy, JavaScript and CSS changes also need bench build and a hard refresh (⌘⇧R / Ctrl⇧R) — the browser caches the old bundle otherwise.
A tab's count and its rows disagree
Counts respect permissions, so a badge counts only records the reader can open. If the numbers differ between two people, compare what each is allowed to read.
A filter on a child-table field errors or finds nothing
Write it as the child DocType and the field — Sales Order Item.item_code — rather than the field alone. Frappe joins the child table when the filter names it; without the name it looks for the column on the parent, which does not have it.
Following a link from Connections does not filter the list
Fixed in August 2026. The layout name was being written into the URL before the incoming filters were read, and the filters lost. If it still happens, the site is on an older build: rebuild assets and hard-refresh.
A condition disappears while it is being built
Also fixed in August 2026. A half-built condition — which is exactly the state you are in the moment you walk into a Link, because the field on the far side has not been chosen yet — was dropped when the panel refreshed. Same remedy.
Group dividers are in a strange order
They used to come back biggest-group-first. Set Theme → Group headers → Order the groups to By what they group, which is now the default for new layouts.
Something is slow
Read what the condition preview says it costs. No extra lookups means the database answered on its own; each extra lookup is another query. The usual causes are drilling through several links on a large list, a related block comparing against each row, or an auto-refresh set too short.
A Server Script list shows the wrong rows
The script decides what it returns; the app does not filter afterwards and cannot. Check the script's own permission handling. See Data sources.
A colour rule never fires
Rules are read top to bottom and the first match wins — a broad rule above a specific one will swallow it. A rule with no condition is the fallback and belongs last.
An element is missing for some people
Check Show this only when… on the element, its column, and the tab. All three gate independently, and an element hidden by any of them is not rendered at all.
Getting back to stock behaviour
Untick Enable Advanced Listview. Every list returns to Frappe's own immediately, and nothing is lost — layouts, saved views and settings are all still there when it is switched back on. Removing one DocType from Governed DocTypes does the same for that one list.
That switch exists precisely so a Frappe upgrade that breaks something is a tickbox rather than an incident.
Reporting a problem
Worth including:
- the DocType and the layout name;
- what you expected and what you saw;
- whether it happens on the first visit to the list or only after navigating — several past bugs happened only on a cold page load, and knowing that narrowed each of them in minutes;
- whether it happens for one person or everyone (that separates permissions from behaviour);
- the browser console if there is an error in it.