I know that the calculation field is work without put it on the actual layout.
For example: Line Price = Qty * Price
Some users said that is safer if it's muted (no color/no line) on the layout.
What do you guys think?
There is no need to put a calculation field on a layout unless the user needs to see the data it calculates.
plus 1. If it's a list view it would need to recalculate for every record viewed.
p.s. I just prefer to 'set field' for most data that needs to be calculated then it is:
does not need to recalculate
is historical (saved at the time it was calculated)
but I don't dismiss all calculation fields, you can decide what works, when and why.
Stored calculations do not recalculate in list view, only unstored.
I placed the calculation field Line Price in Line Items layout/table, but not on the Invoice layout (portal).
Should I set the calculations as stored value when generate sales report in List View then?
stored or not - IF you change the price of an item later, it will be recalculated in your older invoice items. This is what I mean by using an auto-enter or Set Field (by script & my preference). This should be historical data, not calculated.
I'm using the script to set field price in the Line Items table.
In my opinion all calculations should be stored if they can be defined that way and still work.
Calculations that reference global or related data must be unstored. Certain get functions such as get ( currentDate) require unstored or they won't update when the function would now return a new value.
Stored calculations and auto-enter calculations both automatically re-evaluate only when a field referenced in the expression changes.
Auto-enter calculations do not re-evaluate when you modify the expression and only re-evaluate during imports if you select the option to enable auto-enter options where calculation fields will automatically re-evaluate in both cases.
From what I see, lookup value, and set fields by script are stored values.
Is this right?
lookup can get a "re-lookup" should you need that. be very carefull if you consider lookup, but yes, it' very useful at times.
That's great info. I am often confused about which is best in which case.
Retrieving data ...