List View Web Part - Default Chrome Setting

In our environment, the "Default" chrome setting does not display the title or the border on our list view pages. We have tried Oslo and Seattle master pages and neither displays this to the end user. We do see the title in Edit mode, but
not once the page is saved. If we switch it to Title Only, it does display.
Is this the correct behavior? If so, is there an easy way to change the chrome setting to "Title Only" for the list view web parts in one particular web application when a view is created?

That is the default behavior. normally, the listview web part is on a page where the title of the library is displayed on the page, which would make it redundant to display it in the web part only. I don't know any way to change this behavior
by default when creating a new view.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Similar Messages

"Oslo.Master" set as the The default Master Page, but when record selected in "List View Web Part" page shifts to the right.

Hi All,
I have set "Oslo.Master" as the The default Master Page for the site. I have a page with a List View web part and an InfoPath Web Part connected. When the page loads is it displayed correctly. However, when a record
is selected and the infopath web part is updated, the content on the page shifts (indents) to the right.
Is there something I am missing? Does anyone know how to correct this?
Thanks in Advance!

Hi Dwayne,
I could reproduce this, as a workaround, we can use javascript code as below to hide the element in the following image.
<script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script>
$(document).ready(function(){
$('#contentBox').prev().hide();
</script>
Thanks
Daniel Yang
TechNet Community Support

Custom column in a list view web part for a multilingual site does not take on custom language labels. Stays in default language.

Hello all,
I have what so far appears to be a fairly unique problem. We are running a multilingual SharePoint 2010 environment with English as the default language and French as the secondary. We have setup the sites in a variance relationship, but the
issue I am discussing happens outside of a variant as well.
We have created a library outside the variant (but within the collection) that the two sites must share. A list view web part was created via Designer to add to each site to provide a quick view into the list. If we are in the libary and switch
to French, then update the column label it will remember the setting (because of the resource file) and maintain it as the language is flipped back and forth. Where it doesn't work is as a web part in a variant or where the language is different.
If the language is different, the out of the box columns work find, but the custom columns (all site columns not library\list columns) remain as the english label. It doesn't matter if within a variant or outside with the browser language changed.
It always reverts back to English. It's like it isn't using the same resource file that was used in the list itself.
I created a custom view and modified it with xslt as per
http://sharepoint.stackexchange.com/questions/50004/how-to-change-column-title-for-a-view-but-not-modify-the-list but this only worked within the list and did not occur in the list view either.
I can't be the first that has come across it, either I am not performing my searches properly, no one has ever documented a fix for this or this is something we just can't fix with OOTB tools. That's the other thing, the solution has to be accomplised
OOTB or with minor client side changes. I can't fire up Visual Studio because they are piloting Office 365 and have put a "No custom code" mandate on for migration.
Thank you all in advance.

Ok, I have come up with a solution. I edited the XSLT for the web part on the page. I did the following:
1.   Create the variants in the Site Ccollection
2.   Create the library outside of the variants.
3.   Add all the columns you require for the library. It is very important all the columns are there before you move on.
4.   Create a French and English view.
5.   Create the list view web part via designer.
6.   Add the list view web part to each site selecting the appropriate view to use.
7.      Edit the page in SharePoint Designer 2010.
8.      Place cursor in the column you wish to modify.
9.      Click Design in the List View Tools on the ribbon.
10.     Then click Customize XSLT and select Customize Item. Select this option otherwise you will generate a **LOT** of unnecessary XSL code.
11.     You are looking for a piece that resembles the following:
        <xsl:with-param name="fieldtitle">
          <xsl:value-of select="@DisplayName"/>
        </xsl:with-param>
12.      Modify it by typing in the actual column name you want. You should end up with something like this:
        <xsl:with-param name="fieldtitle">
          New Column Name.
        </xsl:with-param>
13.      Now, for this page only, the column will be renamed.
There are some caveats:
1.   Doesn’t appear to work in a publishing portal. I think this has to do with how SP stores the pages in this case. In a publishing portal you can only modify the page layout which won’t work as we need to modify the content.
2.   If you add another column, you will need to repeat the XSLT modification
Anyways, I hope this helps out any others with the same issue or need as I had.

List View Web Part anonymous users paging is broken

Hi I checked that list view web part do not work for anonymous users with paging. wanted to check if its known bug or there is some intention to keep it like that.
Rohit Pasrija

Hi,
According to your description, there is an issue that if the paging is configured for a list view web part, it will be broken for anonymous users.
I tried to reproduce this issue with the steps below, however, all work without issue.
1. Enable anonymous access in Web Application level;
2. Enable anonymous access in site collection level;
3. By default, the permission settings of a list inherit the permissions from its parents, that’s say, anonymous access also enabled in the current list, “Anonymous
Users” can “View Items”;
4. Set paging for the “AllItems” view, add this list as a web part into a page, the paging works as expected for anonymous users.
I suggest you create a new Web Application and configure to enable anonymous access following the steps above to see if the issue still exists.
Thanks
Patrick Liang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Patrick Liang
TechNet Community Support

List view threshold error in list view web part, column indexing not working

Hello all,
I have a list with about 8000 items and the list view threshold is set at 5000. I want to filter the list by a certain column ("Title", single line of text) so I indexed that column. I can filter the list (AllItems.aspx) however if I put the list
on a web part page (in the form of a list view web part), I can't filter by that column. Shouldn't the indexed column allow this?
Note that the threshold will not be increased and a daily time period to bypass the threshold is in place, but I'm looking for a solution for any time of they day.
Thanks!

Thanks for your response. Your suggestion did work! It got me thinking and I took some time to investigate this column indexing stuff a little closer. I had an "ah-ha" moment.
Regardless of whether the column has an index or not, dynamic drop down filtering in a list view web part will only work if the list view has fewer items than the threshold. This is the critical point I was missing. I was assuming the index would allow for
drop down filtering.
Thanks again!

Cannot create mysites from powershell: Original XSLT List View Web Part not found

I have a bizarre problem in my SharePoint 2013 farm. This does not occur in my test farm, only in the farm we were going to go live with.
I'm on windows Server 2012, SQLServer 2012 SP1, SharePoint 2013 April CU. 1 appserver/centraladmin server, 2 web servers.
When I log into our mysitehost and click newsfeed, it will create a mysite (even though first it displays "we are sorry there was a problem creating your site")
But from powershell, whether I use $UserProfile.CreatePersonalSite() or New-SPSite, I get the following error:
Original XSLT List View Web Part not found
So far I've only found one other person with this:
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/2503e42c-e114-4e89-8e00-89fe70f0b154/cannot-create-sharepoint-mysite-programmatically
This is a brand new farm, created with the same scripts I created my test farm with, and same version of SharePoint. Only the service accounts are different. (Farm account has admin on the servers right now since I was setting up profile service).
Some other errors from the same correlation ID that look related:
It can't seem to find the listemplate 101
And something looks wrong with the MySiteDocumentLibrary feature
I have tried the following:
1. run psconfig.exe on each server
2. install-spfeature -AllExistingFeatures
3. looped through the directory under Features and for each called Install-SPFeature $dirname -Force
4. uninstalled and reinstalled MySiteDocumentLibrary feature
5. blew away the whole farm (removed all servers from farm, deleted all databases) and recreated it.
6. tried creating the UPA from the CentralAdmin gui.
The only real difference I can think of between the working farm and non working farm is, I installed the working farm using RTM, then as they came out added the March PU and April CU. For this farm I installed RTM and March and April, and then ran my build
farm script.
I am at a loss. What do I need to do, re-install the binaries? That's all I can think of. What I love is that our test / POC system worked fine, and now 2 weeks before go-live I'm seeing errors on the production servers I've never seen before. Using the
same scripts no less.
Feature Activation: Feature 'Fields' (ID: 'ca7bd552-10b1-4563-85b9-5ed1d39c962a') was activated
Feature Activation: Feature 'CTypes' (ID: '695b6570-a48b-4a8e-8ea5-26ea7fc1d162') was activated
No document templates uploaded for list "$Resources:core,global_onet_solutiongallery_list;" -- none found for list template "100"
Failed to find <ListTemplate> tag corresponding to ID "101", tried both onet.xml for site definition ID "0" language "1033" and global site definition. Operation failed.
No document templates uploaded for list "$Resources:core,stylelibraryList;" -- none found for list template "121".
System.Runtime.InteropServices.COMException: A user may not remove his or her own account from a site collection.<nativehr>0x81020051</nativehr><nativestack></nativestack>, StackTrace: at Microsoft.SharePoint.SPUserCollection.UpdateMembers
Feature Activation: Feature 'MySitePersonalSite' (ID: 'f661430e-c155-438e-a7c6-c68648f1b119') was activated
Feature Activation: Activating Feature 'MySiteDocumentLibrary'
Calling 'FeatureActivated' method of SPFeatureReceiver for Feature 'MySiteDocumentLibrary'
SharePoint Foundation Upgrade MySiteDocumentLibraryFeatureReceiveraj08n INFO Creating new My Documents library
Unknown SPRequest error occurred. More information: 0x80070002
SPRequest.GetMetadataForUrl: UserPrincipalName=, AppPrincipalName= ,bstrUrl=http://contoso/personal/cbuchholz/DOCUMENTS ,METADATAFLAGS=59
System.IO.FileNotFoundException: <nativehr>0x80070002</nativehr><nativestack></nativestack>, StackTrace: at Microsoft.SharePoint.SPWeb.GetObjectForUrl at Microsoft.SharePoint.Portal.UserProfiles.MySiteDocumentLibraryUtil.GetSPObjectFromUrl ...
<nativehr>0x80070002</nativehr><nativestack></nativestack>There is no Web named "/personal/cbuchholz/DOCUMENTS"
Possible mismatch between the reported error with code = 0x81070504 and message: "There is no Web named "/personal/cbuchholz/DOCUMENTS"." and the returned error with code 0x80070002.
Attemping to add webpart id 0F6072F2-E804-4CFD-837E-BB37332B9D1C to web http://contoso/personal/cbuchholz
Adding XsltListViewWebPart calling SPRequest::CreateListViewPart. Web part id 0F6072F2-E804-4CFD-837E-BB37332B9D1C, web http://contoso/personal/cbuchholz
Feature receiver assembly 'Microsoft.SharePoint.Portal, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c', class 'Microsoft.SharePoint.Portal.UserProfiles.MySiteDocumentLibraryFeatureReceiver', method 'FeatureActivated' for feature 'e9c0ff81-d821-4771-8b4c-246aa7e5e9eb' threw an exception: System.InvalidOperationException: Original XSLT List View Web Part not found at Microsoft.SharePoint.Portal.UserProfiles.MySiteDocumentLibraryUtil.ReplaceListViewWebPart
Feature Activation: Threw an exception, attempting to roll back. Feature 'MySiteDocumentLibrary'
Exception in EnsureFeaturesActivatedAtSite: System.InvalidOperationException: Original XSLT List View Web Part not found
Failed to activate site-collection-scoped features for template 'SPSPERS#2' in site collection 'http://contoso/personal/cbuchholz'
Failed to apply template "SPSPERS#2" to web at URL "http://contoso/personal/cbuchholz
I've had other problems in this farm: the bug where when you add Administrators to a Search Service via the Manage Service Applications page, it removes the SPSearchDBAdmin role from the search service process account. That one did not happen in the other farm.
At least other people have that one and I could just use the farm admin instead (still troublng of course).

Ok,
Here is the problem:
When creating a mysite from powershell or script, apparently you can ONLY do this from a wfe (or a server running Microsoft SharePoint Foundation Web Application in services on server).
You CANNOT create mysites from script on your appserver if it is not also a Web Application Server. I confirmed the same is true in my test farm. I guess I was always running most of these scripts on the webserver.
I searched all over and cannot find this documented anywhere.
Who do I contact to have Microsoft document this?
It's Thursday morning, I've been working non stop since Saturday morning so you don't have to :)

Missing views dropdown on list view web part.

I asked this before, and it got moved to "admin" with no replies. I really need to know this. I think it may be appropriate for design and customization, because I think that's what the solution may require. It doesn't appear to be an "admin" issue.
Any help will be gratefully received. I am very frustrated by this. The "View:" dropdown list on the right side of the list view web part for my document libraries is not available. The truly weird thing is that in a few cases, it is there, but I can't tell any difference between those web parts or DLs and the ones without the views drop-down. I have defined several public views for each document library. There are no "closed" web parts on the page (which was one suggestion I got).
I can't figure out why the views menu sometimes appears and sometimes does not, when there appears to be no way to control it. Can anyone enlighten me or suggest how I can make it appear? My users are threatening to demand a separate web part for each view (there are hundreds). I may have trouble using SPD on the client's site.

That works if the Web Part was Closed, but does not help if the user deleted the Web Part.
After some digging around in SharePoint Designer and in SharePoint itself, I have a solution for restoring the View dropdown after the out-of-the-box List View Web Part has been deleted. This solution can be accomplished without SharePoint Designer if you are working with a library, but to clean out the views from a list, you will need SharePoint Designer. I am doing this in MOSS 2007 SP1, but it should work for WSS 3.0 as well.
For this example, I am using a document library called Public Documents and my View is allitems.aspx, but this should work for any list or library.
Here are the steps for bringing back the View dropdown:
1.       Navigate to the list or library that is missing the View dropdown
2.       Go to Site Actions > Edit Page > Add a Web Part . In the Lists and Libraries section, check the box next to the Public Documents library and click the Add button.
3.       Within the new Web Part, go to edit > Modify Shared Web Part and change the Toolbar Type to “Full Toolbar”. Click the OK button.
4.       Click the link to Exit Edit Mode and you should have the Full Toolbar for the list/library displayed, but it is still missing the View dropdown menu.
5.       Go to Settings > Create View .
6.       Choose Standard View .
7.       Name the view, check the “Make this the default view” box, select the columns to include, and click the OK button.
8.       Voila, the View dropdown menu is back on the site.
9.       To completely clean it up, for a list, open in SharePoint Designer and delete the allitems.aspx view from the Forms folder. For a library, you can go to the Actions menu and select Open with Windows Explorer . Open the Forms folder (you may need to show hidden files to see this folder) and delete the allitems.aspx view. If you do not have access to SharePoint Designer and you are working in a list, you will need to delete the link on the Quick Launch and add again to point to your new view name.
10.   If the View you deleted was the default for the list or library, it may remove the link from the Quick Launch. It can be added again by going to View All Site Content , selecting the appropriate list or library, going into its Settings menu, and modifying the Title, description and navigation settings to show on the Quick Launch.

XSLT List View Web Part Error when Using Group By

I have a Tasks List created a tasks list in SharePoint. The Tasks (normal OOTB template) list works fine in the normal view, however, I have created an XSLT ListView Web Part that points to this tasks list. When I set the web part to display
a view with a "Group By" rule, it returns an error:
"Attempted to use an object that has ceased to exist. (Exception from HRESULT:
0x80030102 (STG_E_REVERTED))
The list has just over 1000 items and the threshold is set to 5000, I have tried indexing the column that I am "grouping by" just in case and that has not worked.
Has anyone experienced this issue before? If so, what steps can be done to display the XSLT List View Web Part properly?

Thank you for the response. I tried the above link and it didn't seem to solve the issue; in fact, when I clicked on Common Control Tasks there wasn't any Data View Tasks such Filter and Sort & Group.
Perhaps some more information would shed light on a solution. I created a list template including content of the task list in question. I was able to display the new list in an XSLT List View Web part with grouping enabled. However, I noticed that
the "Related Content" column was completely empty (it was there, it just had no data in each row). What is the source of this Related Content? I know it is a system column that appears when Workflows generate the item in the list but could it be the
reason for the Web part being unable to display with groupings?

Row limit in declarative list view web part

Hi,
Imagine you are in a scenario where you develop a custom web template or a site definition. Page Layouts with web part zones are being provisioned and out of them, decoratively web part pages are being created and populated with web parts. So something like:
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Module Name="XXXProjectPages" Url="$Resources:osrvcore,List_Pages_UrlName;" Path="" SetupPath="FEATURES\XXX_Intranet_PMO_PageLayouts\">

<File Url="FullPageLayout\XXXFullPageLayout.aspx" Name="Default.aspx" Type="GhostableInLibrary" IgnoreIfAlreadyExists="FALSE" ReplaceContent="TRUE" Level="Published">
<Property Name="Title" Value="Team & Collaboration" />
<Property Name="ContentType" Value="$Resources:cmscore,contenttype_page_name;" />
<Property Name="PublishingPageLayout" Value="~SiteCollection/_catalogs/masterpage/XXXFullPageLayout.aspx, ~SiteCollection/_catalogs/masterpage/XXXFullPageLayout.aspx" />

<View List="Lists/Announcements" BaseViewID="102" WebPartZoneID="wpZone1" WebPartOrder="2">
<![CDATA[
<WebPart xmlns="http://schemas.microsoft.com/WebPart/v2">
<Assembly>Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Assembly>
<TypeName>Microsoft.SharePoint.WebPartPages.ListViewWebPart</TypeName>
<Title>Latest News</Title>
<FrameType>TitleBarOnly</FrameType>
</WebPart>
]]>
</View>
For simplicity, let's assume that we are working with instances of OOB list definitions, such as Announcements or Document Library. So far so good. And now the question...
In my understanding if you want to do something as simple as limiting the number of items returned, or specifying a custom view criteria (filter/sorting/grouping, whatever) or just remove the toolbar, you have to go as far as provisioning an ENTIRE LIST
DEFINITION, defining your custom View in it (which declares the toolbar type, row limit and View) and then reference this new View by its BaseViewID. Is that correct?
Is there really no other, simpler way, of 'provisioning' and referencing a new view, to an existing list instance, along with the
Module -> File -> View element? I see a couple of logical options:
1) I would imagine such metadata could be stored in the web part and not the actual list. i.e. the web parts sends a CAML query to the list, based on the View metadata stored in it.
2) As we know, when you Edit page and configure the View for a List View Web Part on the page, that view is stored as a new hidden view in the actual list (i.e. if you have two list view web parts that reference that list, you will have two additional hidden
views). Then why can't we provision such (hidden) view along with the List View WebPart when we declare it and create the page? It could be created on first access of the page, or during the page
provisioning.
Another option could be the XmlDefinition property of the XsltListViewWebPart, but
apparently it is being ignored. I have also tried using the 'CustomSchema' property of the ListInstance, but it totally makes no sense because:
a) You cannot define more than one view in it, i.e. you have to override the OOB view that comes with the definition (lol?!)
b) You are supposed to overwrite the entire list definition, instead of simply upgrading parts of it
So, let me elaborate: if I want to have a <View> (ListViewWebPart) in my Page and this view to have some custom criteria, I have to provision an entire List Definition, is that correct? This is crazy.

