2 Couple of corrections
source | link

Alternatives

1) Use ID

It is the best option because SharePoint ensures its uniqueness. But you can not apply business logic. It starts at 1 and increases by 1. You will have gaps when records are deleted.

2) Event handler

Create an event receiver to generate increased values according to the logic that you need. You need VisuaVisual Studio and #C#.

3) Workflow

It can be an alternative. But workflows are not planning for it. The advantage is that you do not need to develop in C #C# as in option 2.

Important

Do not use the ID field within a calculated field: - You will have trouble inserting a record. It will work well in the modification. - It is not officially supported by Microsoft

If you need further assistance, please consult me. Greetings!

Alternatives

1) Use ID

It is the best option because SharePoint ensures its uniqueness. But you can not apply business logic. It starts at 1 and increases by 1. You will have gaps when records are deleted.

2) Event handler

Create an event receiver to generate increased according to the logic that you need. You need Visua Studio and #.

3) Workflow

It can be an alternative. But workflows are not planning for it. The advantage is that you do not need to develop in C # as in option 2.

Important

Do not use the ID field within a calculated field: - You will have trouble inserting a record. It will work well in the modification. - It is not officially supported by Microsoft

If you need further assistance, please consult me. Greetings!

Alternatives

1) Use ID

It is the best option because SharePoint ensures its uniqueness. But you can not apply business logic. It starts at 1 and increases by 1. You will have gaps when records are deleted.

2) Event handler

Create an event receiver to generate increased values according to the logic that you need. You need Visual Studio and C#.

3) Workflow

It can be an alternative. But workflows are not planning for it. The advantage is that you do not need to develop in C# as in option 2.

Important

Do not use the ID field within a calculated field: - You will have trouble inserting a record. It will work well in the modification. - It is not officially supported by Microsoft

If you need further assistance, please consult me. Greetings!

1
source | link

Alternatives

1) Use ID

It is the best option because SharePoint ensures its uniqueness. But you can not apply business logic. It starts at 1 and increases by 1. You will have gaps when records are deleted.

2) Event handler

Create an event receiver to generate increased according to the logic that you need. You need Visua Studio and #.

3) Workflow

It can be an alternative. But workflows are not planning for it. The advantage is that you do not need to develop in C # as in option 2.

Important

Do not use the ID field within a calculated field: - You will have trouble inserting a record. It will work well in the modification. - It is not officially supported by Microsoft

If you need further assistance, please consult me. Greetings!