Forum Discussion
MarkShnier__You
Qrew Champion
You can create a record by using the API for API_AddRecord, and I can help you with the syntax for that once I understand your work flow.
You are sitting on a child record. So via lookups, a child can know any fields from the Parent and they can be used by the API. So you click and create a parent record and then what? Where do you want to land the user and does the child you are sitting on need to get attached to the new parent?
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
You are sitting on a child record. So via lookups, a child can know any fields from the Parent and they can be used by the API. So you click and create a parent record and then what? Where do you want to land the user and does the child you are sitting on need to get attached to the new parent?
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
JeremyCohen
5 years agoQrew Member
Hey Mark,
Sorry for the delayed response.
I would be sitting in the child record and need to initiate a new parent record. The two do not need to tie together. The system I am integrating with through csv reads each change as an individual record so it would be a new line for every addition or subtraction. The user just needs to initiate the new record being generated.
The user will be in the form of the child. This is why I was leaning towards a url button. I was just having a hard way to go with how to replicate a parent record associated to the child form and then make a few minor alterations to that record so that it is unique.
The attachment will happen more external to the system than internal.
------------------------------
Jeremy Cohen
------------------------------
Sorry for the delayed response.
I would be sitting in the child record and need to initiate a new parent record. The two do not need to tie together. The system I am integrating with through csv reads each change as an individual record so it would be a new line for every addition or subtraction. The user just needs to initiate the new record being generated.
The user will be in the form of the child. This is why I was leaning towards a url button. I was just having a hard way to go with how to replicate a parent record associated to the child form and then make a few minor alterations to that record so that it is unique.
The attachment will happen more external to the system than internal.
------------------------------
Jeremy Cohen
------------------------------
- MarkShnier__You5 years agoQrew ChampionIf you want to create a parent record and land the user on the patent record, the formula would be
URLRoot() & "db/" & [_DBID of the Table name from Advanced Properties]
& "?act=API_AddRecord"
& "apptoken=xxxxxxxxxxxx" // you need this line if you have left th3 app to require Application tokens
& "&_fid_7=" & URLEncode([some text field])
& "&_fid_8=" & ToText([some numeric field])
& "&displayrec=1"
I have put an app in the exchange called URL formulas for dummies which can help you with some of the syntax. There is also the API guide which describes the different API calls.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------- JeremyCohen5 years agoQrew MemberHey Mark,
That works for just adding a record. So your saying I should just create lookup fields for every possible field I need when it is related and then use the url to simply add a new record...i guess that would be a much simpler approach to it.
In that case any fields I'm changing due to the conditional I could just tie directly to the fid....I'll try the approach. Thank you very much for the help Mark!
------------------------------
Jeremy Cohen
------------------------------- MarkShnier__You5 years agoQrew ChampionExactly, your initial thinking was way overthinking what was required. It's just the API to ADD a record and the only complexity is where to land the user after the button is pushed.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------