Applied patches from your ISV partner, but have you checked out the following steps?

 


We always have ISVs involved in most of our implementations. They too have their own cycles for ALMs, they too send across patches, updates, bug fixes and extensions. Then how do we tackle them?



The above figure has a Dev branch where all your developers work, a Main branch which in turn is the gateway to higher environments, and an ISV branch to handle your ISV team's ALMs.

a. The easiest way here is that we keep ISVs on a separate branch (let us call it ISV branch). We ask our ISV teams to deploy their changes out there. How to deploy their changes, is completely up to them, but mostly the easiest way to do this is to apply the package from LCS. The changes will automatically start showing as pending changes in the ISV branch.

What are these changes be like: just compiled bin files. You log on to the dev VM that is mapped to this ISV branch.

b. Check it into your ISV branch by tagging it into a pre-created DevOps task/Workitem and then noting the changeset thus created. Additionally, you might need to add the files manually by right-clicking on the ISV's folder that contains the code >> Add Items to Folder:


This will open the following pop-up:


Select Bin and click on Next to see if there are any left-out files. Also, check on the 'Excluded' tab and right-click on any files (if any) >> Include them >> Next >> Finish.

This would create all the Pending changes onto one file for changeset.

c. The next part is easy. Now you can come to your Main Branch and then Merge from your Source Branch (ISV) to Target (Main) and select the changeset that you obtained from the above step to go ahead.

This will ensure that no Bin files have been left behind and no unwanted situation is arising on higher environments when your functional/client team is trying to test something on the ISV solution.

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