XSLT List View Web part with Inline Editing changing value for one field changes the other lookup field

Hi
It's a bit of a weird one. In an XSLT List View web part when Inline editing is enabled if I change the date column, it changes the lookup field column as well. This behavior only occurs if the lookup list has more than 20 entries. Below 20 and we are
OK.
Let me explain by example:
MileStones List - Having more than 20 items
Tasks List - having a lookup to the Title field from MileStones list. Also having a due date field.
Simple web part page with one XSLT List View web part for Tasks having inline editing enabled.
When I edit the first record's due date and press enter (which saves the changes and moves onto next record) and change the due date on second record without even touching the MileStone field. Press enter to commit changes and you see the milestone changing
on first record!
The wierd thing is that if the MileStone list has less than 20 items all works as expected.
Any pointers will be appreciated
Thanks

Hi,
This is a known limitation when working with complex fields like Lookup field.
A workaround is that we can avoid using the inline edit feature when there are
complex fields in a list.
You can take a look at this KB from Microsoft Support to get more details:
http://support.microsoft.com/kb/2600186/en-us
A similar thread for your reference:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/3d369611-ee79-4b5c-86bb-c0f3878cd746/standard-list-view-with-inline-editing-lookup-column-copies-preceding-or-following-items-related?forum=sharepointgeneralprevious
Thanks
Patrick Liang
TechNet Community Support

Similar Messages

Compound filtering xslt list view web part with _dopostback using javascript/jquery

Hello,
I am filtering list view web part as same as the below post,
http://dcsharepointchick.blogspot.in/2013/05/filter-sharepoint-list-with-partial-postback.html
here I need to filter the web part with some another condition . I am trying to write another condition in filter attribute of _doPostback(), but it doesn't work.
Please let me know is there any alternative to achieve compound filtering.
Regards,
Balakrishna M.

Hi Balakrishna,
According to your description, my understanding is that you want to filter the list view web part with more than one filters.
I recommend to use the OOB Choice Filter web part to achieve this goal.
Edit the page where the list view web part exists and then add the Choice Filter web parts to the page based on your need.
More reference:
http://office.microsoft.com/en-in/sharepoint-server-help/connect-a-filter-web-part-to-a-list-view-web-part-HA101785233.aspx#_Toc296943684
Or you use the List Filter Plus Web Part to get the function.
http://www.kwizcom.com/sharepoint-add-ons/sharepoint-list-filter-plus/overview/
Here is the link to download the web part:
http://www.kwizcom.com/sharepoint-add-ons/sharepoint-list-filter-plus/download/
Best regards.
Thanks
Victoria Xia
TechNet Community Support

XSLT list view web part with search box

Hello everyone,
I applied the xslt web part in my page with a searchbox enabled but, when i check in my page searchbox is working propery but when i publish, it gives me error such as,
inplview is not referenced.
when i check this, its loading js but the stack returns me as null.
any solutions?

Hi Sultannur,
Which level is your SharePoint farm patched on?
I searched internally, a similar issue is fixed by October,2013 CU for SharePoint 2013, that a XsltListViewWebParts cannot enable the web part property option "Display search box" in a publishing page, please check results again after update this CU for
your SharePoint server 2013.
http://blogs.technet.com/b/steve_chen/archive/2013/10/11/3601917.aspx
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2825647
Thanks
Daniel Yang
TechNet Community Support

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?

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 :)

XSLT List View Web Part

Hi Everyone,
I'm facing an issue on xslt list view web part.
I created 2 xslt list view web part on the same page, the issue is: the edit menu only show on the first xslt list view wp, I don't see the edit menu in the second list view wp, I check the log and see that it raised an error message:
"Uncaught TypeError: Cannot read property 'IsClientRendering' of undefined"
Please help to give me some solutions to solve it.
Many thanks,
Phu.

Thanks all for your quick response :-)
@Keerthi Vaddy: it is running on single server, it work fine if there is only one in a page, as I said currently the edit menu still show for the first xslt list view wp, everything is ok if there is
a xslt list view wp in a page.
@sk2014:
I need to show two or more xslt list view wp in a page, if there is only one then everything is ok
Many Thanks,
Phu.

XSLT List View Web Part Layout

Hello,
In Visual Studio 2013 i'm working with the 'XSLT List View Web Part' to show lists i have created with the list item in VS.
Is there anyway i can modify the view,group or order with ClientSide code as jquery, javascript ?
I'm new in the app development for Sharepoint.
I'm trying to find out what options i have. i Don't find much information on the web about this.
Kind Regards,
Kris

Check if below can help you:
http://www.bing.com/videos/watch/video/using-javascript-and-jquery-for-sharepoint-2013/10tiqat8f
http://aaclage.blogspot.in/2013/08/example-how-to-use-accordion-jquery.html

Adding "Filter Criteria" to the XSLT List View Web Part impact on "Export to Excel" functionality within Document Library

