New
Use a Formula to Read a Model Point Field by Name
Users can now select a Model Point Field by name using a formula as a more dynamic alternative to selecting a single field by name from the drop down. All formulas that return a string value are considered valid in the variable editor. When the projection is run, Slope will attempt to match the string value to a Model Point Field name and will error if there is not a match.
Enhancements
Virtual Folders on Projection Templates
Users can now select a folder on a projection template so that all projections run from the template are automatically organized into the set folder.
Sunsetting Snapshots
Users will no longer be able to take new snapshots of models. The best approach for preserving a model at a point in time (e.g. after year end valuation) is to set the model to Copy Only using Model Permissions and make all edits to a new copy.
This approach makes it easy to compare the Copy Only (former version) with the edited version using the Manage model to review all changes made to the model.
Additional Information available Available on the Debug View for Arrays
- When only some of the static array values were run in a projection, the calculated values will display and those that don’t have results will indicate that there is no result available.
- Array values deleted after the run will be displayed as struck through and explain the value no longer exists.
- When a variable is changed to be an array variable after the run, and there is a single formula for an array (e.g. dynamic array) the formula will be displayed in the debug view.
- When there is a result without an array value we will show the result with no array value selected.
Fixes
- Empty data cell values on data tables are no longer causing unknown errors.
- The control panel has been removed from the Error report displayed on the Run Logs tab.
- The Asset Allocation page is properly reloading after an asset is deleted following the use of the search panel.
- The header of a data table is no longer included in the row count of an error message.
- Merging a table structure change will now trigger data table versioning on the destination model.
- Model validation is now being triggered when merging a portfolio or product.