Hi Hristo,
According to your description, my understanding is that you want to know if you can use <view> tag in the list view web part to define the row limit of list view web part.
Per my knowledge, you can define rowlimit element in the view element for list view web part directly not necessary to modify the entire list definition.
View Element:
http://msdn.microsoft.com/en-us/library/office/ms438338(v=office.15).aspx
Also, if you want to do more customization, you can still orverride the xslt.
More reference:
http://www.glynblogs.com/2011/04/overriding-the-presentation-of-an-xslt-list-view-web-part.html
http://unorig.com/2012/08/15/format-a-list-web-part-with-xslt/
Best Regards
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Zhengyu Guo
TechNet Community Support

Updating List View Web Part property in page

I have a List View web part (In the page > Add web part > App > document library name). I need to update the TitleUrl property of this web part through C# code.
The SaveChanges() method below works for my visual web parts, but not for the List view webpart. I get an error saying: Exception has been thrown by the target of an invocation
webpartManager = myPage.GetLimitedWebPartManager(System.Web.UI.WebControls.WebParts.PersonalizationScope.Shared);webPart.TitleUrl = titleURL;webpartManager.SaveChanges(webPart);
I did a casting as below
XsltListViewWebPart listViewWebPart = (XsltListViewWebPart)webPart;listViewWebPart.TitleUrl = titleURL;webpartManager.SaveChanges(listViewWebPart);
(Please note that casting to ListViewWebpart instead of the XsltListViewWebpart gives a invalid cast exception, which is the reason why I cast it to XsltListViewWebpart)
But I get the error at SaveChanges() method.
An exception of type 'System.Reflection.TargetInvocationException' occurred in Microsoft.SharePoint.dll but was not handled in user code
The error description is as below
> at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[]
> arguments, Signature sig, Boolean constructor) at
> System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj,
> Object[] parameters, Object[] arguments) at
> System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
> invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
> at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, Object[]
> index) at
> Microsoft.SharePoint.WebPartPages.BinaryWebPartSerializer.DoesPersonalizedPropertValueMatchDefaultValue(SPPersonalizablePropertyEntry
> spPersonalizablePropertyEntry, Object value, Control defaultControl)
> at
> Microsoft.SharePoint.WebPartPages.BinaryWebPartSerializer.Serialize(PersonalizationScope
> scope, BinaryWebPartSerializerFlag binaryWebPartSerializerFlags,
> BinaryWebPartSerializerWriter writer) at
> Microsoft.SharePoint.WebPartPages.BinaryWebPartSerializer.Serialize(SerializationMode
> mode, BinaryWebPartSerializerFlag binaryWebPartSerializerFlags,
> SPSerializationBinderBase serializationBinder,
> BinaryWebPartSerializerWriter writer) at
> Microsoft.SharePoint.WebPartPages.BinaryWebPartSerializer.Serialize(SerializationMode
> mode, BinaryWebPartSerializerFlag binaryWebPartSerializerFlags,
> SPSerializationBinderBase serializationBinder) at
> Microsoft.SharePoint.WebPartPages.SPWebPartManager.SaveChangesCore(SPLayoutProperties
> layoutProperties, Boolean httpGet, Boolean saveCompressed, Boolean
> skipRightsCheck, Boolean skipSafeAgainstScriptCheck, WebPartTypeInfo&
> newTypeId, Byte[]& newAllUsersProperties, Byte[]&
> newPerUserProperties, String[]& newLinks) at
> Microsoft.SharePoint.WebPartPages.SPWebPartManager.SaveChangesInternal(SPLayoutProperties
> layoutProperties, Boolean skipRightsCheck, Boolean
> skipSafeAgainstScriptCheck) at
> Microsoft.SharePoint.WebPartPages.SPWebPartManager.SaveChanges(Guid
> storageKey) at
> Microsoft.SharePoint.WebPartPages.SPLimitedWebPartManager.SaveChanges(WebPart
> webPart) at
> WSP.ABC.ABC.ABCWindow.<>c__DisplayClass5.<ChangeWebPartProperties>b__4()
> at
> Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()
> at
> Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated
> secureCode)
Tried casting back as below
webpartManager.SaveChanges((System.Web.UI.WebControls.WebParts.WebPart)listViewWebPart)
but still the error at SaveChange() is there.
AllowUnsafeUpdates is set to true within this block and code runs in elevated privileges.

