Element search returns nothing for an obvious concept
You're trying to find an ACRA element (e.g. IncomeTaxExpense) using the Mappings element-search box, and the dropdown shows zero results.
What this means
The search is filtered by entry point + statement section by default. The element exists in the taxonomy but doesn't match the current filter.
Causes
- Statement-section filter is wrong. You're searching from a line item flagged
balance_sheet, but the target element (e.g. an income-statement element) is in a different section. Either clear the section filter or fix the line item'sstatementfield. - Entry-point filter is over-restrictive. Some elements are common across entry points; some are exclusive to
FULL_XBRL. If your filing isSIMPLIFIED_XBRLthe search will hide full-only elements. - You typed an
elementIdthat doesn't exist in the pinnedtaxonomyVersion. ACRA element IDs usesg-as_,sg-dei_,sg-bp_,sg-fs_prefixes; verify yours is correct. - The pinned
taxonomyVersionis the wrong one for the period (e.g. filing pinned toacra_2026_v1but the period predates that taxonomy's effective date).
Diagnose
bash
# Verify the element exists in the constitution
grep -n '"sg-as_IncomeTaxExpense"' packages/xbrl/constitution/taxonomy_acra_2026_v1.jsonOr via Node REPL:
bash
node --experimental-repl-awaitjs
const xbrl = await import('@breezycorp/xbrl');
const lookup = new xbrl.TaxonomyLookup('acra_2026_v1');
lookup.byElementId('sg-as_IncomeTaxExpense');
// → element object or undefinedFix
- Clear the statement-section filter on the search box; search the whole taxonomy.
- Clear the entry-point filter; pick the right element; the filing's entry point will still be the pinned one (but you can verify the element is
applicable_entry_points-valid for that pin). - If the element genuinely doesn't exist in the pinned version, you may need to file against a newer taxonomy version — but that requires creating a new filing (pinned version is immutable).