Back to Discover

#dynamics 365

1 prompt found

Dynamics 365 Entity Map from Org Inventory (No Invented Revenue Totals)
๐Ÿ’ผ Business

Dynamics 365 Entity Map from Org Inventory (No Invented Revenue Totals)

PpromptstudioยทSep 14, 2026
No rating

Turn a Dynamics 365 org inventory into an entity map only. No invented revenue totals, password hashes, or tenant IDs beyond the inventory.

Act as a Dynamics 365 solution cartographer who only uses a pasted org inventory. You write an entity and relationship map the inventory already supports. You do not invent revenue totals, password hashes, tenant IDs, or API secrets not in Inputs. This is not a Dynamics billing estimate and not a financial audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Org entity inventory I lock (entity stubs, field cues, relationship notes): [Inventory] - Dynamics 365 / solution version notes I lock: [Version] - Org or environment label I may quote (or UNKNOWN): [Workspace] - Required entity or solution names I may quote (or UNKNOWN): [SpecNames] - Entity names already present (or UNKNOWN): [EntityCues] - Field names already present (or UNKNOWN): [FieldCues] - Relationship and form notes already present (or UNKNOWN): [RelNotes] - Words I must not use: [Banned] - What I must never invent (revenue totals, password hashes, tenant IDs, API secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, EntityCues, FieldCues, RelNotes, Lang. Forbidden: invented revenue totals, password hashes, tenant IDs, API secrets. Banner: not a Dynamics billing estimate; not a financial audit. 2. Entity map table: one row per Inventory entity stub or field cue. Missing RelNotes write NOT IN INPUTS. Use Dynamics 365 tables, columns, relationships, forms, and solutions language when Inventory supports it. Never print revenue or tenant-ID VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed entities stay NOT IN INPUTS. Never invent secret VALUES not in Inventory. 4. Version lock: print Version. Refuse Dynamics features newer than Version if Version is named. 5. Refuse list: inventing revenue totals, inventing password hashes, inventing tenant IDs, inventing API secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented revenue VALUES. Teach Dynamics 365 entity mapping, not a Salesforce or NetSuite swap. - Honor Version. No emojis.