Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

A PMML file cannot be used to create a predictive model

Updated on September 10, 2021

The PMML file that you uploaded contains unsupported features in its model definition.

Cause

This problem occurs when one of the following conditions apply:

  • The PMML file does not contain the attribute version for the PMML root element in the model definition. The version is used to determine the schema definition that is required to validate the model source file.
  • The PMML file does not have an output. The output can be defined as part of the MiningSchema, Output, or Target element.
  • The PMML file has an empty data dictionary.
  • The PMML file has mining fields that do not have corresponding data field elements.
  • The PMML file has the ampersand character (&) as part of the name or ID of any of the data field elements.
  • The PMML file contains the TableLocator element.

Solution

Ask a PMML developer to investigate the error message that indicates the nature of the error and fix the problem. Note that not all PMML model types are supported in the Pega 7 Platform. For more information, see Supported models for import.

  • Previous topic Troubleshooting decision management components
  • Next topic A strategy uses multiple models with parameterized predictors, but their values are not recorded

Related articles

Troubleshooting decision management components

Tags

Pega Platform 7.1.1 - 8.3.1 System Architect Lead System Architect Decision Management

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us