Saving filtersa set of specified criteria that are applied to data in order to identify the subset of data for a subsequent operation, such as continued processing. based on model-specific attributes can cause conflicts with different models, in the same pipeline or other pipelines for a project.
For example, the user can run the Retired Forecasting modeling node in one pipeline
and save a filter using the Model forecasta numerical prediction of a future value for a specified time period for each unique
combination of BY variable values attribute value, customModel. If
the user then goes to the Forecast Viewer for
the Panel Series Neural Network modeling node, simply selecting
the Model value, customModel,
invokes the saved filter from the retired modeling node. The Filter drop-down
menu shows the name of the saved filter from the Retired Forecasting
model. If you attempt to save the selected model, it simply renames
the existing filter instead of saving as a new filter.
This should occur only when the Model value selects all of the time seriesan aggregation of transactional data into specified time intervals and sorted according to unique combinations of the default attributes (BY variables) in the Forecast Viewer for both models.
If you need to save filters based on model-specific attributes, consider using those filters in separate projects. Filters in one project cannot be used in other projects. For a list of model-specific attributes, see Model Attributes (OUTMODELINFO).