You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the update method in the SubsetServices uses the SubsetDeleteAllElements TI function, behind the scenes, when updating static public subsets.
This is a relic from TM1 version 10.2.2 FP 6, when there was no official way to clear all elements from a static subset through the REST API. TM1 11 provides this functionality through standard API calls.
The update method needs to be refactored, in order to make us of the standard functionality instead of TI.
The text was updated successfully, but these errors were encountered:
- make use of api to remove all elements from a static subset
- refactoring of test cases for subset operations
- introduces new is_dynamic, is_static methods on Subset class
- make use of api to remove all elements from a static subset
- refactoring of test cases for subset operations
- introduces new is_dynamic, is_static methods on Subset class
- make use of api to remove all elements from a static subset
- refactoring of test cases for subset operations
- introduces new is_dynamic, is_static methods on Subset class
Currently the update method in the SubsetServices uses the
SubsetDeleteAllElements
TI function, behind the scenes, when updating static public subsets.This is a relic from TM1 version 10.2.2 FP 6, when there was no official way to clear all elements from a static subset through the REST API. TM1 11 provides this functionality through standard API calls.
The update method needs to be refactored, in order to make us of the standard functionality instead of TI.
The text was updated successfully, but these errors were encountered: