BI Dashboards
From a quick chart in the chat to a standing management dashboard over your live ERP.net data.
"How are we doing?" is the question every ERP.net company asks daily — turnover this month, open orders, top customers, stock levels. Operator covers both ends of that need: a one-off answer drawn as a dashboard right in the conversation, and a persistent dashboard app you can open any time or hand to the whole team.
Two shapes, one request
A dashboard in the answer. Ask a question whose answer is numbers — "turnover by month this year", "top 10 customers by revenue" — and the agent replies with KPI cards, charts, and a compact table right below its written summary. Nothing to build, nothing to save; ideal for the question you have now.
A dashboard app. When the same numbers matter every day, Operator builds a small app: revenue tiles, trend charts, breakdowns by customer or product, refreshed from live ERP.net data every time it opens. It can live in your Web Client menu, be shared with the team, or even be public.
Example
A sales manager asks every morning for yesterday's numbers. You say: "build me a sales dashboard — today's and this month's turnover, open orders, and top 5 customers." Operator queries your instance, builds the app, and offers to place it in the Web Client main menu. The next morning the manager just opens it.
How to ask for one
Say what you want to watch, in your own words:
build me a dashboard with monthly turnover and open sales orders for this year
I need a management cockpit — revenue, receivables, and top customers, refreshed on open
make a stock overview app showing slow movers and items below minimum
Useful things to mention:
- The KPIs that matter — turnover, margin, order count, overdue receivables, stock value.
- The breakdowns — by month, customer, product group, store, team.
- The period — this month, rolling 12 months, compared to last year.
- Who will use it — just you, the team in your instance, or a public page.
What to check before approving
- The figures come from real queries. Every number on the dashboard is read from your instance when the app opens — check a couple against a known report once.
- The filters match your business. If "revenue" should exclude a document type or a specific store, say so while designing.
- Permissions. Each viewer sees only what their ERP.net access allows — verify with a colleague who has narrower rights before rolling it out broadly.
Putting it where people work
When the dashboard is ready, Operator fills in its place on the app's Deploy tab — typically a Main menu entry in the Web Client (requires ERP.net 26.2 or later). Nothing reaches your instance until you press Deploy there. Once deployed, everyone in the instance gets the menu item, and the dashboard always opens on current data.
Good to know
- Start in the chat, upgrade to an app: a good in-chat dashboard is often the prototype — "turn this into an app I can open every morning" is a normal next step.
- In-chat dashboards are a picture of one answer — no filters, no drill-down, no auto-refresh. The app form is the one for daily monitoring.
- Dashboard apps follow your theme and work on a phone, so the numbers are checkable from anywhere.
- Changing the dashboard later is a normal request: "add gross margin under turnover" produces a new version that replaces the old one wherever it is placed.