What it requires. CML uses lineItemQuantity or ItemEndQuantity to create components rather than treating them as read-only.
Why it matters. [doc + practitioner: Khaled McGonnell, 26 Aug 2026] "Treat lineItemQuantity and ItemEndQuantity as read-only... Drive component creation by cardinality, not by attribute references" (CML Best Practices). A cardinality constraint tells the solver the valid range directly; rule-driven creation forces it to enumerate and test combinations, and the cost compounds with permutation growth - practitioner-confirmed as disastrous for performance.
How to fix it. Declare the component range as cardinality; use quantity fields only in calculation and evaluation rules.
Source. Salesforce CML Best Practices; practitioner mechanism attributed (Khaled McGonnell, 26 Aug 2026)
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.