DEVELOPER TRACK

Emmet in Visual Studio Code | cheat sheet link

2021-09-27T11:48:00.003+02:00

Support for Emmet snippets and expansion is built right into Visual Studio Code, no extension required. Emmet 2.0 has support for the majority of the Emmet Actions including expanding Emmet abbreviations and snippets.

Emmet is a web-developer’s toolkit that can greatly improve your HTML & CSS workflow

Links:

Emmet in Visual Studio Code

Cheat Sheet (emmet.io)

Office 365 Developer PnP Core Component Provisioning Engine Tokens

2021-09-24T14:27:00.000+02:00

The SharePoint PnP Core Provisioning Engine supports certain tokens which will be replaced by corresponding values during provisioning. These tokens can be used to make the template site collection independent for instance.

PnP-Sites-Core/ProvisioningEngineTokens.md at master · pnp/PnP-Sites-Core · GitHub

SharePoint 2013 CAML Query Errors

2016-04-18T09:05:00.000+02:00

I got this error while running a CAML Query from a SharePoint 2013 Client application:

System.ArgumentException: Value does not fall within the expected range.

This was happening only in the Prod environment.

One thing that needs to be checked is that in Central Administration > Resource Throttling > List View Lookup Threshold is high enough for all lookup fields in your query:

SPWeb.ParserEnabled property

2015-03-17T11:23:00.002+01:00

When set to TRUE:

when a document is added to a document library, the values of the fields in the list item for the document are added to the metadata properties of the document file.
when you download and upload it again these properties are kept

When set to FALSE:

all of the above is ignored - no custom metadata properties from the library is added to the document when added or uploaded.
the issue comes if you are using sandbox solutions - nothing works anymore since none of the solution properties of the package are set and thus you cannot activate / upgrade any solution.

Powershell: Delete Taxonomy Term

2014-09-30T15:39:00.000+02:00

Delete a Term in a TermStore using PowerShell:

function Delete-SPTerm($SiteUrl, $TermStoreName, $TermName) { Start-SPAssignment -Global try{ $site = Get-SPSite $SiteUrl $session = new-object Microsoft.SharePoint.Taxonomy.TaxonomySession($site) $termstore = $session.TermStores[$termStoreName] $terms= $termstore.GetTerms($termName, $false) if($terms.Count -gt 0){ $terms[0].Delete() $termstore.CommitAll() Write-Host 'Term deleted!' }else{ Write-Host 'Term not found!' } } finally { Stop-SPAssignment -Global } }

Use example:

Delete-GroupTerm -SiteUrl "" -TermStoreName "" -TermName ""

SharePoint 2010 State Machine Workflow error: "Failed to Start Workflow"

2013-11-15T16:18:00.001+01:00

I've been working on a custom state machine workflow for a specific content type. I've associated the workflow to the content type like this:

<AssociationCategories>ContentType;0x01........</AssociationCategories>

This workflow has a custom initiation form, in which I'm passing some options to the workflow.

After doing the association to the content type I started getting the following error: "Failed to Start Workflow"

After doing a bit of debugging and head scratching I found that in the StartListWorkflow() method inside the initiation page in which the workflow association is retrieved from the workflowList.WorkflowAssociations list and it does not take into consideration the ContentType workflow associations.

private void StartListWorkflow()
{

 SPWorkflowAssociation association = this.workflowList.WorkflowAssociations[new Guid(this.associationGuid)];

        this.Web.Site.WorkflowManager.StartWorkflow(workflowListItem, association, GetInitiationData());
 SPUtility.Redirect(this.workflowList.DefaultViewUrl, SPRedirectFlags.UseSource, HttpContext.Current);
}

So I replaced this line:

SPWorkflowAssociation association = this.workflowList.WorkflowAssociations[new Guid(this.associationGuid)];

with this line:

SPWorkflowAssociation association = this.workflowList.ContentTypes[workflowListItem.ContentTypeId].WorkflowAssociations[new Guid(this.associationGuid)];

in which I'm getting looking for the association in the WorkflowAssociations of the list content type of the workflowListItem.

SharePoint 2010 - Enable and configure unique Document IDs

2013-10-10T13:13:00.001+02:00

There is a great article on how to Enable and configure unique Document IDs on Microsoft.com.

In short you need to:

Activate the Document ID site collection feature
Enable and configure the use of Document IDs in a site collection

But what it doesn't mention is that behind the scenes there are two time jobs that need to run to activate this feature: one to add the Document ID column and one to generate unique ids for the existing documents. But, these jobs are set to run once a day.

