Hi @PIreland 

How about below suggestions?

    1.    Renumbering Logic: Implement an automatic renumbering function that updates line numbers when a line is deleted, ensuring a continuous sequence that reflects the current active lines.
    2.    Revision History: Consider maintaining a revision history that clearly indicates deleted lines while allowing active lines to be renumbered. This approach preserves the original structure without cluttering the current view.
    3.    Internal Workarounds: If feasible, consider creating a report or supplementary document outlining changes and reasons for deleted lines, which would help track contract history without affecting the numbering.

Regards 

Chanuka

Hi Patrick,

I would be careful with renumbering the Line No or the Item No. These are part of the Primary Key and are used in all related tables and in the different revisions.

For sure if there is an Application For Payment you should not do this, but if nothing has happened on the SC yet, and you would also renumber all revisions, it might be OK

Another alternative might be to add a “Customer Line no” that you use in the various reports? That would contain the renumbered Line No. For sure has less risk and is a lot smother in new releases.

Regards Erik

Hello @EriLNL and @Chanu_Yazi 

I’m aware of ways that could solve or make the problem manageable but they require modification, I don’t think it can be done with a customization.  I should have phrased by last question like this:

Has anyone else had customers who did not like this numbering convention or perhaps have found a way around this phenomenon without modifcation?

Thank you.

Patrick