Understanding and Creating Data Entities
What's a Data Entity (really)? A Data Entity is a business‑friendly view over one or more normalized tables (e.g., CustTable , addresses, contacts), packaged so you can import/export, integrate, and evolve with less pain when the underlying schema changes. Think: one door, many rooms behind it . Entities can also be exposed as OData (for APIs) and used by the Data Management Framework (DMF) for bulk import/export. Heads‑up: F&O does not allow direct T‑SQL against the prod DB. Entities (and BYOD) exist to keep you safe and supported. When should I create my own entity? You need a clean shape for integration—not ten joins. You plan to expose an API (OData) for a specific business concept. You want DMF import/export (files, recurring jobs, mapping) without writing plumbing. Step‑by‑step: Create an entity for Item Serial Numbers Example scenario: Export/import item serial numbers from the InventSerial table (and related bits) via one entity. Create a project in Visual Stu...