The following Crystal Ball spreadsheet functions are handled normally:
These functions are not supported in Extreme speed during a simulation:
While running in Extreme speed, all values for these functions return #VALUE. At the end of the simulation, Crystal Ball performs a final recalculation on the model so these functions are evaluated properly. Normally, this should not present a problem unless one of these functions was defined as a forecast and you are expecting a valid value to be computed during the simulation. If one of these Get functions feeds into a forecast during a simulation, this is not compatible with Extreme speed:
Example message: "Unsupported Microsoft Excel or Crystal Ball function at cell location [Book1.xls]Sheet1!A1. (Code #5539)"
Workaround: Defining forecasts on statistical functions that are dependent on other forecasts is generally not a good modeling practice. If you need to have a forecast cell defined on a statistical result from another forecast, use the Auto Extract feature for the dependent forecast instead of using one of the above Crystal Ball functions.