Troubleshoot the missing template-name message
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
The browser script requires a non-empty name when Save Filter Template is selected.
Where to goAdmin Area → Task Filters → Task Filters
Before you start
- Verify the module is active and use the exact navigation shown above.
- Use an account with the stated module and core CRM permissions.
- Use known test records when changing statuses, visibility, saved filters or global navigation.
What this guide helps you do
The browser script requires a non-empty name when Save Filter Template is selected. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Reproduce the behaviour with a controlled staff account and known task records.
- Enter a concise name within the visible 100-character form limit or clear the save checkbox.
- Refresh the page and compare the result with the core Tasks workspace.
- Record the outcome before changing permissions or module code.
Fields and options
Verified behaviourThe browser script requires a non-empty name when Save Filter Template is selected.
Rules and limits
- The browser script requires a non-empty name when Save Filter Template is selected.
Check it worked
- Troubleshoot the missing template-name message completes without a validation or permission error.
- The refreshed report, menu or saved-template page shows the expected state.
- A second authorised user sees only the records and navigation allowed by their core CRM permissions.
Security, privacy and operational checks
- Test changes with a non-production record or a controlled administrator account before wider rollout.
- Do not use navigation visibility as a substitute for core CRM record permissions.
Related guides
Was this guide useful?Your response is stored only in this browser.