Excel on Steroids: How PrismView Replaces SmartLists and Exports

Ask a distribution controller how they built last month's margin-by-customer numbers and the answer is usually a sequence rather than a system: run a SmartList, export to Excel, paste a second export beside it, write a VLOOKUP, filter, subtotal, save the file into a folder that four other people also save files into. It works. It has worked for years. It is also the most reliable source of stale numbers in the business.

Microsoft Dynamics GP is a capable accounting and distribution platform — more than 100,000 companies worldwide run it — but its native inquiry tools were built for an era in which the answer to "I need to see this data a different way" was "export it." Centerprism's PrismView™ exists to answer that question inside the ERP instead of outside it.

The export habit is a symptom, not a workflow

An export is not free. It looks free because nobody bills for it, but every time a number leaves the ERP it acquires four problems at once.

• It stops being true immediately. The moment the file is created it is a photograph of a moving business. Orders ship, credits post, receipts land, and the spreadsheet does not know.
• Only one person can reproduce it. The filter choices, the hidden column, the row someone deleted because it "looked wrong" — none of that is written down. When that person is on holiday, the report is on holiday.
• The business logic ends up in a cell. How you define a returnable line, an intercompany transfer, a rebate-eligible sale: if that definition lives in column M of a workbook, it is not a company policy, it is a personal habit.
• It leaves the perimeter. Costs, margins and customer lists that are permission-controlled inside the ERP become an unprotected file on a laptop, an email attachment, and eventually an attachment forwarded to someone who left last year.

None of this means Excel is bad. Excel is excellent at modelling, scenarios and one-off maths. The smell is not Excel — it is the routine, recurring export: the same extract, run the same way, by the same person, every Monday. A recurring export is an unmet requirement wearing a disguise.

What PrismView actually is

PrismView is a high-performance data grid and business intelligence layer that reads the live Dynamics GP SQL database directly. It is not a warehouse, not a nightly cube and not a copy. It queries the same tables that order entry, purchasing and the general ledger write to, which is why the people who use it describe it in operational terms rather than reporting terms — they are not "running a report," they are looking at the business.

"PrismView is like Excel on steroids. I can't believe what an amazing tool it is. I can't wait to start using it in our organization." — Marty Machnik, Centerprism client

Because Centerprism's wholesale distribution modules all sit on that one GP database — the same records, not a federation of bolt-ons — a PrismView grid can reach across module boundaries without anyone building an interface first. Sales history, inventory positions, purchase receipts and customer records are all just tables in the same place. There is a full PrismView & business intelligence overview on this site, and the PrismView datasheet (PDF) lists the components in detail.

The components that replace a SmartList

PrismView is not one feature. It is a small set of named tools that between them cover almost everything a recurring export was doing.

PrismGroup™ — grouping instead of pivoting

PrismGroup lets a user drag and drop multi-hierarchical grouping onto any column in any data view. Grouping is unlimited, expand and contract is one click, and the result is a tree-like view you can compare side by side. In practice that means a sales manager can group order lines by salesperson, then by customer, then by item class, collapse the whole thing to see the shape of the month, and open only the branch that looks wrong — without building a pivot table, and without the pivot going stale five minutes later.

Field Chooser™ — the VLOOKUP, retired

Field Chooser is the component that kills the two-tab workbook. It lets a user drag and drop virtually any field from any SQL table into any PrismView grid, and combine multiple data tables from different modules into a single grid. Columns can be pre-set and ordered, and the customised grid can be saved per user. The join that used to be a VLOOKUP between two exports becomes a column you added once and never think about again.

Prism Filter™ and Prism Summaries™

Prism Filter narrows a grid to the rows that matter; Prism Summaries totals what is left. Between them they cover the two things people actually do in Excel after an export — slice, then subtotal — except the slicing and the totalling now happen against live data and can be saved as part of the view.

PrismEdit™

