Forum Discussion
QuickBaseCoachD
Qrew Captain
The [Record ID#] field is the default Key to the table. Typically in Quick Base "speak" we do not call that the Primary Key as there is only 1 Key per Table, so that is the Key field.
If you are now have imported new data which includes a different field that you want to have be the Key field, you can set that new field to be the Key field and after a few scary warning message, Quick Base will make the required changes so that any child record will remain attached to the correct Parents.
Its always a good idea to play with this in a copy of your application if you have not had much experience with changing the Key field.
But once you make that change, then while the [Record ID#[] field will always continue to exists and will always auto increment right up to infinity (well at least to an incredibly big number), your new Key field is now a data entry field that you must maintain manually. It will not auto increment.
I think that you need to reconsider why you want to change the Key field. Is your data going forward going to be hand typed into the app. If so, why change the Key field?
Or is the data going to be imported for another system which will do the auto incrementing of your new Key field? if that is the case, then you do not need Quick Base to auto increment.
Maybe your goal is to retain the value of the Key field for old records being imported and have Quick Base auto number going forwards.
I that case, you could import enough blank records from excel to create the highest record ID# count that you need. Let's say that is 9,000 records. So create say 10,000 records which are blank. (You will need to have at least 1 dummy field being loaded)
Then import your legacy data and map the old Key field into the record ID# field. Most of those 10,000 records will be updated. Those records will be updated. if there were deleted Keys in the legacy data, then those Record ID's will not get populated.
Then delete all the blank records.
Now, new manually entered records will start fresh at Key field ([Record id#]) of 10,000 so every knows that records below 10,000 were from the big import and above 10,000 were the new Quick Base system records.
If you are now have imported new data which includes a different field that you want to have be the Key field, you can set that new field to be the Key field and after a few scary warning message, Quick Base will make the required changes so that any child record will remain attached to the correct Parents.
Its always a good idea to play with this in a copy of your application if you have not had much experience with changing the Key field.
But once you make that change, then while the [Record ID#[] field will always continue to exists and will always auto increment right up to infinity (well at least to an incredibly big number), your new Key field is now a data entry field that you must maintain manually. It will not auto increment.
I think that you need to reconsider why you want to change the Key field. Is your data going forward going to be hand typed into the app. If so, why change the Key field?
Or is the data going to be imported for another system which will do the auto incrementing of your new Key field? if that is the case, then you do not need Quick Base to auto increment.
Maybe your goal is to retain the value of the Key field for old records being imported and have Quick Base auto number going forwards.
I that case, you could import enough blank records from excel to create the highest record ID# count that you need. Let's say that is 9,000 records. So create say 10,000 records which are blank. (You will need to have at least 1 dummy field being loaded)
Then import your legacy data and map the old Key field into the record ID# field. Most of those 10,000 records will be updated. Those records will be updated. if there were deleted Keys in the legacy data, then those Record ID's will not get populated.
Then delete all the blank records.
Now, new manually entered records will start fresh at Key field ([Record id#]) of 10,000 so every knows that records below 10,000 were from the big import and above 10,000 were the new Quick Base system records.
KateTheriault
7 years agoQrew Cadet
The second half of your comment is exactly right. I'd like to maintain the old values and have Quickbase autoincrement the new values. I will try that method, thank you. You are so reliable on here; it's really incredible. /hats off