Your formula suggests to me to that you are in the retail industry and you are rolling out a new
Project to 22 different
Stores and you want to track that process.
There are a ton of problems with your formula including the conceptual problem that you are adding a
[Project ID] value through a
rid parameter for the
API_AddRecord method. There is no
rid parameter for
API_AddRecord, If your formula worked QuickBase was just ignoring the parameter as it has no meaning to the
API_AddRecord. It is hard to see these errors when the formulas are gigantic or poorly formatted. The script solution below is vastly shorter and much more maintainable. As you continue this project you will probably find that there are additional child fields that you may want to initialize based on other fields and criteria. This solution can easily accommodate those future requirements.
When I create a public demo I have to make assumptions to simplify the problem, change some inconsequential details, and construct the demo so I don't have to maintain it in any substantial way.
I created this simple demo that has two tables -
Projects is the parent table and
Stores is the child table.
You are free to click the button to create new
Store records or even a new
Project record. Bear in mind that others may have already clicked on the button and create their own batch of Store records before you created yours.
Store Management Thingyhttps://haversineconsulting.quickbase.com/db/bngmqviemPastie Databasehttps://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=628
