When you've spent years working inside an ERP system, you develop an instinct for where data lives. You know which tables feed which reports, which fields drive which business logic, and — perhaps most importantly — you know exactly where to look when something doesn't add up.
For over a decade, my ERP world was JD Edwards. Before moving into the Business Central ecosystem, I worked across JDE implementations covering finance, distribution, manufacturing, and supply chain. Whether I was troubleshooting a pricing issue in the F4211 Sales Order Detail table, tracing a GL posting back through the F0911 Account Ledger, or mapping out a data migration from an older system, the process always started the same way: understand the schema.
The Tool That Spoiled Me
In the JD Edwards world, there's a tool called ERPRef.com that I used constantly. It's a straightforward schema browser — all 5,097 JDE tables laid out by system code, with columns, indices, data types, and descriptions. Need to know what fields exist on the F0101 Address Book Master? Two clicks. Want to see every table in the Accounts Payable module? It's all there.
It's not flashy. It doesn't have a query builder or data export. But as a reference tool for understanding the data model, it's invaluable. During implementations, I'd have it open in a tab all day. During data migrations, it was the first place I'd go to map source fields to target fields. During troubleshooting, it was faster than digging through the JDE object browser.
When I made the move to Microsoft Dynamics 365 Business Central, one of the first things I did was look for an equivalent. Something that would give me a clean, browseable view of every BC table, every field, every relation — without needing to fire up Visual Studio or install an AL development environment.
What I Found (and What Was Missing)
Business Central has some built-in tools. The Page Inspection feature lets you see which table backs a specific page. The AL Language extension for VS Code gives you IntelliSense on table objects. Microsoft's documentation lists standard tables and fields, but it's scattered across hundreds of pages and often out of date for newer extensions.
There are also Chrome extensions that help you open the table browser in BC — but they require you to be logged into a BC environment, and they only show you one table at a time with raw field names and no context about relations or field classes.
What I couldn't find was a single place where I could:
- Browse every table in BC with record counts, categories, and field counts
- See full field details — data types, primary keys, FlowFields, and table relations
- Navigate between related tables — click a relation and land on the target table
- Find where a field is used across the entire schema (cross-reference)
- Run ad-hoc queries with field selection and BC filter syntax
- Export the results as CSV or Excel for analysis
None of that existed in one tool. Each piece was available somewhere — in VS Code, in the BC web client, in Microsoft Docs — but never together, and never without significant setup.
Building What I Actually Needed
So I built it. XPT Data Explorer started as a tool for my own use during Business Central implementations. I approached it with a simple question: if I could design the perfect data exploration tool for a BC consultant, what would it look like?
The answer came from thinking about the three hats I wear during any ERP project:
The Consultant's Perspective
During fit-gap analysis and requirements gathering, I need to quickly understand what data is available. Which tables hold customer credit limits? Where are the posting group configurations? What's the relationship between a Sales Header and its Lines? A consultant needs to browse and discover — to understand the shape of the data before writing a single line of code.
That's why the Schema Explorer exists. Every one of the 2,000+ BC tables is browseable with full field details, and you can navigate relationships by clicking through table relations. It's the ERPRef equivalent for Business Central.
The Analyst's Perspective
During data migration, reconciliation, or issue investigation, I need to query real data — not just look at field definitions. I need to say "show me all customers where the posting group is DOMESTIC and the balance is not zero" and get results I can export.
BC's built-in filtering is powerful but hidden behind clunky page interfaces. The Query Builder exposes those same BC filters in a clean UI — select your fields, add your filters using standard BC syntax (ranges, wildcards, multiple values), and get results in seconds. Export to CSV or Excel for further analysis.
The Developer's Perspective
When writing AL extensions, I constantly need to check field numbers, data types, and table relations. Is field 32 on the Item table a FlowField? What's the CalcFormula? Which tables reference the Customer table's No. field?
The Field Cross-Reference answers that last question instantly — click any field and see every other table in BC that references it. During development, this saves hours of searching through AL source code or documentation.
Why a Free Schema Browser Matters
One decision I made early on was to make the schema browsing completely free. No account needed. Open dx.xpt.tools and start browsing — all 2,000+ tables, all fields, all relations, all cross-references.
The reasoning is simple: a schema reference tool should be available to everyone working with BC. Consultants doing presales estimates, developers evaluating whether to customise or configure, analysts mapping data for migration — they all need quick access to the BC data model, and they shouldn't need a paid subscription or a development environment to get it.
The Cronus demo environment is included free so you can run queries against realistic data, see actual record counts, and understand how tables are populated in a standard BC installation.
What's Different About the BC Data Model
If you're coming from another ERP like JD Edwards, SAP, or Oracle, there are some things about BC's data model that will surprise you:
FlowFields are unique to BC. A FlowField is a calculated field that doesn't physically store data — instead, BC computes its value on the fly by aggregating records from related tables. The "Inventory" field on the Item table, for example, is a FlowField that sums Item Ledger Entries. Understanding which fields are FlowFields (and which are Normal) is critical when writing queries or building reports, because FlowFields add processing time proportional to the number of records.
Table Relations in BC are defined at the field level, not the table level. This means a single table can have dozens of relations pointing to different tables — and tracing those relations is how you navigate the data model. The Schema Explorer makes this visual by showing outbound relations (tables this table points to) and inbound references (tables that point to this table).
The table numbering system tells you a lot. Tables 1-49999 are standard Microsoft objects, 50000-99999 are the legacy custom range, and anything above 100000 is typically an extension. When you see a table like 5802 (Value Entry), the 58xx range tells you it's in the Costing & Inventory Valuation area.
What's Next
XPT Data Explorer is already useful for browsing schemas, running queries, and exporting data. But there's more coming:
- Saved Views — store your most-used queries and re-run them with a click
- Data diff across environments — compare sandbox and production data side by side
- Scheduled exports — automated daily or weekly data pulls sent to your inbox
If you're a BC consultant, developer, or analyst who spends time digging through data, give it a try. The schema browser and demo queries are completely free.
And if you're coming from JD Edwards — welcome to Business Central. The data model is different, but the instinct for where data lives is the same. You just need the right tool to explore it.
Mike Tawn is the founder of Xpertly Ltd and the creator of XPT Data Explorer. With over two decades of ERP experience spanning JD Edwards and Microsoft Dynamics 365 Business Central, he builds tools for the people who actually work with ERP data every day.