Scenario:
The user created a Purchase Order saved search filtered by specific shipping items but noticed that fields such as Created From and Created From Shipping Cost were not appearing in the results. This occurred because the search was only returning the shipping item lines, while the desired values existed on the main line or inventory item lines of the transaction.
Solution:
This behavior occurs because transaction line-level filters limit the saved search results to only the matching item lines, which may not contain the related transaction values stored on the main line.
One recommended approach is to use a SuiteAnalytics Dataset, which provides better access to related transaction data across transaction lines.
Recommended Dataset Configuration:
Criteria:
- Type = Purchase Order
- Transaction Line: Item = [specific shipping items]
Results:
- Transaction
- Transaction Line: Item
- Created From =
Transaction Line > Related Transactions - Previous > Transaction - Created From: Shipping Cost =
Transaction Line > Related Transactions - Previous > Transaction > Shipment > Shipping Rate
Using SuiteAnalytics Dataset allows the search to retain the item-level filtering while still accessing related transaction and shipping values.
If using SuiteAnalytics Dataset is not feasible, an alternative approach is customization using custom transaction line fields:
- Create a custom transaction line field to store the Created From value.
- Create another custom transaction line field to store the Created From Shipping Cost value.
- Populate these fields through scripting or workflow logic during transaction processing.
This allows the values to exist directly on the filtered transaction lines, making them available in standard saved searches.