Custom attribute not visible in sustainability dashboard after Part class extension

PLM Oracle Agile PLM
, , , , , , , ,
1

I added a new custom attribute called “Carbon_Footprint” to the Part object for sustainability tracking, but it’s not appearing in our sustainability dashboard even after refreshing. The attribute is visible in the Part form and I can enter data, but the dashboard widget shows no data for this field.

The custom attribute was created through Java Client with Text data type and mapped to Page Two of the Part class. We need this field visible in the dashboard so our sustainability team can track carbon metrics across product lines. The dashboard is configured using a web report that pulls Part attributes. Other custom attributes we added months ago display fine. Any ideas what configuration step I might be missing?

system 2

Here’s the complete solution to get your custom attribute visible in the sustainability dashboard:

Step 1: Verify Custom Attribute Configuration on Part Class First, confirm the attribute is properly configured:

  • Open Java Client → Admin → Classes → Part
  • Locate Carbon_Footprint in the attributes list
  • Note the exact API Name (likely something like PAGE_TWO.CARBON_FOOTPRINT)
  • Ensure “Include in Reports” checkbox is enabled
  • If you need numeric aggregation in the dashboard, consider changing data type from Text to Numeric

Step 2: Update Web Report Attribute Mapping The sustainability dashboard relies on a web report that must explicitly include the new attribute:

  • Navigate to Reports → Find your sustainability report
  • Edit the report configuration
  • In the Columns section, click “Add Column”
  • Search for Carbon_Footprint using the API name from Step 1
  • If the field doesn’t appear, go to Admin → Reports → Refresh Attribute Cache
  • After cache refresh, the custom attribute should appear in available fields
  • Add it to your report and save

Step 3: Modify Dashboard XML Configuration The dashboard widget needs explicit reference to the new attribute:

  • Locate your dashboard configuration file (typically in WEB-INF/config/dashboards/)
  • Find the sustainability dashboard XML
  • Add the attribute to the data query section using the exact API name:
<attribute name="PAGE_TWO.CARBON_FOOTPRINT" label="Carbon Footprint"/>
  • Ensure the attribute is also included in any aggregation or filtering logic in the dashboard configuration

Step 4: Clear Caches and Verify

  • Application Server: Restart or clear web cache
  • Browser: Clear browser cache or use incognito mode
  • Database: If using custom queries, verify the attribute column exists in the underlying tables

After these steps, log in and check the dashboard. The Carbon_Footprint field should now be visible and populate with data from Parts that have this attribute filled in. If data still doesn’t appear, verify that your test Parts actually have values entered for this attribute - empty fields won’t display in dashboard aggregations.

For future custom attributes, enable “Include in Reports” during initial attribute creation to avoid this extra configuration.

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

3

Did you update the dashboard’s XML configuration file after adding the attribute? Custom attributes aren’t automatically included in existing dashboards. You need to modify the dashboard XML to explicitly reference the new attribute in the data query section.

4

The web report needs to be updated too. Even if the dashboard XML is correct, the underlying report query must include the custom attribute in its SELECT clause. Go to Reports → Edit your sustainability report → Add the Carbon_Footprint field to the report columns. Then refresh the dashboard cache.

5

I checked the web report configuration and the Carbon_Footprint attribute isn’t listed in the available fields dropdown when editing the report. Does this mean the attribute isn’t properly registered with the reporting engine?

7

That’s exactly the issue. When you add custom attributes through Java Client, they need to be explicitly enabled for reporting. Go to Admin Settings → Attributes → find Carbon_Footprint and check the “Include in Reports” checkbox. After that, you’ll need to refresh the report metadata cache before the field appears in the report builder.

8

Also verify the attribute’s API name. Sometimes the display name differs from the internal API name used in reports and dashboards. The XML configuration needs the exact API name, which might be something like CUSTOM_ATTR_CARBON_FOOTPRINT rather than just Carbon_Footprint.

10

I had this exact scenario last month. Make sure the attribute data type is compatible with dashboard aggregation. Text fields can have display issues in certain dashboard widgets. If you’re trying to show numeric carbon values, consider changing the attribute type to Numeric or Decimal for proper dashboard rendering.