When an Asset is created through the Order-to-Asset process (for example, via a Staged Assetized Fulfillment Step or the Create or Update Asset from Order action), the Renewal Term and Renewal Term Unit fields are not populated on the resulting Asset.
Because these fields are blank, a subsequent Renew action on the Asset fails with:
We couldn't renew the assets. All assets in a request must have values for RenewalTermUnit and RenewalTerm.
This is expected, working-as-designed behavior. The assetization process has two branches, determined solely by whether a Contract is associated with the Order:
No Contract on the Order — Renewal Term and Renewal Term Unit are populated on the Asset, copied from the Order Product fields PricingTerm and PricingTermUnit.
Contract present on the Order — Renewal Term and Renewal Term Unit are intentionally left blank on the Asset. The platform expects these values to be derived from the associated Contract (through the active Asset Contract Relationship) at renewal time.
How to confirm which branch applies:
Check whether the Order has a Contract associated with it.
If a Contract is present, the blank fields are expected.
If no Contract is present, verify that PricingTerm and PricingTermUnit are populated on the Order Product; if they are blank, the Asset has no source values to inherit.
Options to populate the fields when a Contract is on the Order:
Ensure the source Contract has valid Renewal Term and Renewal Term Unit values so renewals initiated from the Contract Asset Viewer succeed.
If the values must exist directly on the Asset, use custom automation (Flow or Apex)
There is no out-of-the-box mechanism that copies Renewal Term and Renewal Term Unit from the Contract onto the Asset during assetization.
005433451

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.