NetAsset - Sourcing Blank Field on Asset Creation

Overview

Two updates have been made to the NetAsset Custom Sourcing functionality: the ability to filter sourcing rules by Suitelet deployment, allowing differentiated behavior across asset creation interfaces, and the ability to source values from a blank field during asset creation, enabling user-defined inputs to populate fields on the resulting asset record. These changes increase flexibility in managing asset metadata during the creation process. 

Prerequisites

• Appropriate permissions to access NetAsset>NetAsset Setup > Manage Custom Sourcing.

• Target field on the asset record (e.g., Asset Tag ID) must be available and editable.

• Users must know the Suitelet deployment names if they intend to apply Suitelet-specific sourcing.

Step-by-Step Process

1. Source Information from a Blank Field

• Go to NetAsset > NetAsset Setup > Manage Custom Sourcing and click New.

• Fill out the following:

  • Name: A descriptive label for the sourcing rule.

  • Trigger: Set to Asset Creation.

  • Allow Edit: Check this box to enable manual input.

    • This introduces a new “- Empty (No From Field)-” option in the From Transaction Field dropdown.

  • To Asset Field: Choose the asset field to populate (e.g., Asset Tag ID).

• Click Save. View full size

2. Enter Value During Asset Creation

• Navigate to an asset creation page (e.g., Create Asset from Proposals).

• A new editable column (e.g., Asset Tag ID) will appear.

• Enter the desired value directly into the column.

• Click Create Single Asset. View full size

3. Confirm Value on Asset Record

• Once the asset is created, open the record.

• Navigate to the Accounting tab.

• The entered value will be populated in the targeted field (e.g., Asset Tag ID), reflecting your input from the creation page. View full size

Limitations/Things to Be Aware Of

• The Allow Edit checkbox must be selected to enable input from a blank field.

• The feature is best suited for free-form or flexible data inputs, but can also be used for list/record field types as long as the corresponding field on the asset record matches the same list/record.

• If sourcing to a restricted field type (e.g., list/record), ensure valid entries are used.

• Suitelet filtering is optional; omitting it will apply the rule universally across all asset creation interfaces.

Troubleshooting

• Field not appearing on asset creation page:

  • Verify that Allow Edit is checked on the sourcing record.

  • Verify that Asset Creation is set as the trigger on the custom sourcing record.

  • Confirm the target field is included on the asset form layout.

• Value not populating on asset record:

  • Ensure the field type and value are compatible.