We're switching to using pipelines and need to be able to create a sandbox where pipelines will work in the same way as the live application so that changes can be tested before implementation. I've read that 'A sandbox does not support tracking or publishing changes to automations, actions and webhooks' (see Sandbox limitations and details). Does that mean when a sandbox is created, automations, actions and webhooks won't work on the sandbox? Pipelines aren't mentioned here, but I guess they are likely affected in the same way. If pipelines won't work in the sandbox (which I guess is the likely situation) could we create copies of our pipelines and search/replace DBIDs between the export and import to point them to the sandbox?We're likely to make changes in several iterations and I wondered if the DBIDs from the second sandbox would be different from those in the first sandbox (meaning we'd need to repeat this exercise every time we created a sandbox). Has anyone tried this (or have a better suggestion) before we try it out?Thanks.------------------------------Jeremy Anson------------------------------

I'm quite sure that Pipelines won't automatically copy when an application is copied but you can export the pipeline in a format called YAML. You can then edit the DBIDs and upload the YAML to make a new Pipeline. But I actually have no idea whether that will work for an application that is in the sandbox.------------------------------Mark Shnier (YQC)Quick Base Solution ProviderYour Quick Base Coachhttp://QuickBaseCoach.commark.shnier@gmail.com------------------------------

Thanks Mark.Having carried out some brief testing it looks like pipelines don't work for the sandboxed application.Each time a sandbox is created a new set of DBIDs are generated, so testing in the sandbox with pipelines active would seem to involve:1. Creating a token for the sandbox (as the token for the live application doesn't provide access to the sandbox).2. For every table referenced in pipelines, retrieving the new DBIDs from the sandbox.3. Mapping these to the DBIDs in the live application.4. Exporting the YAML for the pipelines.5. Replacing DBIDs.6. Replacing references to the token.7. Modifying the name of the pipeline to distinguish it from the original.8. Importing the YAML.I'm not sure if it's possible to derive the 7 character alphanumeric reference to the token that appears in the YAML without - as I did - creating another pipeline and exported the YAML from that, so there's possibly another step to add. ------------------------------Jeremy Anson------------------------------

I have never actually done it myself. You may need to get some help from Support. It's a whole New World of YAML and Slugs.------------------------------Mark Shnier (YQC)Quick Base Solution ProviderYour Quick Base Coachhttp://QuickBaseCoach.commark.shnier@gmail.com------------------------------

If anyone is wondering what a Slug is, it's not a snail that eats the lettuce in your gardenhttps://community.quickbase.com/blogs/bree-mackey1/2020/04/27/importing-pipeline-yaml------------------------------Mark Shnier (YQC)Quick Base Solution ProviderYour Quick Base Coachhttp://QuickBaseCoach.commark.shnier@gmail.com------------------------------

Pipelines and Sandboxes | Qrew Discussions

10 Replies

MarkShnier__You
Qrew Legend
4 years ago
I'm quite sure that Pipelines won't automatically copy when an application is copied but you can export the pipeline in a format called YAML. You can then edit the DBIDs and upload the YAML to make a new Pipeline.

But I actually have no idea whether that will work for an application that is in the sandbox.

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
- JeremyAnson
  Qrew Cadet
  4 years ago
  Thanks Mark.
  
  Having carried out some brief testing it looks like pipelines don't work for the sandboxed application.
  
  Each time a sandbox is created a new set of DBIDs are generated, so testing in the sandbox with pipelines active would seem to involve:
  1. Creating a token for the sandbox (as the token for the live application doesn't provide access to the sandbox).
  2. For every table referenced in pipelines, retrieving the new DBIDs from the sandbox.
  3. Mapping these to the DBIDs in the live application.
  4. Exporting the YAML for the pipelines.
  5. Replacing DBIDs.
  6. Replacing references to the token.
  7. Modifying the name of the pipeline to distinguish it from the original.
  8. Importing the YAML.
  
  I'm not sure if it's possible to derive the 7 character alphanumeric reference to the token that appears in the YAML without - as I did - creating another pipeline and exported the YAML from that, so there's possibly another step to add.
  
  ------------------------------
  Jeremy Anson
  ------------------------------
  - MarkShnier__You
    Qrew Legend
    4 years ago
    I have never actually done it myself. You may need to get some help from Support. It's a whole New World of YAML and Slugs.
    
    ------------------------------
    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach
    http://QuickBaseCoach.com
    mark.shnier@gmail.com
    ------------------------------
AustinK
Qrew Commander
4 years ago
The best way to do this, imo, is to not use the sandbox feature. Sandbox is nice for many things but it has some big limitations like this. Create a copy of your app and test on that and then when you are sure it is working as intended change the app the Pipeline is sending information to to the production version. This is how we have been doing it because of the issues you mentioned.
- JeremyAnson
  Qrew Cadet
  4 years ago
  Thanks Austin. This is the approach we've decided on for now and it's good to see that others have reached the same conclusion.
  
  ------------------------------
  Jeremy Anson
  ------------------------------
- BibhavRimal
  Qrew Trainee
  2 years ago
  Anything I should take into consideration before creating the copy of an app? Do all the automations get copied when I create the copy of an app or do I have to recreate all of them?
  
  ------------------------------
  Bibhav Rimal
  ------------------------------
  - MarkShnier__You
    Qrew Legend
    2 years ago
    Pipelines do not copy.
    
    Automations do not copy.
    
    Saved table to table imports do not copy properly because the source table will be from the old app.
    
    Your URL formula buttons will work if you have properly constructed them, but if you constructed any URL formula buttons where the table references hardcoded, then it will fail because it will refer to the old app.
    
    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------

Forum Discussion

Pipelines and Sandboxes