Example - Feature Filtering

You can find an example feature file, FeatureFilterNoKnowledge.xml, in the Composer installation directory: < install_dir>\Bin. This topic provides examples of how you can customize this file to prevent attributes and meta-properties from being exported to Composer files.

This page discusses:

Basic Example

In this example, the file is separated in two parts: geometrical set and product.

In this example, metadata from geometrical set features is not exported, except for the following:

  • The feat 1 knowledge parameter from all geosets not described in the XML.
  • The H and Y knowledge parameters from the Point.2 geoset.
  • The KP1 knowledge parameter from the joint3 geoset.

Similarly, metadata from product features is not exported, except for the following:

  • The KP1, KP2, and KP3 knowledge parameters from the joint1 feature.
  • The KP1 and KP2 knowledge parameters from the joint2 feature.

Information to Keep in Mind

Keep the following in mind when customizing the FeatureFilterNoKnowledge.xml file:

  • Feature names, types, and parameter names are case-sensitive and must be written exactly as specified by their meta-property. For example, a meta-property might be displayed as "Description" in the 3DEXPERIENCE, but might be named "V_Description". In this case, you need to use V_Description for the knowledge parameter.
  • Contrary to the Feature Filtering functionality in CATIA Composer (that lets you filter out only knowledge parameters and user-defined properties), when exporting content to CATIA Composer files, you can filter out all types of user properties or attributes from 3DEXPERIENCE data. Only the Reference Name property cannot be filtered and is considered as the default meta-property.

    So, for example, if you use the FeatureFilterNoKnowledge.xml file as is, only the Reference Name meta-property is exported. All other meta-properties will be filtered out at export time.

  • If you keep a property that is present in both a reference and its instance, then the property of the instance is exported with the prefix Instance_. Hence if a reference has a PLM_ExternalID property, then the instance is exported with a Instance_PLM_ExternalID property.