transfer data from live to development app
I currently have a live app that my company is working with. We needed to make some new changes to the app so I copied our current live app with all of its data to a test app. From here I have made all my necessary upgrades, how can I now transfer my live data into my test app? I want to do this and then just rename my test app to be the functioning one moving forward. Is this the wrong way of doing this? Sorry still quite new at quickbase.
ALM Table-to-Table Imports Alternative Solution
I understand, with ALM activated, table-to-table imports do not work within Automation's. I understand, with ALM activated, I am physically able to go into the configuration for a table-to-table import and manually trigger it. What, if anything, is a valid work around to overcome this issue with ALM activated? I have a number of fields across a number of tables that have two instances for each field - a 'read' and a 'view' - that, based on a users permissions, may get out of sync. Previously, I would run an automated table-to-table import on each table on each occasion a record was added / modified and a trigger was activated. I would also run a catch all table-to-table import across all tables on a daily routine to pick up any mismatches triggered by the rollover to the next day. I have a need to keep ALM activated and work in a sandbox for an extended period. This means currently I am having to go in manually on a daily basis to trigger the table-to-table imports. Frustrating and inefficient. I have played around in Automation's and can see I can trigger what I need to on a single record only basis and only when the trigger is add / modify. Is there anyway I can trigger this on all records for all tables on a daily schedule? Or am I screwed? ------------------------------ Quentin Fleischfresser ------------------------------Pipelines and Sandboxes
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 ------------------------------
General Sandbox Question
For those who have a good amount of experience utilizing the Sandbox feature to make changes to applications, is there any general rule of thumb to how many changes should be made before publishing? Fore instance, I currently have roughly 1900 change lines in the current Sandbox I am working in that have not yet been published. Granted, the live app is not currently being used by the client anyway, but, I feel like that is a lot of changes to be sitting on. Has anyone had issues with changes not transferring correctly for one reason or another? We are currently at a lull between development work, I feel like it is the right time to publish what has been done so far and then start new work with a clean Sandbox so to speak. Any thoughts? ------------------------------ Chris Swirtz ------------------------------
Sandbox Creation Error
Good evening everyone. I'm having issues creating a sandbox tonight. I've utilized them in the past and when I went to create one tonight to test out a new change I want to make, I got the below error and wanted to see if anyone else has seen this. I have tried every different option in sandbox creation with the same result. I am an administrator in the app. Any help would be greatly appreciated. Scott Jones ------------------------------ Scott Jones ------------------------------
The sandbox is not really built for best practices
While I appreciate where this is, there are some glaring issues with the implementation that leave this feature being not able to be used in a manner all IT best practices would recommend. Examples 1) Not being able to select what is promoted or not or selectively undoing a change. While I understand the possible technical issues, having an all or nothing approach is not always appropriate. 2) Having to have all your tables in production. If you want to create a new table and reference values from that table for a drop down in an existing table, you have to promote the table first before you can do that. So basically you have to create all your tables, promote them, and then go and work on any other changes. Hope you have a solid plan because if you need more changes... A sandbox should be self contained and if you have to search into production in order to use it, then it isn't a true sandbox. Are there other gotchas I should be aware of? I was planning on introducing some sub-admins in but am concerned the more I use it that it may not be the option I thought it was. ------------------------------ David Berndt ------------------------------How to create Report Link fields when in Sandbox
I am using a Sandbox app today to make some changes and I can't figure out how to create a Report Link field. When I click on "Select Target", I can't select any of the fields that are only in the sandbox. Is this a bug, or am I missing something? ------------------------------ Forrest Parker ------------------------------Relationships - Sandbox
I am working on major change updates to our application. I am thinking about changing how relationships flow between some of our tables thinking that there is a better way to have them relate to one another. If I change this in the sandbox, when I move over the changes will it cause issues within the application? ------------------------------ Anna Harris ------------------------------
Sandbox publication error?
Hi, I've been working in a sandbox of an app where I added a new lookup in cross-app table relation, a new role, edited some notifications, made a new homepage, some new reports, and had to update some permissions. The app in the sandbox works fine, I am warned when I go to publish that "Note: Data changes and changes made to automations, actions, webhooks, and personal reports will not be published.", when I go to publish the changes, it pops up with a warning box telling me all my changes will be published, but when I click "publish" or "publish and delete sandbox", an error occurs "Failed to publish changes. Try again." I'm not sure why this is happening? Could it be that I made a change in the sandbox that can only be made in the live version? Thanks for any help or information :) ------------------------------ Inas Zadi ------------------------------
