Tag Info

Hot answers tagged

20

No No No No No No Yes, apparently: Create a view and select a Sort By column, then set that view as the default view The DataSheet view does not play ball. The problem is that the DataSheet view is a Microsoft Access generated data table, so there are none of the usual SharePoint hooks for interacting with it. Here are some more related questions: ...


8

As described in this article : Remove button from the Ribbon in SharePoint 2010, you can, with a feature, remove existing button. In your case, the feature.xml file should be : <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <CustomAction Id="RemoveDataSheetButton" ...


8

From my experience, this is not possible through the SharePoint Dataview Sheet View. This is a new feature in 2010 and although super delicious and powerful, it still has a lot of issues that need to be resolved before it will be as powerful as it can be - in 2013, Microsoft has made improvements as per this article from MSDN To answer your question - in ...


7

There is no way to get the Datasheet view working in Safari. SharePoint Joel has a great matrix of which features work in which browser.


7

I stumbled across a way to fix this today. Under "Versioning Settings" there is a setting called "Require documents to be checked out before they can be edited" By default, in all my libraries, I have this set to "Yes" I discovered if I change that to "No" my datasheet views become read/write. Odd? Very. But it does seem to work. Incidentially, I ...


6

This is one of the limitations of an external list; there is no way to get a datasheet view with the built in functionality of SharePoint. Other limitations are quite well ennumerated on this blog post. As you can see, there are quite a few of them and it is worth bearing these in mind when designing solutions with the Business Connectivity Services.


5

Customisations to the Data Sheet View are not supported, as this is generated using the Microsoft Office Access Web Datasheet Component, which renders the grid using the same base engine as the data sheet view that Microsoft Access uses.


5

AFAIK there are not significant improvements for Datasheet functionality for end users in SharePoint 2010, and I haven't seen any in your focus areas.


5

Datasheet view requires an ActiveX control not available for that platform. See Plan browser support (SharePoint Server 2010)


4

In addition to Steve B's solution, another 2010-only way of doing this is to set the following property to true: SPList.DisableGridEditing Unfortunately there appears to be no way to do this in 2007.


4

This issue will sometimes pop up if you commonly access your pages with two urls, i.e. http://mysite.company.com and http://machinename. Verify that the user is accessing the site using the URL specified as the primary address for that zone in Alternate Access Mappings. If you are using the http://machinename url convention, I would strongly recommend that ...


4

I had the same issue. There is another way to solve this problem with editing Multiple lines of text field in DataSheet(Access) view: Changing Versioning Settings for lists and libraries is useless. You should change field settings in SharePoint Designer. Open site- choose list, then right click on Multiple Line Field (with editing problem) and choose ...


3

The DataSheet view is unfortunately not customisable; SharePoint uses Access to render the sheet, which uses its own controls and methods.


3

I think you're missing the key point here. The datasheet view is not aware of you only having add or only update permissions. It enables you the ability to add as well as update and delete, erego you need the full contribute permissions in order to accomplish this task. I have used tools like jqGrid with the client side object model to implement a rich ...


3

You'd need to have some sort of view created that displays the items you want to see. Set the folder scope to be show all items without folders when you create it. You can then flip that over to datasheet view and do what you need to do.


3

I guess I dont need the format part. All I had to do make viewtype to grid. I dont even have to format each field (like I posted in the original email). oViewCollection.Add(strViewName, viewFields, strQuery, 100, true, true, SPViewCollection.SPViewType.Grid,false);


3

If your data is in a SharePoint List, you could just create a view on the List that is specifically of type DataSheet with the appropriate columns, go through the steps of adding a Web Part to your page (Site Actions-->Edit Page...) picking your SharePoint List which will use the default view initially, then choose Modify the Web Part from its dropdown menu ...


3

You could use javascript to do this. var menuItems = document.getElementsByTagName('ie:menuitem'); for (i=0; i<menuItems.length; i++) if (menuItems[i].text == 'Edit in Datasheet') menuItems[i].removeNode(); jQuery version: $("ie\\:menuitem[text='Edit in Datasheet']").each(function() { this.hidden = true; });


3

Make sure you've configured the Datasheet section of Advanced Settings in List Settings. You should be able to edit the list in datasheet view, if the radio button is checked to "Yes" under "Allow items in this list to be edited using the datasheet and you have the correct permissions to modify the list.


3

I changed the text type from 'Enhanced Rich Text' to 'Rich text' in the column setting(through List setting) from SharePoint and it worked for me.


3

You shouldn't expect SharePoint to work well opening any view with more that 2000/5000 items (depending on SQL server version). What may slow it further down is: Lookup columns (including User and Managed Metadata) Many columns of certain type causing SharePoint to use multiple rows in SQL for each item Many is defined as: 64 Single line of text 32 ...


3

IE makes use of a Web Datasheet Component (I believe via an ActiveX control), but Chrome uses "extensions" which are not supported at the moment. Refer to this article: http://veroniquepalmer.wordpress.com/2012/02/06/sharepoint-2010-compatibility-with-google-chrome/


2

Just a lucky guess, but are you using Office 2010 x64, because: The Edit in Datasheet view functionality is not supported if you install 64-bit Office 2010. However, the functionality is available if you install 32-bit Office 2010. Source: 64-bit editions of Office 2010


2

If you right click the field in datasheet view, there should be a context menu that contains Hyperlink > Edit Hyperlink... This menu item will pop up a dialog window where you can enter both the url and description.


2

You can define your "read only" columns as rich text fields. These columns cannot be edited in the datasheet view. If you're into programming you can create your own custom field types (like custom number, currency...) Custom field types cannot be edited in the datasheet view either.


2

You need to update the DefaultView property of the list. // set web = the SPWeb that your list is in SPList list = web.Lists["My List"]; list.Views["myview"].DefaultView = true; list.Update();


2

You'll need to create a custom permission level that only gives users Edit Items permissions and apply that to a group of users in the list permissions.


2

I'm sorry but you can't. The DataSheet mode uses a "SEALED" ActiveX Control. You have no control over the markup of this control(use IE Dev Toolbar and check it out) in order to control client side behaviour.


2

Calculated columns don't work that way. Calculated columns set values based on information from other columns, not toggle visibility of form fields. The closest thing I can think of that you're wanting to do is a cascade dropdown, filtered options in a drop down list based on the selection of a previous column. The datasheet view cannot handle that to my ...


2

This is most likely due to the version difference (O2003 on MOSS2007). After googling around a bit I get the feeling the concensus is that O2003 lets you work with a list in datasheet view, but that fuunctionality is limited compared to when using O2007. Installing the Access 2007 Runtime (so you don't need the whole product) should fix the problem.



Only top voted, non community-wiki answers of a minimum length are eligible