So if you need your unique Document IDs to be activate right away, you need to go to Central Administration and run these two timer jobs for your respective web application:

Document ID enable/disable job
Document ID assignment job

System.InvalidOperationException: The event receiver context for Workflow is invalid.

2013-09-19T12:19:00.002+02:00

Ever got this error while developing SharePoint 2010 Workflows in Visual Studio?

System.InvalidOperationException: The event receiver context for Workflow is invalid.
at Microsoft.SharePoint.SPEventReceiverDefinition.ValidContext()
at Microsoft.SharePoint.SPEventReceiverDefinition.GetSqlCommandToAddEventReceivers(IList`1 erds)
at Microsoft.SharePoint.Workflow.SPWinOESubscriptionService.CommitNewSubscriptions(Transaction txn, IList`1 erds)

Check the you have set the all the TaskIds in your code:

TaskId = Guid.NewGuid();

If this is not the case need to check that your Correlation Tokens are setup correctly.

SPDisposeCheck for Visual Studio 2012

2013-07-30T09:05:00.004+02:00

Found a great project on CodePlex that allows the creation of an SPDisposeCheck Static Code Analysis Ruleset: http://spdisposecheck2012.codeplex.com

You also have a small video to see how is setup: http://youtu.be/OwiKKYAlXDc

PowerShell script to add work email to the list fields for the author

2013-04-04T09:35:00.001+02:00

The Author (Created By) field is actually an lookup field to the hidden User Information list.

If you need to add the work email of the Author (Created By field) user to a specific list it can be done by adding a dependent lookup field for the Author field:

$site = get-spsite "site url here";
$list = $site.RootWeb.Lists["list name"];

$createdByEmailGuid = $web.Fields.AddDependentLookup("Work e-mail", [Microsoft.SharePoint.SPBuiltInFieldId]::Author);
$createdByEmail = $web.Fields.GetFieldByInternalName($createdByEmailGuid);
$createdByEmail.Description = "Work e-mail address of the Author.";
$createdByEmail.LookupField = $web.Fields[[Microsoft.SharePoint.SPBuiltInFieldId]::EMail].InternalName;
$createdByEmail.Update();
$web.Update();

$list.Fields.Add($createdByEmail);
$list.Update();

If additional fields are needed the same method can be applied. Here is a list of fields that can be added from the User Information list:

- Work e-mail
- Mobile phone
- About me
- Picture
- Department
- Title
- SIP Address
- First name
- Last name
- Work phone
- User name
- Web site
- Ask Me About
- Office

SharePoint 2010 retrieving lookup values using ECMAScript

2013-04-04T09:14:00.002+02:00

Script to retrieve single and multiple value lookup fields values using SharePoint 2010 Client Object Model for JavaScript (ECMAScript):

var listName = "list name here";
var listItemId = 23; // id here

function retrieveLookupValues() {
    var clientContext = new SP.ClientContext.get_current();
    var oList = clientContext.get_web().get_lists().getByTitle(listName);
    var selectedItems = SP.ListOperation.Selection.getSelectedItems();
    var camlQuery = new SP.CamlQuery();
    camlQuery.set_viewXml("< View >< Query >< Where >< Eq >< FieldRef Name='ID' / >< Value Type='Counter'>" + listItemId + "< /Value>< /Eq>< /Where>< /Query>< RowLimit>100< /RowLimit>< /View>");
    this.collListItem = oList.getItems(camlQuery);
    clientContext.load(collListItem, 'Include(CustomSingelLookupFld, CustomMultilLookupFld)');
    clientContext.executeQueryAsync(Function.createDelegate(this, this.onQuerySucceeded), Function.createDelegate(this, this.onQueryFailed));
}

function onQuerySucceeded(sender, args) {
 var listInfo = "";
    var listItemEnumerator = collListItem.getEnumerator();

    while (listItemEnumerator.moveNext()) {
        var oListItem = listItemEnumerator.get_current();
        // get single value LookupField:
        var oCustomSingelLookupFld = oListItem.get_item("CustomSingelLookupFld");
  listInfo += "oCustomSingelLookupFld.Value = " + oCustomSingelLookupFld.get_lookupValue() + " \t oCustomSingelLookupFld.Id = " + oCustomSingelLookupFld.get_lookupId();
  // get multiple value LookupField:
        var oCustomMultilLookupFld = oListItem.get_item("CustomMultilLookupFld");
  for(var ix = 0; ix < oCustomMultilLookupFld.length; ix++){
   listInfo += "oCustomSingelLookupFld[" + ix + "].Value = " + oCustomMultilLookupFld[ix].get_lookupValue() + " \t oCustomSingelLookupFld[" + ix + "].Id = " + oCustomMultilLookupFld[ix].get_lookupId();
  }
    }
 alert(listInfo);
}

