Tag Info

New answers tagged

0

This is the best and shortest solution Go to Edit web part and select "Miscellaneous" property and click on Server Render checkbox. then you will able to see that in designer hope it helps!


2

I can't really provide a sensible answer to why this is happening (I can confirm I'm experiencing the same weird behavior. I'm sure this is related to the fact that they cut out the designer part without properly thinking about the consequences this would have had). What I can offer is a dirty workaround that proved to be almost always working in my case. ...


0

This answer may not fully apply as I was using a ListViewWebPart (not XsltListViewWebPart) but they are similar so it might help. The following code allowed me to use a ListViewWebPart from one site (with the embedded GUIDs in the source code) on a different site collection entirely: listViewWebPart.ListId = theList.ID; listViewWebPart.ViewGuid = ...


2

I came across this today and found another workaround. When the web part is added to the page it creates a hidden view on the list it is bound to. You can get the hidden view and make the changes to it directly. This works for announcements, calendars and doc libraries from what I have tested so far. Example: private static void AddWebPart(Web web, ...


1

When you say "different XSLT Definition", do you mean the view or the XSL ? If you mean the view: XSLTListViewWebParts, if they're pointing to a list (because Document Libraries seem to act up apparently) can be pointed to one of the List's views. This way you don't have to define the view on the webpart. You can set it like so: webpart.ViewGuid = ...



Top 50 recent answers are included