Lattice Scenarios

Task-oriented, end-to-end walkthroughs of a single business outcome. Where the reference docs answer "what is this object and what does it do?", these answer "I need to achieve X: what do I do, in what order, and how do I know it worked?"

The reference set stays authoritative for detail; each scenario links down into it rather than repeating it.

Using Lattice end to end

Most customers follow the same path: connect an external system once, run their business processes through Lattice every day, and keep an eye on the integration. The scenarios below follow that path.

1. Get connected

Scenario	Outcome
Connect an integration client	Register your system in D365, give it the right roles, get a token and make the first call.
Use your own keys	Send your system's customer, order or item keys instead of D365 ids.

2. Run your business processes

Order to cash

Scenario	Outcome
Sales order to invoice	Capture a sales order, confirm it, post the packing slip and the invoice, and follow its status.
Cancel a sales packing slip	Take back a packing slip posted in error, so the order lines are open to deliver again.
Sales return to credit note	Create a customer return, receive the goods and post the credit note.
Free text invoice	Invoice a customer for something that is not an item, and cancel an invoice with a correcting one.
Customer payment and settlement	Post a customer payment and settle it against the invoice it pays, take a deposit against a sales order, and reverse a payment.
Sales prices and price inquiry	Push sales prices into trade agreements and ask what a customer pays for an item.

Procure to pay

Scenario	Outcome
Purchase requisition to purchase order	Request goods, get the request approved through workflow, and turn it into a purchase order.
Purchase order to invoice	Confirm a purchase order, receive the goods and post the vendor invoice.
Cancel a product receipt	Take back a product receipt posted in error, so the order lines are open to receive again.
Purchase order prepayment	Post the vendor's prepayment invoice for a purchase order before the goods arrive.
Post a pending vendor invoice	Post a pending vendor invoice, with or without purchase order lines, once it is matched and approved.
Purchase return to credit note	Return goods to a vendor and post the vendor's credit note.
Vendor invoice approval journal	Register vendor invoices, route them through the invoice pool and approve them.
Vendor payments	Propose vendor payments, generate check payments and post them, settle payments against invoices, pay an advance against a purchase order, and reverse a payment.

Inventory, logistics and production

Scenario	Outcome
Inventory journals	Move, adjust, count and transfer stock, report BOM items as finished, count by tags, and take over consignment stock.
Transfer order ship and receive	Ship a transfer order from one warehouse and receive it at the other.
Production order lifecycle	Take a production order from estimate to end: release, start, pick, report time and finished goods.
Activate new standard costs	Calculate item costs from BOMs and routes into pending prices, make the pending prices of a costing version active, and revalue on-hand inventory at the new costs.

Finance and projects

Scenario	Outcome
General and intercompany journals	Post ledger journals, including customer invoices, vendor adjustments, bank transfers and entries across legal entities, with a validation-only preview first, and reverse a posted journal.
Post an existing journal	Post a ledger, inventory, project, production or trade agreement journal that was entered or imported in D365, when your system decides.
Post a journal exactly once	Call a posting service so a retry or a duplicate call never posts twice.
Budget register entries	Post original budgets and budget transfers.
Fixed asset lifecycle	Acquire, depreciate, adjust, transfer, split and dispose of a fixed asset, and reverse a posting made in error.
Currency revaluation	Revalue open foreign-currency balances.
Project journals and invoicing	Post hours, expenses, items and fees to a project and invoice them.
Expense reports	Create a worker's expense report from your expense tool, send it to approval, and post it once approved.

Approvals

Scenario	Outcome
Workflow approvals	Submit documents to D365 workflow and approve, reject, delegate or recall them from your system.

3. Work at scale and stay informed

Scenario	Outcome
Batch and async operations	Send many requests in one call, or hand long-running work to D365 and collect the result later.
Track documents and read data	Follow a document's status after a call and read D365 data through OData.
React to business events	Have D365 tell your system when something happens, instead of polling.
Inbound file to posted document	A partner drops order or journal files; Lattice pulls, transforms and posts them, with recovery when one fails.
Import journals in bulk	Load a large file of journal lines (inventory, payments, customer and vendor invoices, projects, production, trade agreements, forecasts, BOMs, bank statements, asset books) with set-based data management, and get ready-to-post journals with every refused line explained.
Validate and refresh data project mappings	Check the field mappings of your data projects before a deployment or after an update, and repair missing and broken mappings without losing your own.

4. Operate the integration

The day-to-day operating tasks are in the operator guides:

Task	Where
The daily check, recovering a failed message, fixing and resubmitting a payload, tracing a message, testing an operation safely, tuning logging	Integration operations
Publishing the API to Azure API Management, inbound order guardrails, turning off an asynchronous operation, just-in-time database access	Integration operations
Browsing the OData surface, entity templates, recurring data jobs, data management configuration in source control	Data entities
Discovering, activating and filtering business events	Business events
Setting up external systems and the cross references of a record	Cross-reference keys
What every Lattice page does	Page reference

How to read a scenario

Each one is structured the same way:

1. Goal & when to use: the business outcome and the shape of problem it fits.
2. Prerequisites: what must exist first (security, configuration, license).
3. Steps: the ordered actions, with request examples, each linking to the reference doc for detail.
4. How to verify: the concrete signal that it worked.
5. When it goes wrong: the refusals you can meet and the recovery path.

Reference docs these link into

• API reference: services, operations, entities, tables.
• Endpoint payload specification: per-operation request and response payloads.
• Security model: privileges, duties, roles.
• Posting preview: the validation-only preview.
• Idempotency reconcile runbook: exactly-once reconciliation.
• User guide: file ingestion setup.
• Table and entity coverage: which tables an entity covers.