Skip to content

Commit 5403b46

Browse files
authored
minor change
1 parent 3ffbbfd commit 5403b46

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/dynamics-365/supply-chain/asset-management/asset-id-not-editable-when-number-sequence-is-manual.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Asset ID Isn't Editable When Number Sequence Is Set To Manual
33
description: Provides a workaround for editing Asset ID in Microsoft Dynamics 365 Supply Chain Management.
44
author: sorenbacker2
55
ms.author: sorenba
6-
ms.date: 02/25/2025
6+
ms.date: 02/27/2025
77
ms.custom: sap:Asset management\Issues with asset management
88
---
99
# Asset ID isn't editable when number sequence is set to Manual
@@ -23,7 +23,7 @@ This behavior is by design. A user can't edit an existing **Asset ID** because t
2323
To allow a user to edit the **Asset ID** on an existing asset despite the risk of data corruption, a developer would need to extend the `EntAssetObjectTable` form and change the property of the field.
2424

2525
1. Use Chain of Command (CoC) to change the control property through calling the `allowEdit()` method of the control and passing `false` as an argument.
26-
1. Create an extension class and extend the `init()` form method to programmatically allow editing on the field after the `next()` call.
26+
1. Create an extension class and extend the `init()` form method to programmatically allow editing of the field after the `next()` call.
2727

2828
For a detailed explanation of the approach, see [Class extension - Method wrapping and Chain of Command](/dynamics365/fin-ops-core/dev-itpro/extensibility/method-wrapping-coc).
2929

0 commit comments

Comments
 (0)