Import data from production files
planned
Charlie Bailey
Another use case for this feature: let’s say I’m working on a feature that requires a data model change and as part of my push to production, I need to run a post migration script to transform my data to adapt to the new model. If I can copy my files from production to testing and then migrate from dev to testing, I can test my data transformation process with production data.
David Wollesen
planned
Saransh Pachhai
Great one !!!
Charlie Bailey
The typical workflow would be to copy your production files to a testing environment, then migrate from dev to testing.
David Wollesen
Charlie Bailey: Thank you for your input. Flows like these, with more actions, will be a central part an upcoming "Pipelines" feature that will most likely ship with 1.1 or 1.2.
David Wollesen
under review
David Wollesen
Sounds like something that would be usefull for many bug fixes! Tim Anderson do you think this could be completely avoided/mitigated if better logging was implemented? We intent to provide a Logging API in the future which could feed several types of logs directly into a reports/insights/metrics interface that could provide an overview of live and historic logs by company, user, timestamp, module version etc.
T
Tim Anderson
David Wollesen: not for me! There are always things users do that are tricky to reproduce. I remember I had issues with 1 particular client who pasted text in from many different sources. The invisible characters caused many issues that I could not reproduce from my data entry
David Wollesen
Tim Anderson: True, and even vast application logging would not fetch interactions like copy/pasting. Thanks for the example 👍
We'll let this request stay a bit and see if attracts more attention before reviewing it in detail.