Hi there,
XSLT List View displaying all the list items within the Document Library. In order to implement the Search functionality within Document library out of box "Text Filter" web part is configured as explained below. The solution is similar to
the one suggested at
http://www.wonderlaura.com/Lists/Posts/Post.aspx?ID=77
"Text Filter" Web Part added to the page.
Filter Criteria (i.e., XSLT List View columns) added to the XSLT List View where the filter parameters take the input from the "Text Filter" Web Part .
3. Both Web Parts (XSLT List View and the Text Filter) are connected.
When the search criteria is entered into the "Text Filter" Web Part, it is passed to the relevant Columns of the XSLT List View and the documents (List Items) that match the search criteria are shown within XSLT List View.
Search functionality working as expected.
Query: Selecting the "Export to Excel" icon from the ribbon generates the excel spread sheet with no data except Column Titles from the Document library. In the investigation it is
found that adding the 'Filter Criteria' on XSLT List View is causing this bug. When the Filter Criteria is removed, then "Export to Excel" functionality is working as expected.
But it is mandatory to add "Filter Criteria" to implement the search functionality with in the document library.
Help: Help/input appreciated on the work around to get the "Export to Excel" functionality work when the "Filter Criteria"
exist on the XSLT List View.
Regards,

Once again thanks very much for your help Scott. very much appreciated.
In the investigation it is found that removing the 'Filter Criteria' on XSLT List View makes the "Export to Excel" functionality work. But the 'Filter Criteria' is mandatory to get the 'Document Search' functionality.
I think that due to technical limitations it should be concluded that 'only custom development can make all work, no code solutions using the SharePoint Designer can meet all the requirements.
If you can think of any alternative solution that could help in resolving the current issue or fix the issue without any custom implementation please inform. Otherwise this issue would be marked as resolved with your suggested response.
Regards,

SharePoint2010 XSLT list view web part change link to edit field

As Highlighted in image there is XSLT list view webpart and I want to change the edit field link to EditFormAdmin.ASPX form against particular Item ID.
Please suggest me how to implement it.
Thanks and Regards, Digambar Kashid

You can always change the editform.aspx for whole list using below:
http://office.microsoft.com/en-in/sharepoint-designer-help/create-a-custom-list-form-HA010119111.aspx
http://office.microsoft.com/en-in/sharepoint-designer-help/create-a-custom-list-form-using-sharepoint-designer-HA010378258.aspx
You cannot change it for a particular item in list
If this helped you resolve your issue, please mark it Answered

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

List View Web Part Search problem

We have a problem with the search in the
List View Web Part (SearchBox).
If you enter anything in SearchBox
and the beginning of the search, nothing happens.
This problem only occurs in non-admins.
In this case, the browser generates an error:
"inplview" not defined.

I have the same problem. I think the problem is related to the Publish feature.
Any ideas?

How to add SharePoint 2013 Promoted link list view web part in page programatically with Tiles view using CSOM.

How to add SharePoint 2013 Promoted link list view web part in page programatically with Tiles view using CSOM. I found that it can be
done by using XsltListViewWebPart class but how can I use this one by using shraepoint client api.
shiv

Nice, can you point me to the solution please ?
I'm trying to do this but I get an error :
Web Part Error: Cannot complete this action. Please try again. Correlation ID: blablabla
StackTrace: at Microsoft.SharePoint.SPViewCollection.EnsureViewSchema(Boolean fullBlownSchema, Boolean bNeedInitallViews) at Microsoft.SharePoint.SPList.GetView(Guid viewGuid)
All help really appreciated.

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.

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.

External List: List View Web Part query never returns

I am experiencing an usual issue in our development SharePoint 2013 environment. I have been troubleshooting it for a couple hours, so thought it is time to post a message here.
I have created a number of external content types and lists on our site. I have validated that the lists display the expected data.
However, when I add a page to our site, and add a list view web part to the page, and point the list view web part at the external list, I get unexpected behavior. While I am editing the page, the web part displays the expected data. However, after
I publish the page, when you browse to the page, all you get is the rotating green arrow gif image, and no data. It displays the image forever. If you then attempt to edit the page, in the editor, you can then see the expected data.
Any thoughts on what might be causing this issue? I have tried switching out web parts, both to the Business Data List and the Content Query web part. The Content Query web part throws an exception if you attempt to point it at any of the external lists,
which after some reading I discovered that this is a known issue with that web part.
The Business Data list web part shows the expected data, but I have been unable to get paging/grouping working with that web part yet.
Greg Pierson

I have recreated this issue on a clean site collection. I have also discovered this issue only occurs with publishing pages, not site pages. next step is to try to reproduce it on another share point 2013 install.
Greg Pierson

XSLT List View Web part with Inline Editing changing value for one field changes the other lookup field

Similar Messages

Maybe you are looking for