Hi Ahamed,
According to your description, there is an issue when you try to update the TitleUrl property of a List View Web Part.
For a better troubleshooting, I suggest you do as the followings:
1. Debug your code step by step and make sure every object and variable is valid.
2. Here is a code snippet about update web part property programmatically:
SPWeb web = SPContext.Current.Web;
SPFile file = web.GetFile(HttpContext.Current.Request.Url.ToString());
SPLimitedWebPartManager manager = file.GetLimitedWebPartManager(PersonalizationScope.User);
System.Web.UI.WebControls.WebParts.WebPart webPart = manager.WebParts[this.ID];
((UpdateMeWebPart)webPart).Message = “Test”;
try
web.AllowUnsafeUpdates = true;
manager.SaveChanges(webPart);
finally
web.AllowUnsafeUpdates = false;
Here is a detailed article for your reference:
http://jeremyknight.wordpress.com/2010/11/12/programmatically-update-web-part-properties/
Best Regards
Zhengyu Guo
TechNet Community Support

List view web part not reflecting changes made to list view in SharePoint Designer

Dear All,
When adding a list view web part containing a view modified in SharePoint designer (e.g. conditional formatting applied, or group headers modified) I'm finding that the changes made in SPD are not reflected in the web part.
For example, I go into SPD edit a view, and the view appears correctly when I go back into SharePoint, however when I link to the view within a list view web part it results in losing the changes made in SPD.
Becasue it's a publishing page I'm unable to edit the contents of the web part in SPD.
I'm sure this is expected behavior but how do I get around this?
Thnaks,
MDB

