Creating Revision form in quickbase
Dear Quickbase Solver, I have a problem that i need to solve in my organization. We have form Purchase that already establish and i need to make a revision purchase form in it. For example, Pu...
Forum Discussion
There is an app in the QuickBase Exchange entitled, "ABC Customer Updates their own Records".
https://login.quickbase.com/db/main?a=AppDetail&ID=3368&app_name=ABC%20Customer%20Updates%20Their%20Own%20Records
It uses EOTI (Everyone on the internet) to update child records with new updates. Upon saving a Pipeline edits the original record.
1. Someone fills out a form.
2. They get an email with an update button.
3. The person wants to update so they press the button. The button has embedded in it all the details they originally submitted.
4. When they press the button it fills out the form with everything known. This gives people the option to edit the known data or add to it.
5. Upon saving, a QuickBase Pipeline fires to update the original record.
6. Because the update table is a child of the original submission form, it naturally keeps a record of all the changes.
There is a video on the dashboard of the application that goes over the theory behind this.
We cover topics like this during out daily (M-F) "Office Hours" webinars held each weekday at 1:00PM Eastern. All are welcome.
------------------------------
Kirk Trachy , Senior Solutions Consultant
QuickBase | 603-674-5454 M | ktrachy@quickbase.com
------------------------------
https://login.quickbase.com/db/main?a=AppDetail&ID=3368&app_name=ABC%20Customer%20Updates%20Their%20Own%20Records
It uses EOTI (Everyone on the internet) to update child records with new updates. Upon saving a Pipeline edits the original record.
1. Someone fills out a form.
2. They get an email with an update button.
3. The person wants to update so they press the button. The button has embedded in it all the details they originally submitted.
4. When they press the button it fills out the form with everything known. This gives people the option to edit the known data or add to it.
5. Upon saving, a QuickBase Pipeline fires to update the original record.
6. Because the update table is a child of the original submission form, it naturally keeps a record of all the changes.
There is a video on the dashboard of the application that goes over the theory behind this.
We cover topics like this during out daily (M-F) "Office Hours" webinars held each weekday at 1:00PM Eastern. All are welcome.
------------------------------
Kirk Trachy , Senior Solutions Consultant
QuickBase | 603-674-5454 M | ktrachy@quickbase.com
------------------------------
