As I’ve been fairly active pushing for transactions and commenting on the forums, github issues and pull requests, it’s worth mentioning that my company decided to migrate away from Strapi due to this issue and the slowness with which it’s been followed up on.
We’ve waited near 3-4 months for some sort of resolution and have tried to help in whatever way we can given our own constraints but nothing’s been done and we’ve decided to just move away from Strapi. Despite the fact that it was a crucial feature for many users, transactions hasn’t been treated as such by the team. There are other issues we’ve had with Strapi besides this but this convinced us that it wasn’t worth waiting for a patch for this and that we might as well just bite the bullet and move to more reliable packages. It took us about a quarter of the time this issue has taken to fully migrate our backend to prisma, next and trpc and our experience with these has been substantially faster, more reliable and just a better DX overall.
Given my personal experience, if you’re using Strapi for anything more than a simple blog or other simple usecases and if you have the time and resources to move away Strapi, I would strongly advise it. Strapi has been the weakest part of our stack and has held up development for one reason or another all year. The migration to v4 was a nightmare and given a lot of the mistakes made, I can’t imagine the migration to v5 will be much more pleasant. After we switched to prisma, next serverless functions and trpc for our backend, we got almost all the same functionality but faster and less error prone. Best of luck to those waiting on this feature and I hope the team prioritises features that are needed by a minority of users over features wanted by a majority.