You can't change the .master file when it's bound like this, you can only edit the .html file. It will re-generate the .master when you save the .html.
This is due to the Design Manager packet in SP2013. Here's the MSDN article on this feature set: http://msdn.microsoft.com/en-us/library/office/jj822363(v=office.15).aspx
The issue is that you should copy seattle.html which will auto create a .master page for you, and there is a link between the files.
To resolve the issue,
create a copy of seattle.html
Now you have both a seattle_copy(1).html and seattle_copy(1).master.
Next rename seattle_copy(1).html to for example test.html. A pop-up appears asking you to update pages ...
I think I found a solution for appWebUrl. ssdar's answer gave me the same problem as I initially had with loading different pages, but another answer in the thread they linked to contained an answer that led me to the right path.
var appWebUrl = decodeURIComponent(getQueryStringParameter('SPAppWebUrl'));
var hostUrl = decodeURIComponent(...
Right click on your solution -> Select Set Startup Projects -> Choose Multiple Startup Projects -> and select Start action for both app and app web projects. Also, app web project should be the first one.
This should do the trick.
I guess there is a MultiSelect property which you can set to false to allow only a single entry of User/Group
PeopleEditor Control - The article is for SP 2007 but I hope its the same in 2013
If it is not a Global variable yet, you can declare it as window.js=res to force it in the global scope (and thus available to all other functions)
In the code behind the code may look like this:
var url = SPContext.Current.Web.Url + "/_layouts/myPage.aspx;
"CustomScript", "OpenDialog('" + url + "', 994, 1000, 'Title of the script', null);", true);
function OpenDialog(strPageURL, width,...
The SharePoint WebPart has its roots back from the 2003 version where it inherited directly from Control because ASP.NET had no concept of a web part and SharePoint as in many other cases implemented a lot of the functionallity which was moved into ASP.NET 2.0 in order to allow SharePoint to become a real ASP.NET application in 2007.
After ASP.NET 2.0 ...
Few points you need to make corrections
InitializeControl() instead of InitializeControls()
You will find a ".ascx.g.cs" file once you expand '.ascx" file.
Change the namespace to same as in ".ascx.cs" file.
make sure you have same class name in both the files. Replace if it is displaying some other class name in ".ascx.g.cs" file. Replace it where ever you ...
The client side (no-code as you call it) approach is non-destructive to the platform as it all happens with what SharePoint natively serves up. If something breaks, you remove the problematic script and you're back functioning natively without any fancy customizations. If done right, this can still be very powerful and SharePoint gives you native version ...
"It depends" :)
It isn't particularly scalable though. You end up copying a lot of stuff around, hacking away at master pages in notepad, that sort of thing just ...
Here is a link to all possible values: http://msdn.microsoft.com/EN-US/library/ms412690
In your case you should use EditListItem or AddAndCustomizePages depending on type of page and more exact scenario.
The MSDN above has the full definitions for the two options.
If not one specific is doing it for you, you can combine multiple ones by separating them ...
It depends on your needs of course. But if only for storage and security, foundation should be enough.
You can use the managed client object model for communication with SharePoint from your MVC app: http://msdn.microsoft.com/en-us/library/ee857094(v=office.14).aspx
OR, Since you use 2013:
You could add a SharePoint Provider Hosted App to your MVC ...
As mentioned in the blog post you references, it simply needs to happen after the response has been created (i.e. the page content) and before the UpdateRequestCache event. The blog post shows an idea example of using the PostRequestReleaseState event. This happens almost immediately after the response is generated.
public void Init(HttpApplication app)
You can use below snippet to convert it programmatically
SPRegionalSettings regionalSettings = web.RegionalSettings;
SPTimeZone timeZone = regionalSettings.TimeZone;
If Constants.CLIENT_FIELD_PARENT_ID is the name of a multivalue lookup column then the value for that should be in the format Id1;#Value1;#Id2;#Value2 or without values Id1;#;#Id2;#
Which will give this code
batch.InnerXml = "<Method ID='1' Cmd='New'>"
+ "<Field Name='" + Constants.Client_Field_FirstName + "'>" + clientObj....
I am pre-assuming that you are adding this in your user control or visual web part.
You can add button click event in various methods:
Your HTML part:
<asp:Button id="Button1" Text="Click here for greeting..." OnClick="GreetingBtn_Click" runat="server"/>
In code behind file there is one method for click event:
protected void GreetingBtn_Click(...
Lists.asmx is the wrong service to use. My head banging into the subject suggested that there are 3 ways to upload to Sharepoint:
Copy.asmx web service
Frontpage Rpc (Remote Control Procedures)
To summarise the first two are limited by Windows to file sizes around 2MB for reliable transmission (higher and you can get OutOfMemoryExceptions). This is ...
You have probably read .NET Framework support in SharePoint 2010 ?
Basically, it stated that SharePoint can't run on .Net V4 (I guess it's because of the workflow engine, but it's only a supposition).
If you require something that works with V4, you have to create your own application. This application can then consume data in SharePOint using remote api (...
You could use relative paths, like in most web development, like
Or use SPUrl tokens inline in the src or href attribute. See more here: http://hristopavlov.wordpress.com/2008/12/08/urlaction-tokens-of-the-customaction-feature/
This link is 2007, but most tokens should still be valid!
The problem is likely because you are using jQuery 2.0 which does not have support for IE 6/7/8 or IE 9/10 when running in compatibility mode (which I'm guessing SP 2010 is using. You can confirm this by using the F12 developer tools).
I would recommend using jQuery 1.9.1 for use with SharePoint and so you still have support for the older browsers.
That depends where you are using it.
If you are just using it via a list field, then set the properties for that field.
If you are using it as a server side control in your code then refer to MSDN for all the properties. The specific property you want to set is:
peopleEditor.MultiSelect = false;
Karine Bosch also has a really good article on how to use ...
Either grant the anonymous user access to SQL (Not recommended) or make use of the SPSecurity.RunWithElevatedPrivileges feature in SharePoint when calling the database. Using that will execute the code as the pool account rather than as the user account.
The full details are on MSDN, just be sure to instantiate your SPSite object inside the code block ...
In IIS8 (which you are using, if you are using SharePoint 2013) it uses ASP.NET 4.5. The application events are different from 3.5 and are raised in the following order:
After the PostResolveRequestCache event ...
If its your development environment, try IISReset.. Also if that doesn't work, restart SharePoint Timer Job..
You can restart SPTimerV4 service for restarting SharePoint Timer Job, write following in Command Prompt:
net stop SPTimerV4
net start SPTimerV4
Your asp.net application would need to use the client API for SharePoint (aka CSOM), you can think of it like a provider hosted app in 2013 (but without the app web)
Here is a great starting point for CSOM: http://msdn.microsoft.com/en-us/library/office/fp179912(v=office.15).aspx
It depends on what you want to do with the data, I'd say. In general, I would recommend the custom list approach, especially if the purpose of the form is to collect data and use it later. Recently, I built a custom 'poll' web part that did just this - I had a PollResponses list that stored the choice the user submitted through an AJAX request, and then I ...