DataSheet view and content types

Question

Hi,
 
I have a problem with the datasheet view and I would just like to confirm my findings.

We have a document library with multiple content types. Each content type may have some extra columns which may be required.

If the list is opened in datasheet view it appears to me that ALL columns that are required in at least one content type, independent of the content type of the selected row, are now treated as required columns.

Content Type A:
Columns: A, B, C, D
Required: A, D

Content Type B:
Columns: A, B, E, F
Required: A, F

If i edit a row, it appears that I have to fill out columns A, D and F no matter the content type on the current row.

Am I correct? I will conduct more tests on this, but if someone has a quick answer, I would appreciate it.

Regards,
Adrian

Answer 1

hmm.. i will say , this is quite possible 

but to workaround this , you can create view for each content type and edit items for each content type in its own DataSheet view avoiding confusion for the Users also.

Thanks

---

Sandeep Nahta http://snahta.blogspot.com

Answer 2

Sandeep, thanks for your suggestion. We have tried this variation but still have the problem where editing data in datasheet view for content type "A" is requiring data to be entered for required columns in content type "B". If the columns from content type "B" are not visible, it errors out saying that columns that require data are not included in this View, and that they need to be. If the columns are visible, the operator can enter data in the columns for that document and sharepoint seems satisfied - although this is, obviously, not an acceptable solution. I don't know if it may be relate dto the fact that we are using KnowledgeLake Imaging (and document classes) on our site, but I thought it might be worth mentioning. Any suggestions will be very much appreciated. Thanks so much to you, or whomever else might help.
Dave Steimling
DocPoint Solutions
Quality Associates Inc

Answer 3

I can only confirm that creating a separate view for each content type which then in turn is used for datasheet views does not solve the problem.

This makes "bulk edits" of large amounts of data really cumbersome.

Regards,
Adrian