PrismEdit is the piece that turns a grid from something you read into something you work in. Once a view is the place your team already looks, being able to act from that view rather than re-navigating to a maintenance window is what closes the loop.

Live data versus a snapshot

This is the architectural point, and it is worth being blunt about it: an export is a snapshot taken the moment it is created; a PrismView inquiry is a question asked now. Everything else follows from that difference.

Consider a Tuesday morning stock call. Purchasing has a reorder worksheet exported Friday afternoon. Customer service has an availability list pulled Monday. Sales has a backorder report from this morning. All three are defensible, all three were correct when they were made, and all three disagree — so the first twenty minutes of the meeting go on establishing whose numbers to trust rather than on what to buy. Multiply that by every operational meeting in a week and the cost of snapshots stops being theoretical.

When inquiries read the live database, that argument does not happen. It is also why live visibility is worth more in distribution than in most industries: your stock position, your open orders and your inbound receipts all change hourly, and decisions made against Friday's picture are being made against a business that no longer exists. The same logic underpins inventory management and order management in the Centerprism suite.

A worked example: chasing a PO invoice

Here is the workflow that comes up most often, because it is unglamorous and constant. A supplier statement arrives. One line does not tie out. Someone in accounts payable has to establish what was ordered, what was received, what was invoiced, and at what price.

The export version: run a SmartList of purchase orders, export. Run a second list of receipts, export. Run a third of payables transactions, export. Line the three up in a workbook, match on PO number, discover the receipt was posted against a different line, re-run one of the extracts, and eventually reach an answer twenty-five minutes later that nobody will be able to reproduce next month.

The grid version: open the saved view that already carries PO number, vendor, item, quantity ordered, quantity received, invoice number and unit cost — columns assembled once with Field Chooser from the purchasing and payables tables. Filter to the vendor. Group by PO. The discrepancy is visible without a single export, and the same view works for the next statement, and for the buyer who wants to check a lead time, and for the manager who wants to see the vendor's whole month.

"Your company has saved me a ton of time looking up PO invoices. PrismView is way easier than using Smartlist in GP." — Ginny Russell, Centerprism client

Nothing about that is exotic. It is the same data GP already holds; the difference is that the assembly work happened once, inside the system, instead of every time, outside it. You can read more from customers on the Centerprism testimonials page, and the equivalent detail for buying and receiving lives under purchasing management.

One version of the truth

The practical benefit is not "better reporting." It is that fewer stale spreadsheets circulate through the business, so fewer decisions get made against numbers that were true last week.

You notice it in specific places. Pricing is one: when the margin a salesperson sees on screen is the margin the finance team sees, discount conversations become shorter and better, which is exactly the point of a governed pricing management process. Month-end is another: reconciliation time shrinks when there is nothing to reconcile between, because everyone was looking at the same tables all along. And onboarding is a third — a new analyst inherits a set of saved views rather than a folder of workbooks and a verbal explanation of which one is current.

There is also a quieter benefit. When people can answer their own questions, they ask more of them. The queue of "can you pull me a list of…" requests that lands on the one person who knows SmartList well is, in most distributors, a real constraint on how curious the rest of the company is allowed to be.

How to tell whether this applies to you

You do not need an assessment project to work this out. Ask around your own team for a week and count:

• How many recurring exports run on a fixed schedule — daily, weekly, at month-end — and who owns each one.
• How many of those exports get combined with a second export before anyone can use them.
• How many decisions this month were delayed because two people had different numbers.
• How many spreadsheets containing customer cost or margin data exist outside the ERP, and on how many devices.
• What would break next Monday if the person who owns the biggest export left tomorrow.

If those answers are uncomfortable, the fix is not more discipline about file naming. It is moving the assembly work back inside the system. Start with the single export that costs the most time, rebuild it once as a saved grid, and see whether anyone asks for the spreadsheet again.

The Centerprism datasheet library covers PrismView and the rest of the module set, and if you would rather see a grid built live against distribution data than read about one, request a demo and bring your worst recurring export with you.