In order to support varied testing and especially split-model deployments (same dev model with different data sets/time periods), it would be useful to have Time Ranges be Production Data. This will provide value in allowing all deployed models linked to the development model to be configured independently and save on model space without the risk of syncing the incorrect time range definitions and losing data or surpassing workspace size limitations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.