A product stays a draft while something in its model is missing or does not add up, and a draft has no figures to report. Products > Data issues gathers the reasons for every product in the workspace in one place, says how to fix each one, and takes you to the spot in the model that raised it.
The line at the top says how many products are drafts. Of those, it also says how many only wait on a sub-recipe that is still a draft, how many will complete at their next calculation, and how many have not been checked yet.
When drafts have a problem of their own, Data issues in the left rail carries a badge with how many. It updates when a product is saved or the page is reloaded.
Blocking
The Blocking tab lists each problem that keeps products in draft, one row per problem:
- Issue: what is wrong, such as "Supplier shares do not add up to 100%".
- Where: the life cycle stage it is raised in (Raw materials, Production, Distribution and so on).
- Products: how many products have the problem themselves.
- Used by: every product further up that uses one of them as an ingredient or sub-recipe, draft or complete, and how many of those it holds as drafts. This is the reach of a fix: a placeholder in a widely used internal product can reach far more products than its own count suggests.
Click a row to open it. How to fix says what to do, then each product is listed with what was found in it. Click what was found to open the product's model at that spot: the editor opens the facility or location the step sits in and highlights the node. A finding raised on several lines or steps of one product is shown once, marked ×2, ×3 and so on. On a recipe it stays plain text: open the recipe from its name.
A row marked Contact support to fix is a data error the editor cannot correct. Send us the product name and we will repair it.
Waiting on a sub-recipe
The last row, Waiting on a sub-recipe that is still a draft, lists products with nothing wrong of their own: they use an internal product or sub-recipe that is a draft. Each names the one it waits on. Fix that one (its own problem is listed above), and the products waiting on it complete at their next calculation. A sub-recipe that is already complete again reads "now complete: the next calculation completes it".
Common problems and their fixes
| Issue | How to fix |
|---|---|
| Supplier shares do not add up to 100% | When a raw material comes from several suppliers, their shares must add up to 100% and each must be above 0%. Adjust the shares on the line. |
| Amounts do not balance between steps | Within a step, what goes in must match what comes out, waste included, to within 5%; the final step must give the product's own amount plus its packaging. Adjust the amounts the message names, or add default steps to a facility to start from a balanced chain. |
| Raw material has no supplier | Open the line under Raw materials and add the supplier you buy it from, or your default supplier if you do not know. |
| Placeholder material not replaced or Placeholder process not replaced | Replace the placeholder with the real ingredient, material or process, or ask us to add it if it is missing. |
| Transport link missing | Connect the facility or supplier to the places before and after it, so the route is complete. |
| SKU missing | Add the product's SKU in its details. A copied product starts without one, because SKUs must be unique. |
| Co-product measured in a different kind of unit from the main output | Give both outputs of the step as a mass, so the impact can be shared by mass. See Co-products and by-products. |
Every other problem has its own How to fix when you open its row.
Assumptions
The Assumptions tab lists what the figures of your products rest on, for you to check, such as a supplier with a global origin, which uses a global average until you set the country the material comes from. These do not stop a product completing. Open a row to see the products and what to change.
Checking again and exporting
The page is read from each product's last save or calculation. Check again checks every product again without calculating anything; the line beside it shows how far a running check has got, or when the last one finished. The first time anyone opens the page in a workspace, a check starts on its own.
Export as CSV downloads every product and problem on the page, Blocking first.
What you see
Data issues follows the same access rules as your product lists:
- Products in spaces or folders you cannot open are left out, and the counts leave them out too. Internal products, which are not kept in folders, are always listed.
- A product you cannot open, such as a restricted product, is still listed by name, but shows Restricted: you do not have access to this product in place of what was found. The CSV export does the same.
Change models and product groups are not listed, and nor are products sent through the API at low resolution.