Hi, it would be great to have workspaces on the table and connectors level only. Then in situation like this when we push the data from ERP to Tulip Tables we can actually work on one app and have the app revision control in check but also quickly switch between TEST and Production Data. Now you can only setup the connection type only on the connector level which in cases like this is not sufficient because I still works on Production tables. Only option is to export/import app but then I`m facing another known issues with queries and aggregation being duplicated. So having possibility to setup workspaces only on Table and Connector levels would solve most of our issues.
Hi Jacek, thanks for sharing this! To make sure I understand your situation, are you currently using Workspaces to represent dev, test and prod environments as part of the app rollout process?
Additionally, have you tried using Development Mode in order to prevent the updates of production tables? Or do you need to persist the data from your testing sessions?
@kevin.kononenko Development Mode is a really poor alternative to multiple databases, primarily due to the fact that aggregations do not work in Dev Mode. A large majority of applications which are complex enough to require testing also use aggregations.