Skip to main content

XrmToolBox: AutoNumberUpdater - new StateCode filter

Regarding SPFieldMultiLineText (Add HTML/URL content to a field) programmatically

I recently tried so set some HTML content in a SharePoint list column of type SPFieldMultiLineText.

My first approach was this piece of code:

SPFieldMultiLineText field = item.Fields.GetFieldByInternalName("Associated Documents") as SPFieldMultiLineText;

StringBuilder docList = new StringBuilder();
docList.Append("
"); foreach (DataRow docRow in addDocs) { DataRow[] parent = dr.Table.DataSet.Tables[0].Select("DOK_ID=" + docRow["DOK_MGD_ID"].ToString()); if (parent != null && parent.Length > 0) { docList.AppendFormat("{1}", parent[0]["FilePath"].ToString(), parent[0]["Title"].ToString()); } } if (docList.Length > 0) { // remove trailing tag docList.Remove(docList.Length-5, 5); } docList.Append("
"
); string newValue = docList.ToString(); item[field.Title] = newValue;

What this code does is to get all associated documents to the main document and to add these document uri links to the "Associated Documents" column in my custom SharePoint list.

I intended to render the following content in the enhanced rich text field (which works if I enter the content through the SharePoint GUI in the edit form):
<div>
<a target='_blank' href='\\publicshare\docs$\Test1.pdf'>Test 1</a><br/>
<a target='_blank' href='\\publicshare\docs$\Test2.pdf'>Test 2</a><br/>
<a target='_blank' href='\\publicshare\docs$\Test3.pdf'>Test 3</a><br/>
<a target='_blank' href='\\publicshare\docs$\Test4.pdf'>Test 4</a>
</div>

Doing the same via SP object model it will result in the following nasty result:

<div>
<a target=_blank >Test 1</a><br/>
<a target=_blank >Test 2</a><br/>
<a target=_blank >Test 3</a><br/>
<a target=_blank >Test 4</a>
</div>

It drove me nuts because I tried several HTML encode methods or different formatting and nothing helped.
Then after a couple of days and some more gray hairs I got a brilliant idea what could break the A href links of my html source.

I want to point out and talk about the following line:
docList.AppendFormat("{1}
"
, parent[0]["FilePath"].ToString(), parent[0]["Title"].ToString()); Using UNC paths in the href attribute of the "A" tag usually is not a problem. For example you have the following a href tag: <a target='_blank' href='\\share\test.doc'>test doc</a> the browser will render the href url as: file://share/test.doc this behavior also works with a standard SharePoint hyperlink field, except in this scenario To make this whole thing work you must explicitely convert the UNC path to a valid URI path. The following line shows the result which solved this whole issue: docList.AppendFormat("{1}
"
, new Uri(parent[0]["FilePath"].ToString()).AbsoluteUri, parent[0]["Title"].ToString());

Comments

Post a Comment

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete

CRM 2016 SP1: Solution import failed with Solution With Id = 12ac16ec-41d5-1685-a230-0b1c31499250 Does Not Exist

Importing Solutions with the upgrade solution (holding solution) option is still not stable with CRM 2016 SP1 On-Premise. Ronald Lemmon already posted the same issue on his blog: http://ronaldlemmen.blogspot.de/2015/11/solution-with-id-86ac16ec-41d7-4685.html I expected it to be fixed with SP1 but it is still happening every now and then. With this query and the solution id (guid) of the error message you are able to find records in the ProcessTriggerBase table that reference the guid of a failed import from a holding solution that is not existing in the system anymore. select * from ProcessTriggerBase where solutionid = 'YOUR_SOLUTION_GUID' Due to this reference to a solution id not existing in the system you will not be able to import a new version of the target solution to be updated. What I did and this is probably not a supported solution is to update the guid to the actual target solution that is currently deployed in the system. To find out the id of