SharePoint 2013 QuickLinksMicroView webpart and MyLinks hidden list – How To Use them

A quick tip on how to use the MyLinks list in SharePoint 2013 which is “hidden”.

To access the list you have to use a “back door”. Type after your mysite address the following aspx location:

To add a link to add a new link list item to the location mentioned above you can use the following JavaScript and HTML to create such an action(you can do this from anywhere in SharePoint):

<script type=”text/javascript”>

function displayLayover(url) {

var options = SP.UI.$create_DialogOptions();

options.url = url;

options.dialogReturnValueCallback = Function.createDelegate(

null, null);



<a href=”javascript:displayLayover(‘/_layouts/QuickLinksDialogForm.aspx?Mode=Link’)”>Add Item </a>

The above code will create a modal dialog pointing to the specified list, mylinks list.


If you want more functionality related to the MyLinks just open the aspx page in the SharePoint hive and hack it :).

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS

  • myquicklinks.aspx
  • quicklinksdialogform.aspx

The above add link in the aspx page can be found with this line of JavaScript:

function CreateNewQuickLink()
ShowNewQuicklinkPopup(‘QuickLinksDialogForm.aspx?Mode=Link’, PageRefreshOnDialogClose);

When you are ready you can add the QuickLinksMicroView -webpart anywhere and it will instantly show the links in your MyLinks list.

“The Records Center is not properly configured for this request” Error when sending a document to record center

This problem was annoying because of SharePoint lousy error messages that make no sense.

In my case the issue was the existence of two front-end machines which sites did not point to each other correctly. What I had to do was to configure the hosts file(C:\Windows\System32\drivers\etc\hosts) for each site to properly point to from one server to another. Initially in this environment only one server was pointing correctly to the other server but not the other.

This problem is of course limited when testing from the server machines themselves.

Enterprise Keywords field, Custom metadata fields and a bunch of errors

“The SPListItem being updated was not retrieved with all taxonomy fields.”


If you encounter the error above while trying to enable Enterprise Keywords field to a document library and adding a custom metadata field then the solution to this is the following(It’s a workaround, not sure the main reason why this happens, to me it happened in a record center):

Before you do anything related to the Enterprise Keywords field first add your custom metadata field THEN, only then do what you need to do and add the Enterprise Keywords functionality.

For some weird reason in my case no matter what I did I got the above error. Please notice that the above error can also happen if your metadata field does not have any connection to a term set. This problem was very annoying no matter what the situation was.

IIS Express and Android Studio connection issues

If you are getting a following like error when you are trying to connect to a Microsoft Web Service or whatever server point that is under IIS Express you might encounter the following error:

failed to connect to / (port “Your port number here”): connect failed: ECONNREFUSED (Connection refused)

The error above is due to a loopback problem. What you need to do is do some configurations.

  1. Find your applicationhost.config file under your documents(usually): C:\Users\”Your account name here”\Documents\IISExpress\config
  2. Then find your web service binding information see the example below(the sample in the green color, the red color binding is what is by default configured).
  3. Add the IP address and the port to which you want to connect at from android studio. The IP address has to be your development machines IP address.
  4. Also you need to add new rules to your windows firewall that allows your ports through which you wish the connection to be done.
  5. You may need to run Visual Studio in Administrator mode


<site name=”MyFitnessTrackerWebAPI(1)” id=”17″>
<application path=”/” applicationPool=”Clr4IntegratedAppPool”>
<virtualDirectory path=”/” physicalPath=”C:\Users\Adrian Simionescu\Dropbox\MyFitnessTracker\MyFitnessTrackerWebAPI\MyFitnessTrackerWebAPI” />
<binding protocol=”http” bindingInformation=”*:52797:localhost” />
<binding protocol=”http” bindingInformation=”*:80:″ />
<binding protocol=”http” bindingInformation=”*:52797:″ />


After this when you start up your webservice you should be able to access your service by address or host name. Also your IIS Express hosting information should look something in the this direction(based on the configuration above):

IIS express configurations