function onQueryFailed(sender, args) {
    alert('Request failed. ' + args.get_message());
}

Creating SharePoint 2010 Calculated Field from code in sites with different regional settings

2013-02-04T11:17:00.002+01:00

Say you need to create the following calculated column in different sites that have different regional settings: English, French, etc. to format the DateTime [Start Time] filed to "dd-mm-yyyy".

The following formula would look list this in English - with a comma separator:

=TEXT([Start Time],"dd-mm-yyyy")

Like this in french - with a semicolon separator:

=TEXT([Start Time];"dd-mm-yyyy")

When creating the column from from code behind to treat this the SPWeb.Locale.TextInfo.ListSeparator property must be used to get the correct list separator:

SPList spList = SPContext.Current.Web.Lists["List Title"];
string newFieldName = spList.Add("CalculatedField", SPFieldType.Calculated, false);
SPFieldCalculated newField = (SPFieldCalculated)spList.GetField(newFieldName);
newField.Formula = String.Format(@"=TEXT([Start Time]{0} ""dd-mm-yyyy"")", SPContext.Current.Web.Locale.TextInfo.ListSeparator);
newField.Update();

SharePoint Designer 2010 Reusable Workflows with Lookup Values

2013-01-22T14:18:00.000+01:00

When you create a Reusable Workflow in SharePoint Designer 2010, that uses lookup values, and you try to deploy it in another environment, the lookup values will get broken.

This is happening because the list you are reading the lookup values from has another Guid.

Here is what I came up with to make this deployment easier:

Deploy the reusable workflow in the new environment.
Open the site you have deployed the workflow solution in SharePoint Designer
Go to the related list (List and Libraries > Your Related List Name) and copy the new List ID value.
Go to All Files > Workflows > Your Workflow Name > Your Workflow Name.xoml and open it in SharePoint Designer as XML (right click on it > Open with > SharePoint Designer (Open as XML))
Find an and you will find the old list guid in the ListId attribute
Replace the old guid value with the new one
Save it and close the window.

The workflow should be pointing to the correct list.

Managed Metadata field values are not displayed

2012-11-19T16:33:00.001+01:00

Problem:

The values for a Managed Metadata field values are visible only for Site Collection Administrators.
In edit mode the current and possible values for the Managed Metadata field are visible and accessible.

Solution:

The NT AUTHORITY\Authenticated Users does not have Read permission in the TaxonomyHiddenList.

Check the permissions in <site url>/Lists/TaxonomyHiddenList/AllItems.aspx.
The following permissions should be present:
- NT AUTHORITY\Authenticated Users (NT AUTHORITY\authenticated users) with Read permission
- System Account (SHAREPOINT\system) with Full Control permission

SharePoint 2010 Workflow Activities

2012-08-07T15:30:00.000+02:00

Developing Workflow Activities for SharePoint 2010 examples can be found in a section in Developing Applications for SharePoint 2010 from MSDN.

This section is under Execution Models in SharePoint 2010 > Reference Implementation: Workflow Activities.

The code for the entire section can be found here: Developing Applications for SharePoint 2010.

SharePoint 2010 put back the "Set Up Groups for this Site" link

2012-07-25T08:20:00.002+02:00

The "Set Up Groups for this Site" page has been, for some unknown reason, hidden in SharePoint 2010.

The page is still there and it can be accessed here:/_layouts/permsetup.aspx.

To make this generally available I created a custom action to add this to the "People and Groups: All Groups" (/_layouts/groups.aspx) page, in the Settings dropdown menu:


xml version="1.0" encoding="utf-8"?>
< Elements xmlns="http://schemas.microsoft.com/sharepoint/" >
  < CustomAction Id="64f25e2b-f9fb-4e37-b848-5949603b03ab"
                Title="Set Up Groups for this Site"
                Description="Use this page to specify who can access your site. You can create new SharePoint groups or re-use existing SharePoint groups."
                Location="Microsoft.SharePoint.GroupsPage"
                GroupId="SettingsMenu"
                Sequence="1000"
                >
    < UrlAction Url="~site/_layouts/permsetup.aspx">< /UrlAction>
  < /CustomAction >
