Pipeline Simultaneous Multiple and Single Record Creation Ideas
Hi, I am working on a workflow solution and am struggling to solve a problem. Hoping someone in the community who has a bit more experience with pipelines may have a (relatively) straightforward so...
Would it be at all practical to have a button either on the A record or the B record which would be visible in view mode (not grid edit) which would copy the A record and ALL its children and immediately land the user on the New A with its duplicated children. Then the user would use the checkbox on the embedded report to delete the unwanted children?
------------------------------ Mark Shnier (YQC) mark.shnier@gmail.com ------------------------------
Thanks for taking the time to look at this and I appreciate the alternate solution idea. It is a possibility. We don't allow the end user's to delete records, though I am looking to build in a cancel/remove button functionality which would operate in the same way as what you are getting at.
For my app, it would probably make most sense to have that button on the A record. My concern with a button is for it to finish running the copy/recreate before landing them on the newly created A record. How do you envision this button workflow operating? Would it trigger a pipeline? I'm familiar with both a formula and pipeline solution based on what you are getting at so you can just give me a relatively high-level idea. But as I mentioned, based on my past experiences I'm concerned about the runtime.
One way would be to use the built in Copy Master Detail wizard button maker which is located on the App Management page. This can also be done with a URL
Select Copy the "Project" or whatever your A table is called and then just specify which relationship you want children copied. Post back if you get stuck.
As for deleting, you could have a checkbox called deletion requested, and then a Pipeline run when that field was checked and perhaps some other conditions were true such as the date created = date modified of the parent record (meaning that the parent had never been edited, or perhaps only for children created today.
------------------------------ Mark Shnier (YQC) mark.shnier@gmail.com ------------------------------
Mark, maybe off topic, happy to create a different post on this... but have you had any success implementing the "copy master detail" process into a pipeline? I've been picking away at it and can't seem to make it work; this thread jogged my memory.
What I'm trying to do, is copy an existing record with children, and apply it to a new parent record. I have a button launching a miniform, select the child to copy. This triggers a pipeline which will in theory copy master detail, then find that new record, and change a few fields to relate it to the new parent.
I'm trying to use the QuickbaseAPI -> Make request as shown, hacking up the parts of the generated code to attempt to get the end result. Pipeline runs successfully, but no new record is created...Thoughts/advice?
------------------------------ Jeremy Myer ------------------------------
What I'm trying to do, is copy an existing record with children, and apply it to a new parent record.
I don't understand about the parent record. Which process is creating the new parent record, the copy master detail or is the user creating the parent manually and they want to copy children from another Parent. Why can't you just use a regular copy master detail formula URL button to do this?
------------------------------ Mark Shnier (YQC) mark.shnier@gmail.com ------------------------------
ah no, you cannot blank out fields on the fly with that API. It's not ab supported parameter. You would need to trigger a pipeline to blank out the fields. But it would need to know that the children records were auto created somehow so it knew which ones to blank out.
------------------------------ Mark Shnier (YQC) mark.shnier@gmail.com ------------------------------
