Auto-number Functional Changes
Here's a description of the functional changes applied to the Auto-number field behavior.
Functionality | Prior to Version 5.0 | Behavior from 5.0 onward |
---|---|---|
Starting number |
|
|
Current Number | This property did not exist. Instead, the starting number displayed the current running sequence of the auto-number field. |
Note: The value of a current number cannot be edited or
retrieved through APIs . |
|
| When a record is being created from the user
interface, there is no validation involved as the auto-number field is
empty until the record is created. Note: When creating a
record from the user interface, if there are null or blank check
applied on the auto-number field, the validation triggers might fail
due to which the script might need modification. Other triggers
consume the auto-number field value. |
Create records | The auto-number field behavior for creating records from the user interface and the APIs were different. | The auto-number behavior is similar whether you
are creating records from the user interface or the APIs.
|
Edit records | The auto-number field behavior for editing records from the user interface and the APIs were different. | The auto-number field behavior is similar when editing records from the user interface and APIs. In both the cases, the current number is updated only if the auto-number field value is set in a valid format. |
Cloning records | Platform always generates a new value for the auto-number fields when cloning a record through the user interface or an API. |
Note: The current number is updated only if the
auto-number field value is set in a valid format.