< /Elements >

This can a Site or Web level feature, depending on where it has to be applied.

How to create a custom Workflow Task / SharePoint Server Workflow Task content type using Visual Studio?

2012-07-17T14:00:00.000+02:00

If you are designing an Workflow and you want to create custom Workflow Task or SharePoint Server Workflow Task using Visual Studio interface then you'll need to make these two content types visible.

To make them visible I'm using the following PowerShell script:

$site = Get-SPSite "http://site/url/here"
$web = $site.RootWeb

# Workflow Task
$contentType = $web.ContentTypes["Workflow Task"]
$contentType.Group = "Custom Content Types"
$contentType.Hidden = $FALSE
$contentType.Update()

# SharePoint Server Workflow Task
$contentType = $web.ContentTypes["SharePoint Server Workflow Task"]
$contentType.Group = "Custom Content Types"
$contentType.Hidden = $FALSE
$contentType.Update()

$site.Dispose()

Then when you can add a new Content Type from Visual Studio and you will see the two Content Type in the list.

To revert these changes run this PowerShell script:

$site = Get-SPSite "http://site/url/here" $web = $site.RootWeb # Workflow Task $contentType = $web.ContentTypes["Workflow Task"] $contentType.Group = "_Hidden" $contentType.Hidden = $TRUE $contentType.Update() # SharePoint Server Workflow Task $contentType = $web.ContentTypes["SharePoint Server Workflow Task"] $contentType.Group = "_Hidden" $contentType.Hidden = $TRUE $contentType.Update() $site.Dispose()

SharePoint 2010 Customizing default application pages

2012-06-18T16:40:00.000+02:00

Customizing an SharePoint 2010 Application Page.

In this example I'm customizing the /_layouts/MWS.aspx, the new meeting workspace page.

These steps can be followed for any of Application Page.

1. Create the custom application page and deploy it into the _layouts folder.

2. Create an IHttpModule to redirect all requests that come to MWS.aspx and redirect them to customMWS.aspx:

class RedirectModule : IHttpModule { public void Dispose(){ } public void Init(HttpApplication context) { // add event handler context.PreRequestHandlerExecute += context_PreRequestHandlerExecute; } void context_PreRequestHandlerExecute(object sender, EventArgs e) { HttpApplication httpApp = sender as HttpApplication; HttpContext context = httpApp.Context; string httpUrl = context.Request.RawUrl.ToString(); //compare our URL and redirect it to custom one if (httpUrl.ToLower().Contains("/_layouts/customMWS.aspx")) { HttpContext.Current.Server.ClearError(); HttpContext.Current.Response.Clear(); HttpContext.Current.Response.Redirect(Regex.Replace(httpUrl, "/_layouts/newMWS.aspx", "/_layouts/customMWS.aspx", RegexOptions.IgnoreCase)); } } }

3. Add a new element in the web.config configuration/system.webServer/modules section to enable this IHttpModule. To do this create an web application feature to add this change in the web.config of the application.

public class MWSRedirectModuleFeature : SPFeatureReceiver {
 SPWebConfigModification webConfigModification = new SPWebConfigModification
 {
  Name = "add[@name='MWSRedirectModule']",
  Path = "configuration/system.webServer/modules",
  Owner = "CustomOwner",
  Sequence = 100,
  Type = SPWebConfigModification.SPWebConfigModificationType.EnsureChildNode,
  Value = "Class Name, Assembly Full Name"/>"
 };

 // Add config changes
 public override void FeatureActivated(SPFeatureReceiverProperties properties)
 {
  SPWebApplication parent = (SPWebApplication)properties.Feature.Parent;

  if (parent == null)
   return;

  try
  {
   parent.WebConfigModifications.Add(webConfigModification);
   parent.Update(true);
   parent.WebService.ApplyWebConfigModifications();
  }
  catch (Exception exception)
  {
   // log error
  }
 }

