Comments on: Duplicates in SharePoint Datasheet view / Export to Spreadsheet (Excel)

By: Tesfaye

Tesfaye — Fri, 30 Jul 2010 21:23:49 +0000

I have got the same issue. When the Multilookup field is not included in a list view and when we use SPList.GetItems(SPQuery), this returns a duplicate Item which differs by the value of MultipleLookup values. Ex. If Item 1 has multiple lookup value of a,b then it comes twice with multipleLookup value of a and b with the same ID.
So this issue is only fixed by users till Microsoft decided to do something.

By: Todd

Todd — Fri, 02 Oct 2009 14:38:36 +0000

Correction.

It was my “Assigned To” field. I have a required, allow multiple people, Assigned To field which, when left out of the view, does create multiple lines in both data sheet view and when exporting.

I was looking for a true LOOKUP field as stated previously on this page.

By: Todd

Todd — Fri, 02 Oct 2009 14:26:58 +0000

I’ll add 1 comment here.

I was having the same problem and had NO current lookup fields and NO allowed multiple value fields.

Turns out that at 1 time I did, had made entries, and then changed the nature of that field to something else.

Once I showed that field in the view of interest, problem went away.

By: Eric

Eric — Tue, 19 May 2009 21:23:12 +0000

I’ll second Brettski. I encountered this problem while using a column of one list as a lookup column in a second. If this first list had other required columns that allowed multiple values, the column value being looked up would appear once for every value in the multiple values columns.

Thanks for putting me on the right track! Making the multiple value columns not required in the first list got around this problem.

By: Andrew

Andrew — Tue, 28 Apr 2009 13:57:07 +0000

Yep, very helpful, thanks very much. If Brettski is buying the first beer, I’ll get the next round.

By: MCDONAMW

MCDONAMW — Fri, 17 Apr 2009 21:08:21 +0000

Turns out my statement isn’t fully true. It seems this issue only occurs with certain types of lookup fields. When I drop them down they list each item as #string#blahblah.. this is what’s throwing it off. I think it’s due to this particular look up field linking to a calculated field.

By: MCDONAMW

MCDONAMW — Fri, 17 Apr 2009 20:27:24 +0000

AAAAHHH Thanks! This was driving me nuts! Unfortunately I think my problem is not so easily resolved.

I have required fields that are lookup fields. When these fields are added to the datasheet view, I can’t edit any of the items due to some invalid text injected into the view for this particular column!

Irritated.

By: Brettski

Brettski — Thu, 05 Feb 2009 15:09:29 +0000

Thanks! Great explanation of this puzzling issue I just encountered, I feel like you saved me hours of troubleshooting. I owe you a beer.