Impact of Changing has_batch_no field (Set Only Once)

We have setup many items with has_batch_no as false. However we realised that these items need batch number.

By default has_batch_no field is configured as ‘Set Only Once’ which do not allow changing the value on already saved item.

We wanted to understand the impact of running ErpNext in development mode and removing ‘Set Only Once’ check and then updating items.

We have not yet created any transactions like sale and purchaes. However these items are being used in the BOM configurations.

1 Like