https:\/\/mycrm.crmcs.co.uk\/main.aspx?etn=opportunity&pagetype=entityrecord<\/strong><\/a><\/p><\/blockquote>\n\n\n\n Opening this link will then directly browse into the New Opportunity Form which can be a handy time-saving technique as we could then embed this link into an Intranet or Dashboard to make CRM quicker (and so easier) to use for the end user.<\/p>\n\n\n\n However the real strength of this is the ability to not only open the Opportunity but provide a URL Link which pre-populates certain Fields on the Form.<\/p>\n\n\n\n So we might provide a Link that creates a New Opportunity pre-populated to a particular Customer and\/or Opportunity Type.<\/p>\n\n\n\n We can do this adding an additional element to the URL for \u2018extraqs\u2019 \u2013 so if looked at a basic example of pre-populating the Name of the Opportunity:<\/p>\n\n\n\n https:\/\/mycrm.crmcs.co.uk\/main.aspx?etn=opportunity&pagetype=entityrecord&extraqs=name%3DMyOpportunity<\/strong><\/a><\/p><\/blockquote>\n\n\n\n This will then prepopulate the \u2018name\u2019 field with \u2018My Opportunity\u2019.<\/p>\n\n\n\n We can then extend this to include multiple parameters using the same %3D Request String format, alongside separating %26 to separate out the parameters<\/p>\n\n\n\n https:\/\/mycrm.crmcs.co.uk\/main.aspx?etn=opportunity&pagetype=entityrecord&extraqs=name%3DMyOpportunity<\/strong>%26description%3DExampleDescription<\/strong><\/a><\/p><\/blockquote>\n\n\n\n Obviously the difficult part here is the %3d and %26 \u2018tagging\u2019 characters to handle breaks in our Parameters \u2013 these are corresponding to the & and = characters within the \u2018extraqs\u2019 parameter itself, but make for a difficult URL when it comes to try to human-read what is going on.<\/p>\n\n\n\n This is using HTML Encoding to handle the \u2018extraqs\u2019 parameter as a part within the wider Request String. The following link gives more context on this ability to Encode a URL using this % notation as way of handling non-standard characters without confusing the Web Browser:<\/p>\n\n\n\n https:\/\/www.w3schools.com\/tags\/ref_urlencode.asp<\/strong><\/a> <\/strong><\/p><\/blockquote>\n\n\n\n Obviously this concept of % characters to replace certain characters does not lead itself to typing up human readable URLs, and so to try and make life easier for ourselves, we can look at using a Spreadsheet Excel Formula to build this link for us:<\/p>\n\n\n\n This can then use the SUBSTITUTE Excel Formula to encode our Name\/Value Parameters into the right encoding for the URL.<\/p>\n\n\n\n We this freedom, we can look at adding various parameters for our URL and look at how we can add Lookup, Option Set and Custom fields to our URL.<\/p>\n\n\n\n For Option Sets and Custom Fields, this is quite simple as these follow the same format.<\/p>\n\n\n\n For Lookups however, we need to supply the other 2 elements that CRM tracks for each Lookup: the .Name<\/strong> and .Type<\/strong> attributes of the Lookup alongside the code .Id<\/strong>.<\/p>\n\n\n\n So we need to pass our request as lookupid={xxx-xxx-xxx}&lookupidname=RecordName&lookupidtype=RecordType<\/strong> which adds some complexity when working with Lookup fields \u2013 however we can work this complexity into our Excel Formula to limit our thinking-time here:<\/p>\n\n\n\n Which then results in passing a more complex set of starting values to our New Opportunity:<\/p>\n\n\n\n Now we have this URL, we can embed this within an Email or Web Page to provide a better User Experience for the End User in potentially giving them a quick link to create a Gap-Fill Opportunity for a particular Customer or with a particular set of starting values.<\/p>\n\n\n\n This is great for a quick static URL, however if we took this principle into a more Web Application point-of-view then we could look at how our Application Code could potentially generate this URL on the fly to give various dynamics URLs at run time for the Entity and Attributes we want \u2013 essentially replacing the Spreadsheet here with our own code-behind logic.<\/p>\n\n\n\n The advantage we have here is that we can use a method in the core .NET Framework to handle the URL Encode for us, instead of relying on an Excel Formula.<\/p>\n\n\n\n \/\/ build our string of useful parameters<\/p>\n\n\n\n string parameterString = “name=New Business Opportunity&”;<\/p>\n\n\n\n parameterString += “description=Please chase this opportunity and update your notes accordigly&”;<\/p>\n\n\n\n parameterString += “new_businesstype=267040002&”;<\/p>\n\n\n\n parameterString += “customerid={81403A53-6D8C-E511-80BC-00155D05198A}&customeridname=Land and New Homes&customeridtype=account”;<\/p>\n\n\n\n \/\/ build the end-url<\/p>\n\n\n\n string urlOpenNewFormInCRM = @”https:\/\/mycrm.crmcs.co.uk\/main.aspx?etn=opportunity&pagetype=entityrecord&extraqs=” + Server.UrlEncode(parameterString)<\/strong>;<\/p>\n\n\n\n \/\/ build hyperlink and add into the page<\/p>\n\n\n\n HyperLink linkOpenNewFormInCRM = new HyperLink();<\/p>\n\n\n\n linkOpenNewFormInCRM.NavigateUrl = urlOpenNewFormInCRM;<\/p>\n\n\n\n This gives a more Development-heavy method of achieving the same result as our Formula-based Spreadsheet, which can be handy if developing a custom link to embed in a Webpage, Dashboard or Email.<\/p>\n\n\n\n This ability to provide CRM URL Links that open particular Forms can very useful to tailor the End User Experience and so is embedded throughout CRM \u2013 not just for Entity Forms, but also for Advanced Finds, Views and even allowing entirely different Forms to be opened for an Entity Form. (so we could have a link to open Form Type A for a Record, and a separate link to open Form Type B for a record)<\/p>\n\n\n\n The following article from Microsoft\u2019s MSDN expands on this concept and gives the finer detail on how these URL Links work within Dynamics CRM:<\/p>\n\n\n\n Open Forms, Views, Dialogs and Reports with a URL<\/strong><\/p>![\"image\"](\"https:\/\/license.citruslime.com\/cs\/blogs\/crmcs\/image_17F1F6A7.png\" "\\"image\\"")
<\/figure>\n\n\n\n![\"image\"](\"https:\/\/license.citruslime.com\/cs\/blogs\/crmcs\/image_4573166A.png\" "\\"image\\"")
<\/figure>\n\n\n\n![\"image\"](\"https:\/\/license.citruslime.com\/cs\/blogs\/crmcs\/image_37349D7A.png\" "\\"image\\"")
<\/figure>\n\n\n\n![\"image\"](\"https:\/\/license.citruslime.com\/cs\/blogs\/crmcs\/image_3DE7A6FD.png\" "\\"image\\"")
<\/figure>\n\n\n\n![\"image\"](\"https:\/\/license.citruslime.com\/cs\/blogs\/crmcs\/image_449AB080.png\" "\\"image\\"")
<\/figure>\n\n\n\n
![\"image\"](\"https:\/\/license.citruslime.com\/cs\/blogs\/crmcs\/image_6F731492.png\" "\\"image\\"")
<\/figure>\n\n\n\n