Tooling management report export missing custom fields in pivot table Excel export

PLM ENOVIA
, , , , , , , ,
1

I’m having trouble with pivot table exports from our tooling management module in ENOVIA R2021x. When users export reports to Excel, several custom fields we’ve added to the tooling objects are completely missing from the export. These fields show up fine in the web interface pivot table, but the Excel export only includes standard out-of-box fields.

The missing fields include tooling cost center, supplier lead time, and maintenance schedule - all critical for our incomplete cost analysis workflows. I’ve checked the pivot table export configuration and our custom field mapping, but can’t figure out why the export is filtering these out.

<exportConfig>
  <includeFields>standard,custom</includeFields>
  <customFields>costCenter,leadTime</customFields>
</exportConfig>

The report template configuration seems correct, but clearly something isn’t connecting properly between the web display and the Excel export function. Has anyone successfully exported custom tooling fields?

system 2

I’ve successfully resolved this exact issue across multiple R2021x implementations. Here’s the complete solution addressing all three focus areas:

Pivot Table Export Configuration: First, verify your pivot table includes custom fields in its column definition. Edit the pivot configuration through Utilities > Report Administration > Pivot Tables. Ensure custom fields are checked in the “Available Columns” and moved to “Selected Columns” for export.

Custom Field Mapping: You need to register custom fields in the reporting metadata. Create or update ReportFieldDefinitions.xml:

<field name="toolingCostCenter" type="string" displayName="Cost Center"/>
<field name="supplierLeadTime" type="number" displayName="Lead Time (days)"/>
<field name="maintenanceSchedule" type="date" format="MM/dd/yyyy"/>

Report Template Configuration: The critical step most people miss - update the tooling management export template. Locate toolingPivotExport.xml in your reporting templates directory and add custom field mappings:

<columnMapping>
  <column field="toolingCostCenter" excelColumn="H" dataType="text"/>
  <column field="supplierLeadTime" excelColumn="I" dataType="number"/>
  <column field="maintenanceSchedule" excelColumn="J" dataType="date"/>
</columnMapping>

After making these changes:

  1. Restart the reporting service (not full server required)
  2. Clear browser cache to ensure new template is loaded
  3. Re-run your pivot table export

Key insight: The export template must explicitly map each custom field to an Excel column. The system doesn’t automatically include custom fields even if they’re defined elsewhere. Also ensure your custom fields have proper access permissions in the ACL - if users can’t read the field, it won’t export even with correct configuration.

For the cost analysis workflow, I recommend creating a dedicated export template specifically for financial reporting that includes all cost-related custom fields pre-configured. This prevents users from having to manually select columns each time.

This draft is based on general ENOVIA knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.

3

Check if your custom fields are registered in the reporting metadata. Just because they display in the UI doesn’t mean they’re available to the export engine. You need to add them to the ReportFieldDefinitions.xml file in your custom directory and restart the reporting service.

5

I’ve dealt with this before. The issue is usually that custom fields need explicit mapping in the pivot table export template. The template you’re using probably has a hardcoded field list that only includes standard attributes. You need to either modify the existing template or create a new one that includes your custom field mappings. Look in the reportTemplates directory for the tooling management export template XML.

7

Thanks for the pointers. I found the ReportFieldDefinitions.xml but I’m not entirely sure about the correct syntax for registering custom fields. Do I need to specify the internal attribute name or the display name? Also, should these definitions include data type and any formatting rules for the Excel export?

8

You need both internal and display names. The internal name is what the system uses for data retrieval, display name is what appears in the Excel header. Include data type (string, number, date) and format masks if needed. For currency fields like your cost center, specify decimal precision. The export engine uses these definitions to properly format cells in Excel - without them, it defaults to text which breaks pivot calculations.

9

Don’t forget about the report template configuration aspect. Even with proper field definitions, your export template needs to reference them. Check the pivotTableExportTemplate.xml specifically for tooling management - there’s usually a section listing available columns. Your custom fields must be added there with proper XPath expressions pointing to the field definitions.