We would like to specify during merging (or, if necessary, during an upgrade) that data migrations should be squashed. Now this has to be done manually after merging a branch, and if forgotten, data could be lost. If this can be specified with a check mark in the merge session, which is on by default, that would be nice. It could also possibly be done at the start of an upgrade, but the preference for us is before the merge session.
+23Hi Bram, the execution of a merge session does do a Squash data migration - in the merge from branch but indeed not in the target branch. We like the idea!
Snippet from the Execute merge session task:
+23New→Open
+23Hi
We have revised the way data migration is squashed in 2025.1. Now, when you generate your data migration, the squash is automatically done. During the execution of the merge session, source branch data migration is squashed to ensure the mappings are correctly added in the target branch.
After merging, once you start upgrading your application, the data migration is generated and the data migration is squashed, effectively solving your wish. Do you agree with me and can we set the status to Completed?
"Wake me up before you low-code"
1 person likes this
+23Open→Needs feedback
- Warrior
- 37 replies
Hi, we haven't upgraded to 2025.1 yet. We have it scheduled for next week. I'll inform you once I've had the opportunity to test it.
1 person likes this
+9Hi
Unless you're already using version 2025.1 and it's clearly not working as expected, I suggest we close this idea.
+9Needs feedback→Closed
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.