Forum Discussion

CurtisMiddleto1's avatar
CurtisMiddleto1
Qrew Cadet
3 years ago

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...
APIs and custom code
Button
Pipelines
CurtisMiddleto1's avatar
CurtisMiddleto1
Qrew Cadet
3 years ago
To add to this, an idea I had was to have it search A records for an existing record by the end user that would meet certain criteria and if it found one, then to not create a new record. Just not sure how that look from a functional standpoint in pipelines and if that would add a significant amount of run time if it was doing that a dozen times. Though, not sure if there is a more efficient way to implement that.

------------------------------
Curtis Middleton
------------------------------
  • MarkShnier__You's avatar
    MarkShnier__You
    Icon for Qrew Legend rankQrew Legend
    3 years ago
    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
    ------------------------------
    • CurtisMiddleto1's avatar
      CurtisMiddleto1
      Qrew Cadet
      3 years ago
      Hey Mark,

      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.

      Thank you!

      ------------------------------
      Curtis Middleton
      ------------------------------
      • MarkShnier__You's avatar
        MarkShnier__You
        Icon for Qrew Legend rankQrew Legend
        3 years ago
        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
        ------------------------------