Try below
http://stackoverflow.com/questions/19533998/sharepoint-designer-doesnt-show-anything-in-list-and-libraries-link
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/a63a1894-6b1d-420a-95dd-b6c546eab34d/updates-made-to-sharepoint-designer-2010-workflow-do-not-show-up-on-the-server?forum=sharepointcustomizationprevious
http://stackoverflow.com/questions/5959521/sharepoint-designer-saves-the-changes-but-it-does-not-affect
http://social.technet.microsoft.com/Forums/en-US/1e9a8c27-bbc5-4a6f-8daf-4b243182f543/changes-in-sharepoint-designer-2010-not-showing-in-sharepoint-server-2010-page?forum=sharepointadminprevious

Display Calendar View in List View Web Part

We have a list and a calendar view of the list. I wanted to display the calendar view of the list in a List View Web Part in another page in the site.
When I select the 'Calendar View' from the Views drop-down - it does not work.
Please can you help.

Hi Aritra,
Is there some errors on your environment? So, you can have two workaround to do it.
You can use SharePoint designer to add an empty data view source on your page ,then select the page.
Use
Page viewer web part on your page, then put your calendar view web part page URL into your PVWP.
Thanks,
Jack
Jack Gao
TechNet Community Support

Items to display in list view web part not showing the items setup

