Blog

27 02, 2018

Implementing Microsoft Dynamics 365 for Finance and Operations – Book review

By |2020-03-23T13:49:16+01:00February 27th, 2018|Categories: AX 7, Dynamics 365 for Finance and Operations|Tags: , |1 Comment

It has been very busy times in the past couple of weeks, by doing the preparation steps for our upgrade to Dynamics 365 for Finance and Operations at JJ Food Service. As you can imagine it is not an easy task with an AX system that has been running for 11+ years, upgraded for every major version since 3.0 with a 2TB+ database size. As the Technical architect and with no partner involved I needed to understand all the components, challenges to be expected, processes to be completed in order to carry out a successful move to the cloud. Fortunately I have received an editorial copy of Implementing Microsoft Dynamics 365 for Finance and Operations.

Implementing Microsoft Dynamics 365 for Finance and Operations
Implementing Microsoft Dynamics 365 for Finance and Operations

First of all I really like the idea that the book starts with an introduction of the various Dynamics 365 products and reporting/data management tools, since Microsoft’s intention is to bundle together different applications in the cloud via a subscription-model. This gives a great overview of the available tools. One point to mention here is that CRM has been split up and compartmentalized as different, smaller applications. This is the direction where Dynamics AX is heading as well eventually.

The Implementing Microsoft Dynamics 365 for Finance and Operations book is also touching up on Application Lifecycle Management (ALM), through the utilization of LifeCycle Services (LCS) portal. This is what we use for managing and architecting our environments, going through the project implementation, mapping our business processes, deploying data packages and releasing code.

Since the book is aimed at audience like myself, technical architects with a strong development background, I have found this book to be an excellent resource for getting into the nooks and crannies of using Visual Studio for development, VSTS for version control, walking through the various major changes like ditching AIF for RESTful API, JSON and OData.

I also really like that the book touches up on the automated testing part, which is very much neglected in most implementation projects. I would expect that it would change in the future, forcing customers and partners to provide testing in some form before code could be applied in a Production instance with a certain code coverage threshold met.

All-in-all I found the details very well summarized in the book, and is a great starting point to build essential knowledge for a new AX 7 implementation project. The rest could be filled in by reaching out to the extensive Microsoft Docs site as a detailed technical and user manual, if you need more insight into the various areas.

26 09, 2017

Microsoft CEO Satya Nadella releases Hit Refresh

By |2017-09-26T12:57:45+02:00September 26th, 2017|Categories: Microsoft Dynamics AX|Tags: , , |1 Comment

It is common to see CEO’s releasing books about the steps they took in the past to build a successful company, but is uncommon to find someone who is sharing their vision and approach on what steps are they taking today, to shape a better future. Satya Nadella, chairman of Microsoft is inviting us for a journey about rediscovering the soul of one of the largest IT corporate in the world in his new book, Hit Refresh.

Read his post about the book in the making on LinkedIn:

https://www.linkedin.com/pulse/writing-hit-refresh-satya-nadella

Available in stores:

Hit Refresh

25 09, 2017

Microsoft Ignite Live stream for 2017

By |2017-09-25T19:49:16+02:00September 25th, 2017|Categories: Microsoft Dynamics AX|Tags: , |0 Comments

The replacement conference for Convergence is already taking place in Orlando, USA. In case you are not able to be there in person, you may check many interesting sessions on-demand, and you could tune in to the Microsoft Ignite Live stream online:

Microsoft Ignite Live stream

Microsoft Ignite 2017

I can recommend to check the keynote at least, featuring Satya Nadella among other industry professionals.

 

3 08, 2017

Microsoft MVP Award 2017 for Business Solutions

By |2017-08-03T11:48:35+02:00August 3rd, 2017|Categories: Microsoft Dynamics AX|Tags: |2 Comments

I have been awarded the Microsoft Most Valuable Professional (MVP) title for the 2017-2018 cycle. Being a Microsoft MVP is a recognition that only a handful of people within the Dynamics AX family have received. It is a great honor to be ranked among the bloggers, community volunteers, speakers and experts that I have been learning from for the past 15 years and have met at various projects, events and conferences.

Microsoft MVP

As a Microsoft MVP by getting more networking opportunities and access to the product teams it is becoming easier to share relevant, fresh content, exchange information with the professionals in the industry, and keep a finger on the pulse of new trends for Satya’s vision about business transformation.

This is giving an additional kick and motivation for releasing additional publications, and doing more community and conference participation.

See you guys around!

20 07, 2017

Add call stack to InfoLog messages

By |2020-03-23T13:50:07+01:00July 20th, 2017|Categories: AX 2012|Tags: , , , , , , |0 Comments

The main communication channel for our ERP users in case we want to tell them something is via the InfoLog messages within Microsoft Dynamics AX. In case we get an error or a warning, the technical staff does not receive the details required to troubleshoot the issue much easier. In this post I would like to show you how to send the X++ or .Net CIL call stack to InfoLog messages.
Microsoft already has an article on this for AX 2009, but that was before the AX 2012 IL code execution for server-side code, so it needs slight adjustments.

https://blogs.msdn.microsoft.com/axsupport/2010/08/02/how-to-send-the-callstack-to-the-infolog/

My changes got the following improvements:

  • Can handle X++ and CIL execution.
  • Users only see the call stack when clicking the message line due to filling it with whitespace.
  • Specific users could be excluded from receiving the call stack, we are doing this for our service accounts such as the batch execution account. We are also excluding our eCommerce portal customers from seeing a call stack, which are the Claims-based users.
  • Current database server/name and user account is included in the message, in case we are storing the errors in the Event log and would like to know who had the problem.

Here is the example output:

call stack to InfoLog
(more…)
Go to Top