SLAM Discussions Rss Feed

New Post: Double hit on Sync

rtonerii — Wed, 03 Apr 2013 13:26:05 GMT

Is there any real reason on a double hit on new sync?

I see you are triggering on Updating and Updated.
Is there a reason you are doing this?

Also, you seem to be storing the SlamIdNumber in the sites property bag every time you get a new ID. Can you maybe explain why you are doing this? I am just curious.

I feel is slows down the process.

New Post: Lookup Column - System.FormatException: String was not recognized as a valid DateTime.

thirdrock — Fri, 22 Mar 2013 12:28:04 GMT

I had this same issue yesterday.

Regarding the second solution, it appears that the 'LastUpdated' SLAM property value is in US date format but the 'Modified' field in my list is in UK format due to the site being set to use UK regional settings.

I've updated the above VerifyItemRequiresSlamUpdate method to use SPUtility.ParseDate on the 'Modified' field only:

public static bool VerifyItemRequiresSlamUpdate(this SPListItem listItem)
{
        bool result;
        string updatedDateString = listItem.GetSlamPropertyValue("LastUpdated");
        string modifiedDateString = listItem["Modified"].ToString();
        SPWeb web = listItem.Web;

        try
        {
            result = !(!String.IsNullOrEmpty(updatedDateString)
                && (DateTime.Parse(updatedDateString, DateTimeFormatInfo.InvariantInfo)
                    .CompareTo(SPUtility.ParseDate(web, modifiedDateString, SPDateFormat.DateTime, false)) >= 0));
        }
        catch (Exception ex)
        {
            try
            {
                result = !(!String.IsNullOrEmpty(updatedDateString)
                    && (DateTime.Parse(updatedDateString)
                        .CompareTo(SPUtility.ParseDate(web, modifiedDateString, SPDateFormat.DateTime, false)) >= 0));
            }
            catch (Exception)
            {
                ILogger logger = ComponentService.GetInstance<ILogger>();
                logger.LogMessage("Exception", "Unable to compare dates: updated = " + updatedDateString + ", modified = " + modifiedDateString + ", " + ex.StackTrace);
                result = true;
            }
        }

        return result;
}

I also noticed that in the 'LastUpdated' datetime is being set using the InvariantInfo, hence the first check. At the end of the sync, I was receiving an exception on the updatedDateString masked as System.Data.SqlClient.SqlException: There is already an object named 'SLAM' in the database, hence the second check.

It seems to work for me - exception free - and hopefully prevents a lot of unnecessary updating?

Hope this helps.

New Post: Sharepoint 2013 support

brjenkins — Mon, 18 Mar 2013 02:13:29 GMT

Yes. We are still working out some details, but hopefully we will start working on it soon.

New Post: Sharepoint 2013 support

wdtlhelpdesk — Mon, 18 Mar 2013 01:21:12 GMT

Hi there

Any plans to support SharePoint 2013 edition?

New Post: SLAM v2.1 Update Question

rtonerii — Mon, 11 Mar 2013 17:09:45 GMT

Is there a switch in the XML to exclude folders? They are going to make a lot of inaccurate records for me.

New Post: SLAM v2.1 Update Question

rtonerii — Fri, 08 Mar 2013 17:09:56 GMT

Humm... I never thought about folders, since records don't care about folders.

New Post: SLAM v2.1 Update Question

brjenkins — Fri, 08 Mar 2013 16:25:17 GMT

A modified form of this change is included in the release now. The change is that scope is RecursiveAll so that folders are included, and paging also will apply to lists being synchronized by content type.

New Post: SLAM v2.1 Update Question

rtonerii — Fri, 08 Mar 2013 13:51:32 GMT

I posted it under "The BIG Perforance Test lots of records"

New Post: The BIG Perforance Test lots of records

rtonerii — Thu, 07 Mar 2013 20:29:53 GMT

OK,
Please let em know if you see any issues and maybe when you could have this in the final version?
Rick

Here is my code:

This is the method I added under Core\Activation\SqlDataSynchronizeTypeProcessor.cs

    /// <summary>
    /// Helper method pages the list items.
    /// </summary>
    /// <param name="currList">This is the current List object</param>      
    private void ProcessList(SPList currList)
    {
        SPQuery spQuery = new SPQuery();
        spQuery.RowLimit = 1000;
        spQuery.ViewAttributes = "Scope=\"Recursive\"";

        do
        {
            SPListItemCollection collListItems = currList.GetItems(spQuery);

            foreach (SPListItem listItem in collListItems)
            {
                SynchronizeListItem(listItem);
            }
            spQuery.ListItemCollectionPosition = collListItems.ListItemCollectionPosition;
        } while (spQuery.ListItemCollectionPosition != null);

    }

I replaced:

    //Call update for every item in the list
    //foreach (SPListItem listItem in list.Items)
    //{
    //    SynchronizeListItem(listItem);
    //}


    //foreach (SPListItem listItem in list.Folders)
    //{
    //    SynchronizeListItem(listItem);
    //}

With:

    ProcessList(list);

New Post: SLAM v2.1 Update Question

brjenkins — Thu, 07 Mar 2013 18:00:37 GMT

That works.

New Post: SLAM v2.1 Update Question

rtonerii — Thu, 07 Mar 2013 17:59:47 GMT

I didn't, I have never updated code through CodePlex. I would have to paste the code here and have someone else add it.

New Post: SLAM v2.1 Update Question

brjenkins — Thu, 07 Mar 2013 17:51:36 GMT

Did you submit a patch with that code? If you have it then we can add that as well.

New Post: SLAM v2.1 Update Question

rtonerii — Thu, 07 Mar 2013 17:48:32 GMT

Would this happen to include using the SPQuery object and paging? If it doesn't, I have the code for that and it seems to be working great.

New Post: The BIG Perforance Test lots of records

rtonerii — Tue, 05 Mar 2013 22:23:35 GMT

OK,
It is crunching on the live server! I am not seeing any memory leaks anymore. This might work. I will let you know tomorrow.

New Post: The BIG Perforance Test lots of records

brjenkins — Tue, 05 Mar 2013 21:58:23 GMT

VS 2012

New Post: The BIG Perforance Test lots of records

rtonerii — Tue, 05 Mar 2013 21:55:38 GMT

Are you using VS 2010 or 2012 for this?

New Post: The BIG Perforance Test lots of records

brjenkins — Tue, 05 Mar 2013 21:52:38 GMT

Use Main.

New Post: The BIG Perforance Test lots of records

rtonerii — Tue, 05 Mar 2013 21:45:12 GMT

OK,
I am trying to update my code, what folder do I use? 2.0 or 3.0?

New Post: The BIG Perforance Test lots of records

rtonerii — Mon, 18 Feb 2013 14:07:53 GMT

Just to let you know, I am doing this on a webpart but it is taking 15 seconds to load the records. But I am doing it with view fields and SPQuery. I am just worried if I start digging into this that it might end up being a rewrite and then it would be better for me to start from scratch.

New Post: Synchronization Failed. NullReferenceException

brjenkins — Fri, 15 Feb 2013 19:55:35 GMT

After correcting your xml did you activate again?

If you do that, what happens if you add/update a single item?