Tag Info

New answers tagged

0

Solved, was a compatability issue between vs2012 and vs2013.


0

I am a newb to InfoPath development. As I come across your question, I can only say that I have an InfoPath form that I've started to edit in InfoPath Designer, and then I put some code-behind logic using the Visual Studio Tools for Applications (VSTA) ... But, after I've put in my custom logic, I can still go back to InfoPath designer and use it's ...


0

We found a solution allowing us to manipulate the Content Search web part in the following ways: 1) Append a "Show all" link to the web part's visual output 2) Add custom properties and use the values in code-behind. First, we created a new (non-visual) web part extending ContentBySearchWebPart. Then we overrode CreateChildControls, adding our link control: ...


0

We solved our problem. We were using Visual Studio 2012 and somehow 2012 version doesnt support $Resources:AppPart_Title inside client web part xml. When you publish the app you get the ".app" file and the "$Resources" inside client web part xml become "string type" instead of a link to a variable inside the Resource file. We solved this by upgrading to ...


0

After much research and crawling through the internet I came across this article: http://blogs.msdn.com/b/uksharepoint/archive/2011/04/04/provisioning-web-parts-to-a-page.aspx There are many articles like this but in the beginning of the article it explains my issue quite succinctly: Embed references to the web parts directly in the mark-up of the aspx ...


0

You can follow following step: Double click om the file FeatureName.Feature Then on the feature main window press F4. This will show the properties pane.


2

I think the way you are going about the whole process of hiding fields based on group is completely mislead. Hiding a field will hide the field for the entire list and for everyone. What you are working with is only a view. You can create a new view that will filter out fields based on group membership, but you will be using CSOM and javascript rather than ...


-1

Try cleanup solution using Visual Studio.. This solves to me.


0

Form modification should be used instead. http://community.bamboosolutions.com/blogs/sharepoint-2013/archive/2012/09/20/how-to-create-custom-forms-using-sharepoint-designer-2013.aspx Customize “Add New Item” form in a Sharepoint 2013 List to pull parameters from the query string Or Infopath (old school) ...


0

If your form is hosted inn sharepoint, You can use server object model for this If it is hosted outside, you can use client object model: public void UploadDocument(string siteURL, string documentListName, string documentListURL, string documentName, byte[] documentStream) { using (ClientContext clientContext = new ClientContext(siteURL)) { ...


1

My take on these: Server-side code is fun and easy to write, and you can incorporate any feature of SharePoint in order to manipulate it. You can build out vast solutions that touch many different aspects, even outside SharePoint, and bakes it into SharePoint using webparts, timer jobs, event receivers, and the like. It is hard to maintain, and migration ...


0

Please verify the SafeControl entries as mentioned in below image. Maybe that help you.


1

OK, so finally I figured it out... 1) In Tools-->Options->Text Editor->Javascript-->intellisense-->references the path to my "_references.js" file in my project was missing. I added the relative path to it ("~/Script/_references.js") 2) Also the "~/_layouts/15/" part of the path's in the references.js file itself are not working for file ...


0

Try this url having description that how to enable intellisense in VS2012 http://code.msdn.microsoft.com/office/Enable-ECMA-Client-Object-28e112cd



Top 50 recent answers are included