Six-level nested IF is getting unmaintainable. Looking for the cleanest table-driven pattern to filter the next control off the previous selection.
Customers send prose, not fields. Curious how people are pre-parsing an RFQ into a structured spec without the model inventing values.
Trying to chain configure → export drawing across three sizes we quote. Is there a clean way to loop configurations through the MCP server?
Setting up our first real project. What conventions have held up for you over time — naming, groups, where you keep tables?
Reading mass right after a suppress sometimes returns the pre-rebuild value. Anyone else hitting this and forcing a rebuild first?
Weighing the REST API vs a direct write for getting quotes back into Epicor. What has been more maintainable for you?
Would love a way to see exactly what moved in a rule between two versions — a proper diff instead of squinting at nested logic.