Hi, I have the following issue. I have a list view web part, but the web part is showing more items that the ones setup in the: Number of items to display in list view web part for this view.
It is because that works when using datasheet view and not a normal view? Is there any technical documentation from Microsoft supporting this?

thank you for your answer. It is interesting that the mobile view with the items to show in the mobile view doesn't work in the webpart, but it works when you are using datasheet view, but if you uncheck to activate the mobile view, then, the webpart doesn't
show information, so, it works partially because one part works and not the other.

List View Web part not showing all available views for list

We have added a list view web part to a page, and we get the "Current View" link in the web part...which is configurable when modifying the actual web part.
What we'd like to see (instead of having to click the ellipses button/context menu to get the other views) is the views displayed horizontally like when you are viewing the list itself.
When viewing the list itself, we see "All Items" "View 1" "View 2", etc.
Is this possible in the list view web part to display all available views in a horizontal/breadcrumb layout? Please advise.

The below works via alert, just need to now assign data to a <DIV> or element for display.
Trying this in simple webpart code snippet to get back all views:
    <script>
    var viewCollection = null;
        function runCode() {
            var clientContext = new SP.ClientContext.get_current();
            if (clientContext != undefined && clientContext != null) {
                var web = clientContext.get_web();
                var listCollection = web.get_lists();
                var list = listCollection.getByTitle("MyListName");
                this.viewCollection = list.get_views();
                //var viewInfo = new SP.ViewCreationInformation();
                //viewInfo.set_title('MyView');
                //this.viewCollection.add(viewInfo);
                clientContext.load(this.viewCollection);
                clientContext.executeQueryAsync(Function.createDelegate(this, this.onQuerySucceeded), Function.createDelegate(this, this.onQueryFailed));
        function onQuerySucceeded() {
            var viewInfo = 'Tasks list current views: \n\n';
            var viewEnumerator = this.viewCollection.getEnumerator();
            while (viewEnumerator.moveNext()) {
                var view = viewEnumerator.get_current();
                viewInfo += view.get_title() + '\n';
            alert(viewInfo);
        function onQueryFailed(sender, args) {
            alert('Request failed. ' + args.get_message() + '\n' + args.get_stackTrace());
    </script>
    <a onclick='return runCode();'>Click here</a>

SharePoint 2010 List View Web Part not showing for read-only users?

Hello all,
I have List View Webparts on my Blank Web Part page, and it's not showing for Read-Only users.
Is this intended by Microsoft or is it a bug?
Thank you!

Hi,
According to your post, my understanding is that the read only user could not see the list view web part.
Per my knowledge, the issue may be cause that the user do not have the proper permission for the list.
1. Check whether the user can access the list.
2. Check whether the user can view all the items instead of partial items in the list.
3. Check whether there are some fields refer to other lists or terms, especially the lookup field or managed metadata filed.
If that is the case, make sure the user can access the lookup list.
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

List View Web Part - Default Chrome Setting

Similar Messages

Maybe you are looking for