Separate Database for Preview and Publish Environments
This video will help you understand how to work between databases for different environments such as Preview and Publish. All the test data created during building/developing the no-code app and while testing it stays in the preview database collection. Live users of your application will not see the dummy or the junk data. This way you can do as much testing as needed without impacting the end users and they will only see the real/actual data which is meant for them.
The Separate Database for Preview and Publish Environments feature in DrapCode allows users to maintain distinct databases for testing (preview) and live (publish) environments. This functionality ensures that changes can be tested safely without affecting production data, enhancing development workflow and minimizing errors. By keeping preview and published data separate, users can maintain data integrity and deploy updates confidently.
For seamless data management, explore Update Collection Field Values Without Collection Form to learn how to modify collection field values without using a form. This feature provides greater flexibility in updating records programmatically or through automated processes.
Development and testing becomes much easier this way on DrapCode.
Find new videos here -
Displaying the Filtered Data of Current Logged In User
External API Response in Data Table without Storing Data
Custom Sentence Derived Fields
Please feel free to reach out to us on support@dracode.com for any questions that you may have.