Get site content for freeCannot get the list schema column property from the SharePoint List
A number of people have experienced this error message when exporting a list to Microsoft Excel 2003 or even Office 2007: Cannot get the list schema column property from the SharePoint List.
This is most likely caused by a column setup as "Date and Time" which is a known issue in MOSS.
To solve this problem you can try the following items:
1. Install Windows SharePoint Services 3.0 hotfix
The hotfix information is as follows:
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
The issues the hotfix are able to resolve are the following error messages:
1. A duplicate name "Duplicate Test" was found.
2. The URL 'url to uploaded doc' is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in this current web.
3. Error: Value does not fall within the expected range.
4. An error occurred while sending file to the record center.
The MOSS RC Records Center is not properly configured for this request.
5. Cannot complete this action. Please try again.
6. This page contains one or more errors. Fix the following before continuing:
There is not enough disk space. Free up space on your hard disk and then try again.
7. Error, Cannot complete this action
8. FatalError: There is no row at position 0
9. There is a problem with the query that this web part is issuing. Check the configuration of this web part and try again.
10. The query you typed contains only words to exclude from results. Type one or more search words to include, and then retry your search.
Comments - there were some application of these hotfix that didn't solve the issue and as such some things needs to be done (see number 2 below).
2. Convert "Date and Time" to "Single Line of Text"
This is not the best solution but should be able to quickly resolve your issue. Some clients might not want this option and they would still want the "Date and Time" field in their schema. You can handle this with the following suggestions:
1. Maintain the current list and create a workflow that automatically dumps the list to another list having "Text" as it's type.
2. From the main list, edit the navigation so that the export would actually export the list from the temporary list
3. To make this seamless to the user, you can either edit the navigation from the original list via javascipts to make sure that exports extract data from the temporary list for exporting
4. You can also use content query webparts, xml programming to make it even more seamless to the user
3. Brute force approach
If you only have few items, you can do the following:
1. Create another column with Date as type
2. In Datasheet View, make sure your view only shows the "Title", "Original Date/Time" and the "New Date" Columns
3. Copy "Original Date/Time" Date column
4. Paste the values in excel as "values" only
4. Format the values to Date
5 Copy the formatted values back to your data sheet view to the "New Date" column
6. Export the fields together with your "New Date" column
7. Worth a try
Conclusion
The error might not occur when exporting to Office 2007 after the hotfix has been applied. For those clients that still have the old Office 2003, you might want to build a case around the importance of upgrading the software. Microsoft has disclaimers about using old technologies with MOSS in the event that the site breaks, doesn't function correctly, or misbehave properly. It is always best to read the recommeded technologies and try to upgrade them to avoid a lot of workarounds and spending more on upgrades for decade old technologies.
It is already year 2009 (crying out loud) and SharePoint 2009 or SharePoint 2010 is close to release, make sure we look into these old technologies and plan accordingly.
BOOKMARK FOR REFERENCE
-
[...] A number of people have experienced this error message when exporting a list to Microsoft Excel 2003 or even Office 2007: Cannot get the list schema column property from the SharePoint List. [...]
-
[...] A number of people have experienced this error message when exporting a list to Microsoft Excel 2003 or even Office 2007: Cannot get the list schema column property from the SharePoint List. [...]
-
[...] A number of people have experienced this error message when exporting a list to Microsoft Excel 2003 or even Office 2007: Cannot get the list schema column property from the SharePoint List. [...]
-
[...] A number of people have experienced this error message when exporting a list to Microsoft Excel 2003 or even Office 2007: Cannot get the list schema column property from the SharePoint List. [...]
-
[...] A number of people have experienced this error message when exporting a list to Microsoft Excel 2003 or even Office 2007: Cannot get the list schema column property from the SharePoint List. [...]
-
[...] A number of people have experienced this error message when exporting a list to Microsoft Excel 2003 or even Office 2007: Cannot get the list schema column property from the SharePoint List. [...]
-
[...] A number of people have experienced this error message when exporting a list to Microsoft Excel 2003 or even Office 2007: Cannot get the list schema column property from the SharePoint List. [...]
Leave a Comment
