Thread 20590 / Follow up
The fix and the workflow change
The member regenerated with the full recipe set and the new field appeared in the list and form screens. The root cause was a partial recipe selection that had been saved as the project default during an earlier experiment.
The project default was reset to the full set, and the team added a short checklist to its own project notes. The checklist names the layers that must be regenerated when an entity changes, and it asks the author to read the generation report before committing.
What changed
- The project recipe default was restored to the full set.
- The generation report became a required review item.
- A clean output folder is used for the first run on a new machine.
- The model file is committed with the generated code.
None of these steps is unusual. Together they make a generation run predictable, which is the whole point of a model centric workflow.