Tag Info

New answers tagged

3

Why are you using the client side ID. Use the server side ID "abc". It will work. Regards.


0

Here is a workaround you can use. In the visual webpart use a hidden input control to save the value you want to display in the div. After populating, use JavaScript to read value from the input hidden control and populate the div element. Here we are using a hidden input to communicate between the div control and server side code.


1

You can save User data as below string[] userarray = a.CommaSeparatedAccounts.ToString().Split(',');; SPFieldUserValueCollection usercollection = new SPFieldUserValueCollection(); for (int i = 0; i < userarray.Length; i++) { SPFieldUserValue usertoadd = ConvertLoginAccount(userarray[i]); usercollection.Add(usertoadd); } ...


0

had got the solution of that.. changed "PublicToken" to "PublicKeyToken"


0

I can menage after ad to Alternate Mapping Default adress for my Developer Server. And it works.


1

I was able to get my solution upgraded from a 2010 project to 2013 using the following. Note that this will update your solution to use the new 2013 API. It is possible to update just the project file but still run in 2010 mode. First edit your .csproj file (for c#). Modify the target framework to this: ...


0

Yes it does makes difference.. However since you are using Visual Web part, you can use ASP.NET control and fill the dropdown etc. programmatically.


0

Couple of things. You need to handle OnSorting event and manually sort the DataTable. Then put the datatable back into ViewState You should use DisplayName Pseudo Code protected void grdProtocolli_Sorting(object sender, GridViewSortEventArgs e) { string sortingDirection = //LOGIC TO SET DIRECTION //direction is the public property if ...


2

I suspect this behavior could be related with JavaScript template itself. It seems that when XLV web part is instantiated via Visual web part, custom template is not applied since clienttemplates.js (part of CSR library) library is not yet loaded. In order to make sure the custom template is registered property, try to enclose it using SP.SOD.executeFunc ...


1

Not sure but this could be the problem: lvwp.JSLink = "~site/_layouts/15/JS/jquery2.1.1.min.js|~site/_layouts/15/JS/JSLinkFields.js"; I think you should remove the ~site part from the URL:s, like this: lvwp.JSLink = "/_layouts/15/JS/jquery2.1.1.min.js|/_layouts/15/JS/JSLinkFields.js"; Also make sure to set the ClientRender ...


0

try below code <asp:FileUpload id="FileUploadControl" runat="server" /> <asp:Button runat="server" id="UploadButton" text="Upload" onclick="UploadButton_Click" /> to upload use below code in the event string filename = Path.GetFileName(FileUploadControl.FileName); FileUploadControl.SaveAs(Server.MapPath("~/") + filename); ...


3

Package a WSP Right click your project in the right column. Then click "Publish". A dialog will open, where you will get to choose where to place the resulting .wsp file. After clicking "Publish" your project will be build and then packaged in the selected location. Make sure to have the Solution configuration set to Release when building for production. ...


0

I should say the problem is that your query is malformed. I will take a guess that you are using SSOM (C# in a .wsp)? If so you should rewrite your query like this: SPQuery myQuery = new SPQuery{ Query = @"<Where> <Eq> <FieldRef Name='FSObjType' /> <Value ...



Top 50 recent answers are included