A user who manually fills out the same five fields every morning to find pending invoices loses half an hour. The day is spent mostly on the list, not the form.
The right filter and saved view ensure access to the correct record in seconds. In this article, we covered search, multi-filtering, column layout, and sharing.
EQLEM is a solution platform; while it accelerates operations with a standard list experience, it does not replace your existing ERP system.
Table of Contents
Why is the list critical?
The user spends most of the day searching for records; the form is only a brief stop. A slow list means slow operations.
A good filter also increases decision quality; work is done on the right subset. The wrong subset produces incorrect approvals.
The list is the complement of standard document entry. Standard document entry must speak the same language as.
Finishing daily work with a list instead of a report is faster for most teams. Heavy reports are not needed for every task.
Filter discipline is reinforced with training; the tool alone is not enough. A short internal guide accelerates new personnel in their first week.
Quick search
Code, title, and document number should be searchable from a single box; the user should not have to think about which field to select. Simple search is the first door.
Results update as you type and are sorted by relevance. When there are no results, hints on what to try next should be provided.
Including fields like barcode and serial number in the search speeds up fieldwork.Warranty inquiry connects to this.
Search history can be kept personal; frequently viewed records remain just a click away.
Indexes must be up to date for performance; a slow search makes filters useless. If a user abandons a slow screen once, they never return.
Multi-filter
Date range, status, branch, and user should be applicable together. A single filter rarely solves the job.
Active filters appear like chips and are removed with a single click. A hidden filter produces incorrect results.
AND / OR logic must be clear; ambiguous combinations break trust. Defaulting to AND fits most scenarios.
Blank field filters are also needed; such as "cost center is empty." This is how missing data cleanup is done.
Save preset filters to catch row errors; row errors see the post.
Saved views
Filters set up every morning should be saved and opened by name. Repeated setup is a waste of time.
A default view can be assigned by role; an approver sees the approval queue upon opening. This generates discipline.
The number of views should not bloat; more than ten records makes selection difficult. Perform periodic cleanups.
View names must be in business language; "Filter 3" means nothing to anyone. Meaningful names are essential.
Personal and shared views must be separated; mixing them creates authorization risks. Shared sets protect team standards, while personal sets are for fine-tuning.
Column layout
Visible columns should be chosen based on the task; unnecessary columns increase scrolling. Fewer and more meaningful columns are faster.
Sorting and pinning must be supported; amount or date can always stay on the left. Fixed columns make reading easier.
If density indicators are color-coded in the status column, priorities become visible. Also use icons for color blindness.
Column preferences are saved per user; they do not need to be reconfigured every session. This small detail saves a lot of time.
The same set of columns can be used in exports, increasing report consistency. Excel files generated with different columns create discussions in meetings.
Sharing with the team
When a good view is shared with the team, everyone speaks the same language. Individual filters produce messy operations.
Sharing permission must be controlled; not everyone can modify every view. The owner role is clarified.
Opening views via links works well in meetings; everyone looks at the same set. Screen sharing is not needed.
When combined with notifications, queue clearance accelerates. Notification management refer to the article.
When a shared view changes, a short note should be left for the team.
Scope and authorization
Filters cannot exceed the authorization scope; a user cannot find a record they should not see using a filter. Security applies to the list as well.
Branch and warehouse scope is applied automatically. Branch and warehouse scope refer to the article.
Role-based authorization can also manage column hiding in the list. Role-based authorization refer to the article.
Export must be tied to a separate permission; not everyone who sees the list should be able to get an Excel file.
Authorization violation attempts are logged; an audit trail is maintained.
Mobile usage
On mobile, you should work with fewer columns and saved views; complex filters are exhausting on small screens. Simplicity is speed.
For the field team, a ready-made "today's visits" view is sufficient. Field mobile refer to the article.
Offline search may be limited; critical views are cached. Expectations must be managed clearly.
The mobile dashboard and the list complement each other.Mobile dashboard check out the article.
Touch sorting is prone to misclicks; approved views are preferred. In field tempo, a ready view is always superior to manually set filters.
Practical scenarios
Approval queue: today + pending + my branch view should be the first screen of the morning. This trio cuts most delays.
SLA risk: expiring soon + open requests filter protects the service.SLA targets check out the article.
Stock risk: below critical level + fast-moving products filter feeds purchasing. A daily overview is sufficient.
Error hunting: zero price or excessive discount filter is quality control. Tie it to a weekly routine.
List views can be aligned with the executive KPI set;daily KPI check out the article.
Points to consider
Don't forget the hidden filter; deciding in the wrong cluster is costly. Active filters should always be visible.
Don't fall into view inflation; fewer and shared sets are better. Avoid multiplying personal copies.
Don't position EQLEM as an ERP; the list experience speeds up operations, it doesn't change the financial center.
Do not leave export unauthorized; list data can be sensitive.
Adding a new filter to a slow list is not enough; index and scope must also be reviewed.
Frequently asked questions
Is the saved view mandatory for every user?
It is not mandatory, but assigning a default by role increases efficiency. Opening to a blank screen wastes time every morning.
Can a filter exceed authorization?
It cannot; scope is always superior. The filter only works within the authorized set.
Does EQLEM replace the existing ERP?
No; it works alongside it as a solution platform and accelerates operations through the list experience.
How many saved views are sufficient?
Three to seven per role is usually enough. Any more than that slows down selection.
The day is spent in the list; the right filter speeds up the right decision. Filling out the same field every morning is a waste.
Bind saved views to the role and keep active filters visible. Hidden filters produce wrong decisions.
Simplify columns and share good views with the team. Individual clutter slows down operations.
Keep the scope of authorization above the list; lock down data export separately.
Work with fewer columns and ready-made views on mobile; leave complex filtering for the desk.
By consulting with the EQLEM team, you can clarify your list and saved view configuration.