Tag Info

New answers tagged

1

Tinkering around to fix it in the database is not recommended or supported. The old stand by is to navigate to your web part page and add ?contents=1 to the end of the URL. Here you can delete the corrupt web part. Then go back to your web part page and add it back. You can always try exporting the web part from the site it is working in and importing it ...


0

I have created a batch job to replace default.aspx page in blank web site. see the below code. private static string RootSite = ConfigurationManager.AppSettings.Get("RootSite"); private static string WebSite = ConfigurationManager.AppSettings.Get("WebSite"); private static string OriginalFile = ConfigurationManager.AppSettings.Get("OriginalFile"); private ...


-1

I found the answer in this forum: http://www.codingforums.com/javascript-programming/342525-pasting-excel-into-multiple-fields-form.html#post1450699


0

Step 1: Edit Web Part Step 2: Click "View" Just above "Appearance" and "Parameters" Step 3: Uncheck "Auto-Generate Web Part Title" Step 4: Click "Apply" Step 5: Click "Appearance" Step 6: Change your title Step 7: Click "Apply" Done!


0

This needs to be configured in 2 places: Find pagesize="30" and specify the value you need there Find <xsl:variable name="RowLimit" select="30" /> and specify the value you need there.


1

As Waqas Sarwar mentioned, I had to start SharePoint Foundation Web Application on the Search Server to get rid of that message. When I stop it again and re-run the missing server side dependencies the error appears again. I now disabled the check, because I must not run two Web frontends because of some 3rd party licenses.


0

You can't change user password in sharepoint. If you are trying to change the password of an fba user you can use the ChangePassword method (http://msdn.microsoft.com/en-us/library/system.web.security.membershipuser.changepassword.aspx) of the MembershipUser class. By other way if you want to change it in AD, you have to invoke the ChangePassword method ...


0

As SharePoint:DateTimeControl Crashes in SP2013 Webpart. Try below: <SharePoint:DateTimeControl ID="dtStartdate" runat="server" DateOnly="true" DatePickerFrameUrl="<% $SPUrl:~sitecollection/_layouts/15/iframe.aspx %>" />


0

i know it is a bit late but i was just involved in a similar Scenario: I used the MembersWebPart in SharePoint 2013 and this is a working example: <WebPart xmlns="http://schemas.microsoft.com/WebPart/v2"> <Assembly>Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Assembly> ...


0

Zone Index affects the order of web parts that are in the same Zone in a web part page, but in a wiki page, this parameter is not applicable because web parts are "inline" with the wikitext in each zone - an index alone would not be sufficient to indicate the proper positioning for the renderer. But, since it's a wiki page, you can switch to a different ...


1

You need to setup the width / float properties of the webpart zones using CSS You have to add css to MasterPage or any of the page layout that the page in which you are adding your webpart is using.


0

the export to excel can be done by client side. The SPGRidView is rendered as table itself so a simple javascript can suffice exporting to excel.This is the code <input type="button" id="Button1" value="Export" onclick="TableToExcel('TableID');" /> function TableToExcel(tableid) { var id = $('[id$="' + tableid + '"]'); var output = ...


0

You apparently have to have Tablular View turned on for a view in order for Quick Edit to work.


0

Using JSOM var clientContext = new SP.ClientContext(_spPageContextInfo.webServerRelativeUrl); var oFile = clientContext.get_web().getFileByServerRelativeUrl(_spPageContextInfo.serverRequestPath); var limitedWebPartManager = oFile.getLimitedWebPartManager(SP.WebParts.PersonalizationScope.shared); var collWebPart = ...


1

Check if "each" page is checked-in/published. Also, if you referenced any external files in script editor wp ... that files should be checked-in/published as well. Let us know if this helped.


0

I found a working solution. The ReportViewerWebPart needs an additional context. Can anyone tell me, where this is documented? Whatever, here is my working code: $webUrl = "https://sharepoint.de/websites/projekte" $pageUrl = "default.aspx" $web = Get-SPWeb $webUrl ...


0

Adding to jkandiko's answer (which worked for me), If the URL of the page containing your document list web part is http://www.mySharePoint.com/SitePages/Home.aspx, append the text ?RootFolder=((Path to target folder)) to this URL. The ?RootFolder=((...)) can be found by navigating to the target folder in the document library, then checking the ...


0

During post back you need to recreate controls and attach event as if(IsPostBack){ CreateDynamicControlsEvents(); } void CreateDynamicControlsEvents() { myButton = new Button(); myButton.Text = "Submit"; myButton.Click += myButton_clickHandler; this.Controls.Add(myButton); }


0

I found out that i simply have to call base.EnsureWebpartReady(); After this call the SharedQueryManager is correctly initialized. Thanks for your help!


3

This is because it is not deployed by your solution, only referenced! In Visual Studio, double click the Package file and choose the "Advanced" tab. Then on that tab add a reference to the file from where nuget downloads it in your project folder. This way it will be deployed to GAC on installation of your wsp


0

Why do you do this ListBox1 = new System.Web.UI.WebControls.ListBox(); You obviously already have the Listbox added in your .ascx. No need to create a new object. Just remove these lines.


0

Remember to copy the xslt from the original web part as the default xslt coming with a new CoreResultWebPart is for internal SharePoint search, and will not render anything.


1

You've ran into this problem 3 hours before me going by the time of your post. Apparently one of the issues is that in IE11 you have to turn on compatibility mode. Once I did that it worked, and then I had to select "Get filter values" rather than parameters in order to get the list of filter options. I hope that helps!


0

I have given audience targeting to the group in the web part and it worked.


1

The REST API url needs to have the site url with full /sites/BusinessServices/ etc. https://TENANT/sites/HomePortal/_api/web/GetFileByServerRelativeUrl('/sites/HomePortal/Pages/ProductInfo.aspx') And then need the personalizationscope when getting webparts : ...


0

If publishing feature is activated on the site collection level then you can see the Summary Link Web Part. it is available in the Office 365 as well but not in foundation. here is the picture:


2

Yes, there is a Summary Links web part in SharePoint 2013. It can be found under Content Rollup. However, it is not available to SharePoint Foundation, just versions above.


1

You need to use Server Side Code. The easiest option is to convert the back end DataTable to comma-seperated file. Then then use Response.Write to save it as a csv file. This file can be opened using Excel. response.ClearContent(); response.Clear(); response.ContentType = "text/plain"; response.AddHeader("Content-Disposition", "attachment; ...


0

I think that there is need to enable the site collection feature associated with web part, To do this you need site collection admin privillage and perform following Goto site setting->Under site collection administration click on site collection feature ->Find your webpart name and enable the feature.



Top 50 recent answers are included