 // Remove config changes
 public override void FeatureDeactivating(SPFeatureReceiverProperties properties)
 {
  SPWebApplication parent = (SPWebApplication)properties.Feature.Parent;

  if (parent == null)
   return;

  try
  {
   parent.WebConfigModifications.Remove(webConfigModification);
   parent.Update(true);
   parent.WebService.ApplyWebConfigModifications();
  }
  catch (Exception exception)
  {
   // log error
  }
 }
}

SharePoint 2010 Custom List / Library Template: Custom Action are not displayed in the Ribbon

2012-04-27T10:14:00.002+02:00

Issue:

We have Custom List / Document Library Template - the Custom Action are not displayed in the Ribbon.

Solution:

Check that all views in the list template have the Toolbar tag inside it with type "Standard":

< Toolbar Type="Standard" / >

To fix for existing lists / libraries:

1. Change the source file in the Visual Studio solution and redeploy it.

OR

2. If the solution cannot be redeployed then to fix existing lists / libraries follow these steps:
- Open the site in SharePoint Designer
- Open the Views in Edit Mode and add/update the following tag inside the View tag:

How to deloy InfoPath 2010 "Administrator-approved form template" to SharePoint 2010 programaticaly

2012-03-22T15:05:00.007+01:00

Scenario: you've developed and InfoPath 2010 form. This form contains code that requires full trust, so you need to deploy it as a administrator-approved form template.

This requires an farm administrator to check, upload and activate the form for the site collection.

Solution: to automate this operation I created a farm level feature - when the feature is activated upload the form programmatically and when the feature is deactivated remove the form programmatically.

Here is how I did it:

1. Create an Empty SharePoint Project and set it to be deployed as a farm solution

2. Add an Empty element item - EmptyElement1. This will also generate a feature - Feature1

3. Delete the Elements.xml file of the EmptyElement1

4. Copy/Paste the InfoPath 2010 form into the EmptyElement1

5. Right click on the added form and click Properties:

- Deployment Type: ElementFile

- Deployment Location> Path: set it to blank

6. Open the generated feature, Feature1

7. Set the scope to Farm level and save it

8. Right click on the feature and select "Add Event Receiver"

9. Comment out the FeatureActivated and FeatureDeactivating methods

10. Add the following code to the FeatureActivated method to upload the form:

SPSecurity.RunWithElevatedPrivileges(() =>

{

SPFarm localFarm = SPFarm.Local;

FormsService localFormsService;

string solutionPath = properties.Definition.RootDirectory + @"\Form.xsn";

try

{

localFormsService = localFarm.Services.GetValue(FormsService.ServiceName);

localFormsService.FormTemplates.UploadFormTemplate(solutionPath);

}

catch (Exception ex) {

// Handle exception Here

}

});

10. Add the following code to the FeatureDeactivating method to remove the form:

SPSecurity.RunWithElevatedPrivileges(() =>

{

SPFarm localFarm = SPFarm.Local;

FormsService localFormsService;

string solutionPath = properties.Definition.RootDirectory + @"\Form.xsn";

try

{

localFormsService = localFarm.Services.GetValue(FormsService.ServiceName);

FormTemplate formTemplateToRemove = (from formTemplates in localFormsService.FormTemplates

where formTemplates.DisplayName == "Form"

select formTemplates).Single();

localFormsService.FormTemplates.RemoveFormTemplate(formTemplateToRemove);

}

catch (Exception ex) {

// Handle exception Here

}

});

11. Build and deploy the solution.

That is it!

Note that you need to reference the Microsoft.Office.InfoPath.Server.dll. This is usually located here: C:\Program Files\Microsoft Office Servers\14.0\Bin\

Oversized buttons in IE

2009-01-26T20:54:00.012+01:00

Yeah ... just another problem with IE.

Lucky for all of us there are some people that can hack their way through the IE bugs.

Here is a fix for this problem:

input.button {
  padding: 0.25em;
  width: 0;
  overflow:visible;
}
input.button[class] { /*ie ignores [class]*/
  width: auto;
}

postgresql altering column type

2008-02-06T20:46:00.001+01:00

ever had to change the column type and run into trouble?

well here is what I found as far:

* postgresql 7.4 ( and lower I think ) - cannot be done with the ALTER TABLE command, and then you have to do something like this:

BEGIN;
ALTER TABLE <table name> ADD COLUMN <new column> <new data type>;
UPDATE table SET <new column> = CAST(<old column> AS <new data type>);
ALTER TABLE <table> DROP COLUMN <old column>;
COMMIT;
VACUUM FULL <table>;

VACUUM FULL tab to reclaim the disk space used by the expired rows
( for more detailed information go here)

* postgresql 8.0 ( and higher ) - has implemented the ALTER TABLE ALTER COLUMN command and you have to do something like this:

ALTER TABLE <table name> ALTER COLUMN <column name> TYPE <new type> USING <column name>::<new type>;

( for more detailed information go here)