Skip to main content

Notifications

Dynamics 365 Community / Forums / Finance forum / Service Update merged ...
Finance forum
Answered

Service Update merged with Application AOT update from new enivronment

Posted on by 450
Hello,
 
We can read this advice in the Microsoft Documenation
“Make sure that the application binary update package is applied to your dev/build environment AFTER it is applied to your sandbox and production environment
- If the application binary package is applied on your dev/build environment and this raises the platform build version to be higher than your target sandbox or production environment, you will be blocked from applying any AOT packages that are produced from this dev/build environment. To apply AOT packages produced from a dev/build environment, your dev/build instance must be equal to or lower than your target environments.”

At https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/migration-upgrade/update-guide?context=%2Fdynamics365%2Fcontext%2Ffinance#runtime-compatibility we read:

“All Microsoft updates are intended to be runtime backward-compatible. This compatibility covers both binary compatibility and functional compatibility. Runtime compatibility means that customizations that exist in production and sandbox environments will continue to work after Microsoft service updates are deployed to those environments. Those updates include service updates and quality updates. Runtime compatibility also means that Microsoft updates are backward-compatible with customizations that were compiled on an earlier platform.

Binary compatibility is backward only. You can compile a customization on an older application version and platform version, and deploy it to an environment that is running a later version. However, you can't deploy code to an environment that is running a version that is earlier than the version that the code was compiled on.“

 

So.. this means if I'm running 10.0.35, and I create a new cloud hosted development environment at 10.0.39, update my code, create a Software Deployable Package there, and deploy it to my preproduction and then production environments running 10.0.31, I should receive an error saying I can not do so due te the above warnings.

 

BUT... when I am doing a Service Update with my Code update it seems I can do my Application AOT code updates (with ISV Code updates to 10.0.39 in this example) and merge the Service Update SDP (10.0.39 from 10.0.35) with the Application SDP created on a 10.0.39 application version cloud hosted environment.

 

Do I have this right? Any explanation for this behaviour?

 

Any insights would be appreciated. Thanks so much!

  • jt1024 Profile Picture
    jt1024 450 on at
    Service Update merged with Application AOT update from new enivronment
    Hello Navneeth,
     
    Thanks for your time in posting a reply to my question.
     
    As a side point, I see you commented on using TFVC All the training I did on MS Learn talked about using TFVC, and our site started out that way.  I haven't seen any MSFT documentation for D365 development pointing people to Git. 
     
    Is there any MSFT documentation pointing to using GIT for D365 finance development?
     
    - Jim
  • Suggested answer
    Navneeth Nagrajan Profile Picture
    Navneeth Nagrajan 1,225 on at
    Service Update merged with Application AOT update from new enivronment
    Hi jt1024,
     
    Faced this issue. This issue usually occurs if we update the higher environment and merge code onto a lower version environment. It tends to create binary update conflicts. In this case, the version 10.0.39 is applied to a higher environment and later, the code has been merged onto a 10.0.35 environment. Instead, its better to update the dev and the build environment to 10.0.39 and bring it equivalent to the higher environment and then perform the code merge. 
     
    Also, it looks like you are using TFVC in this case as the source control which is going to pose some challenges.
     
    Happy to answer questions, if any.
  • Verified answer
    Andre Arnaud de Calavon Profile Picture
    Andre Arnaud de Cal... 283,405 Super User on at
    Service Update merged with Application AOT update from new enivronment
    Hi jt1024,
     
    Yes when you apply a Microsoft service update, it will bring the environment to 10.0.39 and you can then also directly apply the latest customizations.
    It should not work if you have an SDP created on 10.0.39 and update your environment to Microsoft version 10.0.38. 
  • jt1024 Profile Picture
    jt1024 450 on at
    Service Update merged with Application AOT update from new enivronment
    Hello Andre, Anthony,
     
    Thank-you both for your time in replying to my question.
     
    Andre: what I was confused at was this: I can create a 10.0.39 dev and build environments. Build my code and SDP there. Merge that with the Service Update package from my 10.0.35 Service update list of hotfixes. That service update brings the MSFT code from 10.0.35 to 10.0.39. 
     
    The merged package was successfully used to update my preproduction environment, and then I was able to select that applied update, sign off, Mark as Release candidate and apply that to update our production environment from 10.0.35 to 10.0.39.
     
    But if I was doing just a custom code feature update, and I did that from 10.0.39 build environment, I would not be able to apply that to 10.0.35 environment for the reasons you and microsoft describe.
     
    Anthony: The build environment was at 10.0.39, sequence use as described above.
     
    Lastly, I did try building the new ISV code with our custome code on a 10.0.35 environment, and tried to merge that with the Service Update package from my 10.0.35 Service update list of hotfixes. That service update brings the MSFT code from 10.0.35 to 10.0.39. This fails to merge since they are from different platform versions.
     
    So overall the difference between service updating and just updating your custom work seems to be that you can apply something built on a newer environment over older version when doing a service update, but not for just updating your custom code.
     
    Do I have that right?
  • Suggested answer
    Anthony Blake Profile Picture
    Anthony Blake 870 on at
    Service Update merged with Application AOT update from new enivronment
    hi jt1024
     
    Are you creating the deployable package on your dev environment or via a build pipeline?
     
    The reason I ask - if you updated a dev environment, and all build correctly, but the deployable package is created via a Pipeline using a build environment or an azure hosted build, the built package will still be build using the old binaries, is 10.0.35, unless the build environment or the build nugets are update to 10.0.39. If the build environment is creating a 10.0.35 or even 10.0.31 version of your package as it has not been updated, backwards compatibility still works.
     
    Summary - have you updated your build Artifacts or Build box?
     
     
     
  • Andre Arnaud de Calavon Profile Picture
    Andre Arnaud de Cal... 283,405 Super User on at
    Service Update merged with Application AOT update from new enivronment
    Hi jt1024,
     
    You can deploy custom deployable packages on the same version and higher versions compared to the environment used for the build. If the customization package is created on 10.0.35, you can deploy that to an environment running on 10.0.35 and above. So yes, you can merge the single deployable package from 10.0.35 with a service update 10.0.39. 

Helpful resources

Quick Links

Upcoming TechTalk: Copilot Capabilities…

Review the Copilot features that are currently available in Dynamics 365 Finance…

Demystifying Copilot: Service Edition with Sundar Raghavan

Sundar answers more questions about Copilot for Service...

Dynamics 365 Business Central vs Finance and SCM

Take a look at the key differences between Business Central and…

Leaderboard

#1
Andre Arnaud de Calavon Profile Picture

Andre Arnaud de Cal... 283,405 Super User

#2
Martin Dráb Profile Picture

Martin Dráb 223,370 Super User

#3
nmaenpaa Profile Picture

nmaenpaa 101,140

Featured topics

Product updates

Dynamics 365 release plans