@dvlprlife It depends - I use both. If the if-statement can be a function that describes what it does, I would write it "if fx() then...else..."
If true of I often use, when there are many different conditions and outcomes.
@waldo1001@steveendow Most of the value we as VARs bring to the table is knowledge and experience - if we do not know the product (and thus do not have any experience with it) the value of the support we provides is reduced.
@waldo1001@steveendow From a customer support perspective, refuse sounds a bit hush... but I can relate to the point of view. Normally I would try and help the customer - but at the same time letting them know the risk of me supporting a product I do not know...
@steveendow I think I always have used numbers in CaptionClass. It should be the same in Base - unless they have changed it.
I see the documentation says something different, though ๐
@tnavguy I use WorkDate() unkess there is a special need for it to be the system date - but now with the system fields it is rarely required...
But yes, it should be a functional requirement โ๏ธ
@JesperSchulz@steveendow Just as new implementations should always have new pricing enabled. Even with no customization, the customer should not have to learn how to setup pricing twice...