SharePoint Online Event handlers are deployed as Remote Event Receiver (RER), which uses the client-side object model (CSOM).  Hence, the typical even race that happens when you have a code logic to update some property in ItemAdded/ItemUpdated will recursively trigger the ItemUpdated event.  Since, it’s CSOM, the server side event disabling is not available.  The only workaround to resolve this issue is to have conditional checks when ItemAdded/ItemUpdated event occurs.  The most robust way I’ve seen it works is to programmatically disassociate and re-associate the event receivers when it’s not required to be fired.

The remote event receivers are mostly deployed as WCF service where it could be handled correctly.  Below is the code snippet that I’ve used which works to resolve the event receiver issue:

SPRemoteEventResult IRemoteEventService.ProcessEvent(SPRemoteEventProperties properties)
        {
            SPRemoteEventResult result = new SPRemoteEventResult();
            switch (properties.EventType)
            {
                case SPRemoteEventType.ItemAdded:
                    try
                    {
                        ManageUpdateEventHandler(properties.ItemEventProperties.WebUrl, false);
                        HandleItemAdded(properties);
                    }
                    finally
                    {
                        ManageUpdateEventHandler(properties.ItemEventProperties.WebUrl, true);
                    }
                    break;
                case SPRemoteEventType.ItemUpdated:
                    try
                    {
                        ManageUpdateEventHandler(properties.ItemEventProperties.WebUrl, false);
                        HandleItemUpdated(properties);
                    }
                    finally
                    {
                        ManageUpdateEventHandler(properties.ItemEventProperties.WebUrl, true);
                    }
                    break;
                case SPRemoteEventType.ItemCheckedIn:
                    HandleItemCheckedin(properties);
                    break;
            }
            return result;
        }

private void ManageUpdateEventHandler(string webUrl, bool enable)
{
    Guid eventReceiverId = Guid.Empty ;
    using(ClientContext context = CreateClientContextUsingAdminToken(webUrl))
    {
        if(context!=null)
        {
            List sourceList= context.Web.Lists.GetByTitle("<List Title>");
            context.Load(sourceList, a => a.EventReceivers);
            context.ExecuteQuery();

            for (int c = 0; c < sourceList.EventReceivers.Count; c++)
            {
                if (sourceList.EventReceivers[c].ReceiverName.Equals("<receiver name>"))
                {
                    eventReceiverId = sourceList.EventReceivers[c].ReceiverId;
                    break;
                }
            }

            if(enable)
            {
                if(eventReceiverId==Guid.Empty)
                {
                    EventReceiverDefinitionCreationInformation itemUpdatedEvent = new EventReceiverDefinitionCreationInformation();
                    itemUpdatedEvent .EventType = EventReceiverType.ItemUpdated;
                    itemUpdatedEvent .ReceiverUrl = ConfigurationManager.AppSettings.Get("RemoteEventReceiverURL");
                    itemUpdatedEvent .ReceiverName = "<receiver name>";
                    itemUpdatedEvent .Synchronization = EventReceiverSynchronization.Synchronous;

                    sourceList.EventReceivers.Add(itemUpdatedEvent );
                    context.ExecuteQuery();
                }
            }
            else
            {
                if(eventReceiverId!=Guid.Empty)
                {
                    sourceList.EventReceivers.GetById(eventReceiverId).DeleteObject();
                    sourceList.Update();
                    context.ExecuteQuery();
                }
            }
        }
    }
}

1. Lotus Notes Database = SharePoint Lists
2. Views = SharePoint List View
3. Forms = SharePoint List Forms / InfoPath Forms
4. Lotus Notes Scripts/Agents = C# code-behind

For data migration, there are lot of third-party tools available to read it from Lotus Notes DB to SharePoint lists.  The most commonly used and efficiently used one is CASAHL.  Before doing the data migration, the source data in Lotus Notes DB should be cleansed thoroughly and ensure data consistency to match the target SharePoint list schema, as Lotus Notes DB manage data in well-defined schema.  Another thing to remember is, since Lotus Notes is a thick client application, for a geographically distributed organizations, the users might have entered data in different time zone & currency values for the same DB column.  Just a quick pointers before you start thinking of migrating....

So, for example if you've signed up your Windows Phone with a Microsoft account (Hotmail, live, msn, etc.), after which if you've set a new alias using Outlook.com, then make sure your old email address to which the Facebook services is connected is set as primary email alias.

    - Insufficient privileges to SQL Server
    - Administrator on the Sharepoint Server
    - Part of the WSS_ADMIN_WPG
    - Farm Administrator
    - The Application Pool (for WSS Site and Central Admin) uses the same user

After ensuring everything in the above list, still it throws the same exception.  Then, I changed my target platform in project properties to x64, as my DEV machine is 64 bit, then everything worked perfect.  So, if you’ve a 64 bit machine please change your target platform to either x64 or “Any CPU”, which will resolve this issue.

Please refer the slam.codeplex.com for more details.

Are you tired of handling dirty characters in SharePoint such as “_x0020_, _x002f,… “ etc ?  Suppose if you know what to be done, then please ignore this post.  I was breaking my heads to find a solution for this, even without knowing there is a API method to handle this…

Yes, this can encoded/decoded using the respective methods below:

XmlConvert.EncodeName = converts all the special characters to equivalent _x00xx_

XmlConvert.DecodeName = converts all the _x00xx_ back to the special characters.

I’ve recently used the Accordion menu in Silverlight for one of my UI.  I’m pretty much amazed with the efficiency of this control in saving lot of screen real estate and at the same time having lots of controls packed into it.  I’m posting this to share the same with others, on using this Accordion menu.  Please follow the steps below:

1. Download the Silverlight 4 Toolkit from https://silverlight.codeplex.com/releases/view/43528
2. Install the toolkit in the development box
3. Add System.Windows.Controls.Layout.Toolkit assembly reference
4. Add the namespace reference for "https://schemas.microsoft.com/winfx/2006/xaml/presentation/toolkit” in xaml with a prefix
5. Add the following code to have Accordion menu in the application

<toolkit:Accordion Height="138" HorizontalAlignment="Left" Name="accordion1" VerticalAlignment="Top" Width="151" SelectionSequence="CollapseBeforeExpand" SelectionMode="ZeroOrOne">

<toolkit:AccordionItem Content="Level 1 Content" Header="Level 1" />

<toolkit:AccordionItem Content="Level 1 Item" Header="Level 1" />

</toolkit:Accordion>

For more samples, please refer Silverlight 4 samples