Metadata Document Generator – document data model

Metadata Document Generator(Part of XRMToolbox) saved a lot of my time. I have exported in 30s all atributes (10k+) for selected entities like Account, Contact, Issue (Case), Lead, Opportunity from Dynamics 365 (Online). I believe it is the best possible way to extract metadata, document even complex CRM data model.

Unfortunately out of the box methods for that are not working properly, particularly when it comes to export bulk attributes!

XRM Architects’ team

I was happy to accept invitation to XRM Architects’ team. Please see the whole team: http://www.xrmarchitects.com/meet-the-team/

A designer of CRM / AX technical architecture, Mariusz knows how to deliver a polished and beneficial implementation of Dynamics 365. He can manage the full project lifecycle for any Dynamics 365 project and seamlessly works with us on a temporary basis.  Mariusz works with us on a temporary basis when projects require his specialise skillset.  He is from our Dynamics 365 partners TopOneCRM.

Portal Code Editor

Configuring the Portals for Dynamics 365 could be very complex and time consuming – simply madness. I never gave up, but I believe it should better way to manage this madness these days. Recently Monsier Touzard, the creator of the XrmToolBox, released a new tool called the “Portal Code Editor” to help manage many things in a nice and easy way – Thanks God. It reduced my big effort a lot – well done. It is well structured and useful tool. Indeed a great tool it is and really needed!

More details: https://readyxrmblog.wordpress.com/2017/04/02/xrm-tool-box-portal-code-editor-overview-and-review/

Unit testing is important but… where do I start?

If you have attended the increasingly popular CRM Saturday conference, you probably gained some valuable insights around the key aspects of delivering successful CRM implementations, and how to overcome the main challenges one may face during the implementation.

If not, I encourage you to visit the web site, it has great speakers, great content, and lots of networking opportunities… not to mention is one of the few Dynamics events out there where attendance is 100% free.

Two of the sessions were around test automation and how to implement a true DevOps strategy for Dynamics CRM, two key areas and best practices to increase the overall quality and healthiness of your CRM implementation, which, in turn, would give you the following benefits:

  •     Turning your customers into even more happy customers  (external)
  •     Making your colleagues a bit less stressed because of regression / production bugs will be reduced (internal)

If you are still not convinced about why your team should unit test your code, here’s another blog post with the slides of the test automation presentation.

Once your team realises how important unit testing is, the next immediate question probably is:

  • “Ok, I have an implementation which has been running for years , and I have a bunch of existing code, not tested. At the same time, I have a limited set of resources and trying to unit test everything would be mad… where do I start?”

Ideally, one should achieve a code coverage above 90%, but if you have limited resources, my advice would be: the 80/20 rule.

Try to find the 20% of your code which represents at least the 80% of the total number of executions or executed time, just because if there is a bug in there, then it is likely to affect more users than a piece of code which is executed from time to time only (this might be actually more complex as maybe something than just runs from time to time may have a bigger impact based on a million different variables… but I hope you get the idea).

The next question might be…. how to measure it?

Well, it turns out, from a plugin / codeactivity perspective, you could extract that information from the System Jobs entity rather easily.

Every time a plugin / workflow is executed, a new entry in that table is created, with the Created On, Completed On, fields etc, so you could actually measure how much time a single workflow / plugin execution took. If you have an On-Premise installation, then that is just a SQL query with some groupings, if On-Line, then a data extract plus some Excel manipulation magic should be enough too or… make use of the great Organisation Insights feature in AppSource:

Are you unit testing your code? If so, how did you start unit testing legacy code? Did you use a different approach? We would love to know more about your own experiences.

Please leave a comment below.

www.xrmarchitects.com – Innovation and Excellence in Microsoft

I was happy to accept invitation from Simon Jackson to be an associated CRM/AX Solution Architect with XRM Architects.

The website www.xrmarchitects.com went live and shortly team page will go live as well.  XRM Architects specialise and provide bespoke Microsoft Dynamics 365 solutions. Implementing the right CRM solution first time for the client is a priority for XRM Architects. Getting it wrong is very expensive waste of time and resources, isn’t it ?

I follow Simon’ articles on Linkedin, posts and blogs. I think he really does a great job for CRM community. I was impressed his innovative and interactive blog – well done. His blog was also very informative for me last year. Please look yourself as well – https://crm-musings.blogspot.co.uk/

The readers can even switch between custom views for posts e.g. Flipcard, Mosaic, Sidebar, Snapshot, Timeline. My favourite view is Snapshot – https://crm-musings.blogspot.co.uk/?view=snapshot

Last, but not least I highly recommend to read 11 Top Tips for CRM Success from XRM Architects. There you will find 11 top tips to getting CRM system implementation right the first time.