Multiple Counter Values
Hi, I am currently trying to make a program that uses an ID in order to identify a specific item. My ID follows the following format: www-xx-yy-zzz. For example, a yellow highlighter might have the ...
Forum Discussion
sure, here are some links
https://community.quickbase.com/communities/community-home/digestviewer/viewthread?MessageKey=d30c143b-d701-410b-b933-bc4874f403b6&CommunityKey=d860b0f8-6a48-487b-b346-44c47a19a804&tab=digestviewer
https://community.quickbase.com/blogs/matthew-brisch1/2020/01/22/auto-numbering-in-quick-base
https://community.quickbase.com/browse/blogs/blogviewer?BlogKey=ef9eca41-cd5f-4711-bf42-f9d9f26c6c7a&CommunityKey=d860b0f8-6a48-487b-b346-44c47a19a804&tab=blogviewer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
and here is an answer among several I once posted.
Basically the idea is to create a [Sequence #] field which is based on a formula which will start off the numbering by Department at whatever number you want to start at.
var number StartNumber =
Case([Department Number],
"10",1234,
"20",2000);
Max($StartNumber,[Sequence # snapshot])
Then we make a field called [Sequence # plus 1] which is the formula of [Sequence #] +1, and make a summary of the Maximum that field.
and then do a lookup back down to the Antiques Table and then take a snapshot of that field called [Sequence # snapshot]
By doing a snapshot we ensure that the numbers don't all get jiggled down when a record is deleted.
The actual Serial # we display is this formula.
[Department Number] & "-" & Right("00000" & ToText([Sequence #]),6)
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
https://community.quickbase.com/communities/community-home/digestviewer/viewthread?MessageKey=d30c143b-d701-410b-b933-bc4874f403b6&CommunityKey=d860b0f8-6a48-487b-b346-44c47a19a804&tab=digestviewer
https://community.quickbase.com/blogs/matthew-brisch1/2020/01/22/auto-numbering-in-quick-base
https://community.quickbase.com/browse/blogs/blogviewer?BlogKey=ef9eca41-cd5f-4711-bf42-f9d9f26c6c7a&CommunityKey=d860b0f8-6a48-487b-b346-44c47a19a804&tab=blogviewer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
and here is an answer among several I once posted.
Basically the idea is to create a [Sequence #] field which is based on a formula which will start off the numbering by Department at whatever number you want to start at.
var number StartNumber =
Case([Department Number],
"10",1234,
"20",2000);
Max($StartNumber,[Sequence # snapshot])
Then we make a field called [Sequence # plus 1] which is the formula of [Sequence #] +1, and make a summary of the Maximum that field.
and then do a lookup back down to the Antiques Table and then take a snapshot of that field called [Sequence # snapshot]
By doing a snapshot we ensure that the numbers don't all get jiggled down when a record is deleted.
The actual Serial # we display is this formula.
[Department Number] & "-" & Right("00000" & ToText([Sequence #]),6)
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
I have a similar problem but I have a unique issue. I understand the Record ID as a Sequence Number solution but my Child Table serves as the table for many records that may be separately associated with one Parent Record.
In other words, the Child Table contains records that could be associated with different Parent records. In my case the Parent table contains CAPEX Numbers, each Parent CAPEX could have many Children.
The CAPEX Number consists of the Program Name, the Year, and a Sequential Number (abcde-2021-#####), then on the Child table I would like to have an additional suffix for each Incremental CAPEX Request that starts at 1, then 2.
This would mean that each SET of child records for a given Parent record need to start at 1 and increase by one each time a new Incremental record is added.
I tried a Counter but haven't figured out how to get the first Increment to stay at 1, when the counter becomes 2 etc.
Thanks for any assistance
Mike V
------------------------------
Michael Van Drunen
------------------------------
In other words, the Child Table contains records that could be associated with different Parent records. In my case the Parent table contains CAPEX Numbers, each Parent CAPEX could have many Children.
The CAPEX Number consists of the Program Name, the Year, and a Sequential Number (abcde-2021-#####), then on the Child table I would like to have an additional suffix for each Incremental CAPEX Request that starts at 1, then 2.
This would mean that each SET of child records for a given Parent record need to start at 1 and increase by one each time a new Incremental record is added.
I tried a Counter but haven't figured out how to get the first Increment to stay at 1, when the counter becomes 2 etc.
Thanks for any assistance
Mike V
------------------------------
Michael Van Drunen
------------------------------
- I suggest that you have a Data Entry field on your child table for [CAPEX Suffix#].
Make a summary field on the relationship to calculate the Maximum of that field.
Make a formula numeric field to calculate the [Next CAPEX Suffix#] ie [CAPEX Suffix#] +1.
Then on the ADD Child button use [Next CAPEX Suffix#] to populate the [CAPEX Suffix#] field.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
