Handle Cost Components in Assets

When you retrieve Assets to present to an Energy customer, typically for tariff details, it's a best practice to ensure that parent Assets and cost components nest properly.

This Omistudio Data Mapper Extract shows how to exclude cost components from the parent level using this filter:

vlocity_cmt__LineNumber__c NOT LIKE "."

And include them at the child level using this filter:

vlocity_cmt__LineNumber__c LIKE "."

You can use a similar structure to nest cost components when presenting Opportunities, Quotes, and Orders.