Attach files by business key
Create, read and update attachments on orders, invoices, receipts, production and quality orders and more, by the keys your document system already holds.
Products / Lattice / Data entities
data entitiesThe data entities Finance & Operations should have shipped.
132 purpose-built OData data entities fill the gaps in the standard catalog: attachments by business key, writable contacts, intercompany visibility, trade agreements, finance transactions and lean, change-tracked feeds built for real volume.
132
data entities, OData and data management
Business keys
not internal record ids, for attachments and contacts
Delta-ready
feeds export only what changed
The problem
Every Finance & Operations analytics or integration effort hits the same wall: data you can see on a page but cannot cleanly export, entities that are read-only where you need to write, and standard entities that crawl under real volume. Teams hand-build entities to get around it, then rebuild them when an update changes the tables underneath. The data layer ends up on the critical path of every project, and on the maintenance list forever.
How Lattice answers it
Lattice fills those gaps with entities that already exist, already perform, and are maintained across releases. Attachments can be created, read, updated and deleted by the business key you already have, such as a sales order and its invoice number, including on posted documents, without ever looking up an internal record id. Customer and vendor contacts are writable by account number alone. Intercompany orders come pre-filtered with the linkage you need to reconcile them.
Beyond the gaps, Lattice covers the data integrations keep asking for: sales and purchase trade agreements of every kind, general ledger entries, the trial balance, tax and withholding tax, customer and vendor transactions and settlements, warehouse work and reservations, open order lines, planned order requirements, posted project transactions and the period close calendar.
The high-volume feeds are engineered rather than accidental. They select only the fields they map, skip write and validation work where they are read-only, filter in the query so consumers receive smaller results, key on the source index so paging stays fast at any depth, and are ready for change tracking, so data management and data lake exports can run as incremental deltas instead of full snapshots.
Lattice also helps you use the data. The OData metadata explorer browses the surface and generates a Postman collection or an OpenAPI specification to hand to an integrator. The coverage analysis shows which tables already have an entity. Any entity can be exported as an Excel template describing its fields, types, keys and allowed values, and the wide Excel export handles entities with more than 255 fields, which the standard export cannot. And integration configuration can be captured to source control and applied again on any environment, safely, as often as you like.
What you get
Data in and out, without the hand-built layer.
What is in the box
The entity catalog, by area.
Every entity is available over OData, and through data management for import, export and data lake jobs.
Documents and attachments 6
- Sales confirmations, packing slips and invoices
- Purchase confirmations, receipts lists, product receipts, invoices and order lines
- Customers, vendors and free text invoices
- Production orders, quality orders and projects
- Transfer orders and lines
- A general-purpose attachment entity for any table
Customers, vendors and contacts 3
- Customer and vendor contact details (phone, email, URL)
- Customer and vendor contact people
- Customer packing slip journals, lines and line history
Orders and intercompany 5
- Sales and purchase order lines with site and warehouse
- Open sales and purchase order lines
- Intercompany sales and purchase orders and lines
- Sales order line charges
- Opportunities and project estimates
Trade agreements 3
- Sales and purchase price agreements
- Line, multiline and total discount agreements, sales and purchase
- Trade agreement journals
Finance and tax 6
- General ledger entries and the trial balance
- Tax and withholding tax transactions
- Customer and vendor transactions and settlements
- Bank account and fixed asset transactions
- Payment requests and lines
- Period close calendar, roles, resources and task areas
Inventory, product and warehouse 5
- High-performance on-hand and released-product feeds
- Inventory transactions and planned order requirements
- Warehouse work, work lines, reservations and location types
- Mobile device steps and texts
- Item group, model group, order setup and tax assignments
Projects, production and retail 4
- Posted project transactions
- Production journal headers
- Retail transactions
- Worker actions
Cross-reference keys 3
- External system keys for customers, vendors, products, variants and batches
- Keys for sales, return, purchase and transfer orders and their lines
- Keys for quotations, agreements, requisitions, journals, projects, fixed assets, BOMs and routes
Integration monitoring and setup 5
- Service call log and statistics, idempotency log and dead-letter queue
- Asynchronous operation tracking and file ingestion log
- Recurring data jobs and table-to-entity coverage
- Excel templates for any entity, and a wide export past 255 fields
- Sales, procurement, inventory, ledger and receivables parameters
Questions
What buyers ask.
Do these replace the standard entities?
No. They sit alongside Microsoft's catalog and fill what it leaves out. Your existing entities, data projects and integrations keep working exactly as they do.
Can we use them with data management and our data lake?
Yes. Every entity works over OData and through data management. The high-volume feeds are ready for change tracking, so recurring exports can send only what changed.
What about performance on large tables?
The feeds built for volume select only the fields they need, filter in the query and page on the source index. Follow the server's paging links and they stay fast at any depth.
Will they survive Finance & Operations updates?
They are built the standard way and maintained across every release, so an update does not mean rebuilding your data layer. After an update that changes staging tables, a single refresh brings the picture current.
Try it
See it in your own sandbox.
Lattice is one package: every capability on these pages comes with it. Run it free in any non-production environment for as long as you like, and subscribe only when it goes to production.