Globals are session-specific. Each user will see the calculation (or filtered portal, for example) as per their session's global values.
Unrelated calculation will not give the right information or any at all.
if your calculation is a global field, each record will have unique global calculation meaning it will show each user what kind of information you have put into the field.
Why don't you set the calc field to global storage anyhow?
An unstored calculation field will show the result of an expression according to the context when it evaluates.
Users will see their own globals.
1 of 1 people found this helpful
Your question is:
Does the calc field act like a global and show different values for each person, or will everyone see the value of the last person to cause the calc to evaluate?
Depending on your calculation, the "not global" calculation field will handle the calculation like this:
- The values it is using from the other "not global" fields will be the same as for other users if being at the same record on the same layout.
- The value it is using from the global field will be specific for the specific user.
Therefore the result will be specific for the individual user depending on the value in the global field. If the global is empty and the calculation is still logic with an empty value then everybody would get the same result if they are at the same layout and on the same record. If the content of the global is "different" for each user they will get different results.
But your calculation field is not acting like a global field. Because when the "not global" values change, depending on the context, found set or the specific record .... the content will change and will not be the same across the entire file like a global field would.
And while a global field can be used from anywhere in any context, the calculation field will still only work depending on it's graph context.
I hope this is clear.
Clear and comprehensive answer. Thank you very much