💼 Business
Dynamics 365 Entity Map from Org Inventory (No Invented Revenue Totals)
Turn a Dynamics 365 org inventory into an entity map only. No invented revenue totals, password hashes, or tenant IDs beyond the inventory.
0Reviews
Prompt
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.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
Inventory: entity Harbor Quay Account as pasted field cue accountnumber as pasted rel notes primary contact as pasted; entity River Ops Opportunity as pasted field cue name as pasted. Revenue invent NONE. Tenant invent NONE. Version: Dynamics 365 Sales 2024 wave 1 as pasted (do not invent unreleased AI entity writer) Workspace: Harbor Quay Contoso UAT environment as pasted SpecNames: Account entity map as pasted; Opportunity entity map as pasted. API secret UNKNOWN. EntityCues: Account as pasted; Opportunity as pasted. Lead UNKNOWN. FieldCues: accountnumber as pasted; name as pasted. revenue UNKNOWN. RelNotes: primary contact as pasted. Revenue total VALUES NOT IN INPUTS. Banned: guaranteed revenue, revenue invent, tenant invent, secret invent Never: invent revenue totals, invent password hashes, invent tenant IDs, invent API secrets Format: ledger + table + specs + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: entity Harbor Quay Account field cue accountnumber rel notes primary contact; entity River Ops Opportunity field cue name. Revenue invent NONE. Tenant invent NONE. Version Dynamics 365 Sales 2024 wave 1. Workspace Harbor Quay Contoso UAT environment. SpecNames Account entity map; Opportunity entity map; API secret UNKNOWN. EntityCues Account; Opportunity; Lead UNKNOWN. FieldCues accountnumber; name; revenue UNKNOWN. RelNotes primary contact; Revenue total VALUES NOT IN INPUTS. Lang English. Banner: not a Dynamics billing estimate; not a financial audit. Forbidden: invented revenue totals, password hashes, tenant IDs, API secrets, guaranteed revenue, revenue invent, tenant invent, secret invent. 2. Entity map. 1. Harbor Quay Account | EntityCues Account as pasted | FieldCues accountnumber as pasted | RelNotes primary contact as pasted | revenue VALUES NONE | tenant NONE | Dynamics 365 entity map only. 2. River Ops Opportunity | EntityCues Opportunity as pasted | FieldCues name as pasted | RelNotes beyond primary contact NOT IN INPUTS | revenue VALUES NONE | tenant NONE. API secret UNKNOWN so write API secret NOT IN INPUTS. Lead not invented beyond EntityCues. 3. Spec name set. Account entity map; Opportunity entity map as SpecNames. API secret UNKNOWN so write API secret NOT IN INPUTS. No revenue VALUES beyond Inventory. No third entity invented. 4. Version lock. Dynamics 365 Sales 2024 wave 1 as pasted. Unreleased AI entity writer not used. Password hash packs NOT IN INPUTS. 5. Refuse. Revenue invent: refused. Tenant invent: refused. Secret invent: refused. Password invent: refused. Guaranteed revenue: refused. 6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: API secret policy, Lead EntityCues, revenue FieldCues, revenue total VALUES RelNotes, solution layer list if any. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.