My unique ID point is where you want to have a test and live instance with the live instance being updated from test.
For example, I design Dashboard 1 in test. Publishing to live is easy as it doesn’t exist yet.
Next, I update Dashboard 1 in test. I want to update it in live, but there is nothing unique to link the source and destination.
I’m used to working with SAP BI. In that, every object has an ID within the server, but also has an additional GUID that is unique to that object. If you migrate from server A to B, the ID will change, but the GUID will remain the same. Means you can always identify the source.
With your method of just incrementing the ID, when I come to update a question, I’ll not be able to update the original question in the destination server. I just get 2 similar questions.
How do you manage the database ID?