PU39: managing your ISV licenses wisely

 


We all know there is a drastic change in licensing, as introduced as a part of architectural change in PU39. The official documentation mentions support for SHA1 until was till February 2024, and then you can migrate to SHA256. When generating a license using the AxUtil tool, you need to use signature version 2 or leave this field blank to generate a new license using SHA256 . This change applies to new versions starting from 10.0.39. You need to upgrade the system version to implement feature updates. Typically, software updates and features are designed for specific versions, and it is recommended to upgrade to the target version.

You need keep in mind few things, while applying the licenses you get from your ISV partners.

Option A: 

When you get the patch (the patch ZIP file, compatible with PU39) from your ISV partner, make sure you do this, before you apply the patch to your environments.

Step 1:

You need to get the license files from your partner first. They are typically text files, and you need to copy the patch Zip file to your Dev VM --> Open it --> navigate to \\AOSService\\Scripts folder. Here you can create a folder called: License folder and copy the files to this location.


Step 2:

Upload this new version of the ZIP file to LCS>> Asset library, apply it to your target instance.

This will eventually apply the license to your instance, you can verify the necessary ISV modules, check if all the menu items are opening successfully. Additionaly you can cross verify the SYSCONFIG table: the access codes will get successfully updated with the new license codes, owing to this. 


Option B:

Alternately, you can copy the license files to your source code of your DEV branch. And then After applying the patch from LCS, changes will be available here as Pending changes. You can now check in the pending changes, they will flow through your pipeline, to your 'one deployable package'.



Don't forget to update your 'Add Licenses to your deployable package', as mentioned in one of my previous blogs:

https://www.blogger.com/blog/post/edit/2520883737187850604/537830883472598151





Failure to do this, will give you an error ssaying: leaf node not found.

Comments

Post a Comment

Popular posts from this blog

X++ : mistakes which developers commit the most

Image
   The most important thing is to remember where and when to write the code. a. Developers have an inherent habit of writing erratic select statements: select * from custTable where custTable.AccountNum == <SomeValue> Where in essence we need to make use of optimized choice of fields in the select statement. b. Making use of 'continue' keywords: While select custTrans where <someConditions> { if (cusTTrans.CustGroup != mappingTable.CustGroup) { continue; } } 'Continue' statements are precisely a very unhygienic way of designing your code. The above statement could have been easily ornamented by using exists/not exists joins. Using Continue statements would eventually result in a high performance impact. Also select statements should be made punctuated with a 'firstonly' clause -- just not from best practise standpoint, but also from performance considerations. c. Writing nested loops: This is a common mistake that perha
Read more

Make your menu items visible on main menu, conditionally,, using this cool feature of D365FO

Image
  Wassup guys? I am sure you must have encountered this situation where you needed to display your menuItems, on main menu, based on some condition, haven't you? This was only possible by using config keys and flights. Things get a bit tricky,  when suppose you have a requirement like this: you need to make it dynamic, by introducing a toggle switch on a field on a paremeter form.  Suppose on Accounts Receivables Parameters >> You have a field called ' Show US customer '. You have a requirement that says when you turn on this toggle, then only the menuItem ' Input SSN details ', under AR module. This is now highly acheivable by leveraging subscription to 'SysMenuNavigationObjectFactory' class, simply by saying a. Create a new class USMenuItemsVisibilityManager b. Copy the following method, with proper documentation (don't change signature/anything else) [SubscribesTo(classstr(SysMenuNavigationObjectFactory), staticdelegatestr(SysMenuNavigationObjec
Read more

Speed up your execution performance by using SysGlobalCaches

Image
  Ever come across a situation where you needed to  a. Using a multi-threaded batch to import a journal header and lines, from a staging table. The table already contains the Journal Ids which you need to assign to the header and allocate the lines under that header. b. You need to continuously check after each line being imported, if the journal with the Id has been created. If not, it will create the header and create the lines under it;  If yes, it will directly create the lines for the header (Find or create). c. As you could rightly guess, this architecture has an inherent sluggishness associated with it -- each time you keep on checking if the header has been created or not, it does mean a lot of performance effects, as a consequence. Also as you can understand it's a multithreaded code, which means each thread has no direct relation with the other -- which does mean there is no way I can talk between the threads/pass on any information. SysGlobalCaches to the rescue: I perso
Read more