What are the Slack Archives?
It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hey guys, is it possible to switch (for old orders) the fk_oms_order_process on spy_sales_order_item
Hey guys,
is it possible to switch (for old orders) the fk_oms_order_process on spy_sales_order_item manually in db to the latest oms order process? We have atm the problem that we introduced a new state machine and now we want to use it also for maybe the last 60 days of old orders. Or is this not a good idea and something will break here?
Comments
-
Hey Julian! It depends a lot on the diff between your 2 state machines. Usually new version of SM is introduced, when you introduce some non-backward-compatible changes to your order-related data or the way you process your orders.
I don’t see an issue changing the version manually, as soon as you’re 100% sure that the old (60 days) orders can be processed with the new state machine:
• all the data is complete
• there won’t be issues with other external systems
• old order items are not in the states that no longer exist in a new process.0 -
be very careful though
0 -
Hey Andriy, thanks for the feedback. We completely splitted up the old oms into many sub oms and use them into the others. Additionally we added state changes from the erp like shipment delivery note or automatically partial refund for paypal and credit card also from erp. Since we offer 60 days of return for our customer, it would be nice that its possible to automatically refund old orders too and not only the one started from todays deployment. So the easiest way for us would be to move the old orders to the new oms. Another way would be to process old refunds via external command but no info within the oms states and we have to create the command first
0 -
Ok, we updated it via DB, everything seems fine
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 75 Spryker News
- 921 Developer Corner
- 781 Spryker Development
- 88 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 34 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 25 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random