Production AI in Business Central
-
1. Calling AI from Business Central: the platform realities nobody warns you about
Your AL HttpClient call to an AI endpoint returns send=false and no error. It's not your code, it's three platform guardrails (the HttpClient flag, the anti-SSRF allowlist and loopback hostnames) that fail silently. Here's the checklist.
-
2. A 502 in your PDF-to-LLM pipeline is the gateway, not the model
Business Central sends a PDF through an AI gateway and gets a flat 502. The instinct is to blame the prompt. Don't, the model never saw your document. Here's how to bisect the pipeline and force a text-extraction path that works.
-
3. Shipping a Copilot feature in Business Central that survives real users
A PromptDialog demo takes an afternoon. A Copilot feature real users won't switch off takes the other 90%: scoping, grounding, the generate, review, accept loop and treating the model's output as a proposal that never silently touches data.
-
4. Your AI feature must run on a fresh tenant, or it doesn't run
The line between a demo and a product is whether it works on a clean Business Central environment with none of your developer setup. Five concrete things that separate 'works on my box' from 'a customer can actually use it'.
