Is there a way to customize the starting number for the default record ID field? I would like the first record to be 100 instead of 1.

  • 0
  • 1
  • Question
  • Updated 4 years ago
  • Answered
Photo of Rachel

Rachel

  • 52 Points

Posted 4 years ago

  • 0
  • 1
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 62,520 Points 50k badge 2x thumb
No problem.

Just use excel to import enough dummy records to get your next real record to be 100.  Then run a list all report, "More" and Delete them all. Don't overshoot, there is no way to roll back the country without copying your whole app without data.
Photo of Rachel

Rachel

  • 52 Points
Thanks Mark!  I knew there had to be a simple way to do this and I was overthinking it.
Photo of Tom_M

Tom_M, Champion

  • 0 Points
Is there a specific reason that you want to use the built-in record id field? If not, a far more flexible option would be to create a formula numeric field (let's call it record number) to calculate a number based on the built-in record id.


For example, you are testing your application's functionality prior to moving it to production and you have already created 36 records as a part of your testing. When you move to production, your formula numeric field named record number would contain the formula [Record ID] + 63. This way, the first record created in production would have a built-in record id of 37 and adding 63 would get you to a record number of 100.


Similarly, if you created 120 records as a part of your testing, your record number field could contain the formula [Record ID] - 21 so that when the first production record is created and has record id = 121, it would show up as record number 100.

Reporting and such within the app could then be keyed off your calculated record number field rather than the built-in record id field. Hope this helps.
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 62,520 Points 50k badge 2x thumb
Well, FWIW, I would not recommend that. If I have say an Invoice number and that Invoice Table is the Parent to Invoice Lines, I always want the field [Related Invoice] in the Invoice Lines table to be the Invoice number and not a meaningless [Record ID#]. Just keeps the app less complicated to maintain in the future.
Photo of Tom_M

Tom_M, Champion

  • 0 Points
Couldn't you simply import the calculated invoice number field into the Invoice Lines table through the relationship setup? Then you would have a field that operates just like "related invoice", but is named something else? Or am I still missing the strength behind adding and deleting records to manufacture the correct record id?
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 62,520 Points 50k badge 2x thumb
I don't understand your comment about porting the calculated invoice number.

I'm just saying that if the Invoice number is 100, then the app is simpler if the record ID is 100.  Yes, I know that you can create your own Invoice number as a formula, but why add that complexity. So when I'm ready to launch an app I ask my client what Invoice number to start at, and typically they will choose 1000.  So I just import and then mass delete enough dummy records to roll the counter forward. I just make an excel sheet and import.