Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 302 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Business Central on Cloud (SaaS) - Sandbox vs Production Version
YA_BF
Member Posts: 7
Hi all,
We are currently working with a client who uses Business Central SaaS with GB Localization. We were asked for some development from our customer which we did via AL extensions and published to Sandbox successfully. At this point, both our Sandbox and Production where Version 14.
In the mean time, a couple of days have passed until the customer did some UAT and approved our customisation and now we're ready to go live. The issue is that in the meantime, the sandbox environment has been automatically upgraded to Version15. When we went in the sandbox, our extension was no longer there so we re-published it successfully to the sandbox.
But now, since our production is still on version 14, can we upload the .app package of the sandbox extension (on version 15) to production? Or shall production be upgraded to version 15, first?
Any help is appreciated as this is the first time we found ourselves in such situation
Thanks in advance!
We are currently working with a client who uses Business Central SaaS with GB Localization. We were asked for some development from our customer which we did via AL extensions and published to Sandbox successfully. At this point, both our Sandbox and Production where Version 14.
In the mean time, a couple of days have passed until the customer did some UAT and approved our customisation and now we're ready to go live. The issue is that in the meantime, the sandbox environment has been automatically upgraded to Version15. When we went in the sandbox, our extension was no longer there so we re-published it successfully to the sandbox.
But now, since our production is still on version 14, can we upload the .app package of the sandbox extension (on version 15) to production? Or shall production be upgraded to version 15, first?
Any help is appreciated as this is the first time we found ourselves in such situation
Thanks in advance!
0
Answers
I think that you can publish the app in production now, reading your post seems like you don't made any modification to the app before publish it in the sandbox on version 15 and it is the same app published in the sandbox in version 14.
The apps published in sanboxes are deleted when the sandbox is updated to a new version, in production that doesn't happen.
Regards.
One other small question please ... so my app.json looks like this at the moment for the extension published in sandbox. Will this be OK, please? as I see that the version is 15 for the Base App.
Thanks again!
Did you change anything in this file before re-published the app in the Sanbox v15 ?
Regards
No, just re-published and authenticated again...
In this case the platform must to be the same (15) in production and the SandBox. maybe there is a difference in the minor version (15.x).
So there is not a problem publishing your app in production.
Regards