Tip #320: You have it all backward (compatible)

Backward compatibility is taken by CRM team very seriously. Another good example of this, sometimes insane, compatibility is how CRM treats URLs. The ability to open any form or view in CRM 4.0, and also dialogs, reports and dashboards in CRM Online and CRM 201x is an awesome way to create mashups, and for an external application or a website (think SharePoint, for example) to access CRM records without spending a fortune on creating custom UI.

To create new account in CRM 4.0, all you had to do is to link to the following URL: https://foobar.crm.dynamics.com/SFA/accts/edit.aspx. In CRM Online and CRM 201x, however, URLs have changed and now you need to send unsuspecting user to https://foobar.crm.dynamics.com/main.aspx?etn=account&pagetype=entityrecord. But guess what happens if your legacy integration code uses former URL but new CRM organization? That’s right, user will get redirected to the latter URL and will be able to create a new account record just as before.

When you deal with Dynamics CRM using documented SDK methods and techniques, your code can live forever.

Hats off.

2 thoughts on “Tip #320: You have it all backward (compatible)

  1. Chevva says:

    Will my code, written against documented SDK methods against CRM V4.0 still work against 2016?

    • Hey Chevva,

      we were talking about addressable URL compatibility, not the code. CRM v4 code won’t work against 2016 because of the changed endpoint (2007 -> 2011) and support for 2007 endpoint has been deprecated long time ago.

      Moving forward I would recommend using Web API as 2011 endpoint was deprecated in the latest release of Dynamics 365


Leave a Reply

Your email address will not be published. Required fields are marked *