Run design analyses and map the designer's JSON

It is a bill of materials and a cost, computed from geometry. It performs no structural check: there is no deflection calculation, no wind-load verification, no compliance test anywhere in it. Sizes that are structurally unwise will be analysed, priced and cut exactly as drawn. Structural suitability remains an engineering judgement made against the supplier's tables — the maximum sizes on your glass and profile records are where that judgement gets written down so the catalogue enforces it.

1. Open Analysis › JSON Mapping › Discover Parameters, choose a sale order line to read a real payload from, and let it list the parameters actually present — filtered by section, and optionally showing the ones already mapped.
2. Create the mapping under Field Mappings: give it a name, the JSON Path and section to read from, and the Target Model and Target Field to write to.
3. Shape the value if you must — Multiply By, Round Digits, a Value Prefix or Suffix, or a Default Value when the payload has nothing.
4. For a value that must become a link to another record, set the Lookup Model and Lookup Field, and decide whether to Create if Missing.
5. Choose when it runs — Apply on Save, Apply on Analysis, or both — and use Condition and Python Expression only where the simple options genuinely cannot express it.

Each mapping records its own Execution Count, Last Execution and Last Error. Those three fields are the whole diagnosis: a mapping with a zero execution count never matched anything, and one with a last error is failing quietly on every design. Target Models lists which Odoo models the mappings are allowed to write into — the guard rail that keeps a mapping from writing somewhere nobody expected.

Configuration › Settings holds the designer's own behaviour — how drawings are rendered and dimensioned (draw mode, dimension mode, fonts, colours, print size), how area and size are measured, and whether a default quotation is generated. Configuration › Drawings is the drawing library those settings apply to. Neither is a place to change commercial numbers; they change what is drawn and printed.

An analysis is missing components — the payload references a profile, glass or hardware record that does not exist in the catalogue. Fix the catalogue, then re-analyse.

A mapping does nothing — check its execution count. Zero means the JSON path never matched; the Discover Parameters wizard on a real order line shows what the path should be.

A mapped number is out by a factor of ten or a thousand — the payload's unit is not the field's unit; that is what Multiply By is for.

Everything worked and now every design fails — read Last Error on the recently edited mappings before anything else.