Forum Discussion
AswinBabu
5 years agoQrew Member
By the current method that I use, i will input the textfield1 and and append it with the record id. But after i save and go to table view the design no. field will be abc0000. its same for every other records for eg: bcd000, cde000 etc. I have to edit the record again and in edit I'm able to see the designno. as abc001, bcd002 etc. Then after clicking edit when i save it once again without making any changes designno.'s are properly updated.
This method will be a 2 step process & This is not user friendly.
Please suggest another or changes to that I can do to this method.
------------------------------
Aswin Babu
------------------------------
This method will be a 2 step process & This is not user friendly.
Please suggest another or changes to that I can do to this method.
------------------------------
Aswin Babu
------------------------------
KirkTrachy1
5 years agoQuickbase Staff
Hi Aswin:
You have come across something which is a little involved but can be done.
Mark was right about the Record ID# not having been created yet so what to do?
Well we can create a formula that concatenates the pieces we wish to put together and then a form rule to fire when the record is created that puts that formula into a local scala field. Temporarily we are using 000000 as the Record ID#. Next a Pipeline wakes up, recognizes that the key field has 000000 contained and it fires to go back and update the key field to its new value.
We need a Pipeline that recognizes the record's creation and fires to write the new formula value into the key field.
It is a lot but the following video goes through the process of setting it up.
We cover topics like this during out daily M-F "Office Hours" webinars held at 1pm Eastern. These are open Q&A sessions where we model possible solutions to business challenges. https://quickbase.com/webinars/.
------------------------------
Kirk Trachy , Senior Solutions Consultant
QuickBase | 603-674-5454 M | ktrachy@quickbase.com
------------------------------
You have come across something which is a little involved but can be done.
Mark was right about the Record ID# not having been created yet so what to do?
Well we can create a formula that concatenates the pieces we wish to put together and then a form rule to fire when the record is created that puts that formula into a local scala field. Temporarily we are using 000000 as the Record ID#. Next a Pipeline wakes up, recognizes that the key field has 000000 contained and it fires to go back and update the key field to its new value.
We need a Pipeline that recognizes the record's creation and fires to write the new formula value into the key field.
It is a lot but the following video goes through the process of setting it up.
We cover topics like this during out daily M-F "Office Hours" webinars held at 1pm Eastern. These are open Q&A sessions where we model possible solutions to business challenges. https://quickbase.com/webinars/.
------------------------------
Kirk Trachy , Senior Solutions Consultant
QuickBase | 603-674-5454 M | ktrachy@quickbase.com
------------------------------
- KirkTrachy15 years agoQuickbase StaffWhen you are adding a record, there has not been a Record ID# created so we have to use a temporary stand in to satisfy that a key field has to be unique. So we concatenated the first 3 letters of the company name with 6 zeros in a formula. When the record is saved a form rule moves that temporary key value into the Key Field. This will remain as the key field until the Pipeline updates it with the new knowledge of the records Record ID#.
Feel free to pop into any of my, "Office Hours" webinars held M-F at 1pm Eastern time and we can discuss further.
------------------------------
Kirk Trachy , Senior Solutions Consultant
QuickBase | 603-674-5454 M | ktrachy@quickbase.com
------------------------------ - AswinBabu5 years agoQrew MemberThis is a good solution. Will try it out--RegardsAswin Babu
Related Content
- 11 months ago
- 5 months ago
- 7 months ago