Skip to main content
Question

Pipelines and Sandboxes

  • July 3, 2021
  • 0 replies
  • 338 views
Forum|alt.badge.img+7
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
------------------------------
This topic has been closed for replies.

MarkShnierYou
Forum|alt.badge.img+22
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
------------------------------
Mark Shnier. Your Quickbase Coach
  • AustinK
  • Registered
  • July 8, 2021
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.
Terms & ConditionsAccessibility statement