Issue Summary

Data Manager – Computed attribute values appear correctly in the UI, but objects from one data source show as “Not mapped” when searching, filtering, or exporting.

 

Steps to Reproduce

1. In a JSM Cloud site with Assets and Data Manager enabled, configure a Data Manager flow with two sources feeding into the same compute job:

• • Source A: provides a classification attribute (for example, an “asset type”–like field) plus manufacturer/model attributes.

• • Source B: provides manufacturer/model attributes, but does not provide the classification attribute that Source A has.

2. Map attributes so that:

• • Source A’s classification column is mapped to a shared classification attribute.

• • Both sources map their manufacturer/model columns to the same shared attributes.

• • Source B leaves the classification attribute unmapped.

3. Configure computed attributes in Data Manager so that:

• • A first computed attribute derives a value using the classification attribute and manufacturer.

• • A second computed attribute derives a value using the first computed attribute and model.

1. Run the Data Manager job and resolve all computed issues until the job completes successfully.

1. In the Assets / Data Manager UI, inspect the resulting data set and confirm:

• • Objects from both sources display meaningful values for the computed attributes.

1. Using the same data set, perform a search, apply filters using the computed attributes, and/or export the data to a file.

1. Compare results for objects from Source A (with the classification attribute mapped) and Source B (without the classification attribute mapped).

Expected Results

• Computed attributes behave consistently across:

• • Data Manager / Assets UI,

• • Search and filtering, and

• • Export.

• If an object shows a non-empty computed value in the UI, then search/filter and export should show the same value, regardless of which source it came from and whether the original classification attribute was mapped for that source.

Actual Results

• In the UI:

• • Objects from both sources show valid values for the computed attributes after the job completes.

• In search/filter/export:

• • Objects from Source A (with the classification attribute mapped) behave as expected.

• • Objects from Source B (without the classification attribute mapped) are treated as “Not mapped” / empty for the same attributes, even though the UI shows computed values.

• This creates a discrepancy between the visualization in the Data Manager/Assets view and what users can search on, filter by, or export.

Workaround

No workaround available for now. 

A temporary workaround is to artificially map some column for all sources to the primary attribute so it is no longer flagged as NotMapped, but this:

• Distorts the data model, and

• Risks breaking behavior once that column receives real data.