The use case we are attempting to protect here is as follows.
Numerous Cetec ERP users do not have any pricing pre-loaded in any pricing table, i.e. “blank” pricing for part numbers. These users enter their pricing manually on line items each time.
If that is the case, and in the instance when a user has spec’d out a quote line… and then at a later point that user goes in and modifies a part number to a different part number that has “blank” pricing, then the system would automatically blank out the price that the user had previously manually entered as the price on the line item. That’s bad, because 1- the user may not notice that the system blanked out their price; and 2- the user had to double their efforts to re-enter it manually. We’ve gotten… “loud” feedback from users about this behavior in the past.
That being said, as you point out above, there are some consistency problems in the software currently, where some transaction pricing autopopulation behavior occurs as you describe above, and some doesn’t.
Our first order of business will be making the behavior across the system consistent and predictable. Likely the design pattern we are settling on is the one you are expressing a preference for here, so that’s good news. To cover the other use cases and other users’ preferences, I believe we will have to introduce some UI alerting in those cases when prices get blanked out requiring manual re-entry of pricing.
Thanks for your feedback and ongoing patience here @spencer - we’ll post back on this thread with updates.