Posts

Showing posts from 2016
Missing “Save Site as Template” for Publishing Sites in SharePoint 2013? open site in sharepoint designer -> site options -> (modify) SaveSiteAsTemplateEnabled : true 
Sharepoint site columns visual studio: Single Line of Text: field id=”{FDDC4E38-25E0-4FD9-92E7-D17F34A5AB12}” description=”My Content ID of Item” staticname=”ContentID” name=”ContentID” displayname=”ContentID” type=”Text” group=”Sample Site Columns” sourceid=” http://schemas.microsoft.com/sharepoint/v3&#8243 ; Number: Field ID=”{13b3652a-d543-465d-91cb-a9d625637855}” StaticName=”Read_Times” Name =”Read_Times” DisplayName =”Read_Times” Description=”Read Time count of Item” Type=”Number” Group =”Sample Site Columns” SourceID =” http://schemas.microsoft.com/sharepoint/v3&#8243 ; Date Time: Field ID=”{d076e4d5-c785-4c04-8b56-c1f021721749}” StaticName=”CreateDate” Name=”CreateDate” DisplayName=”Create_Date” Description=”Create Date of Item” Group=”Sample Site Columns” Type=”DateTime” Format=”DateOnly” SourceID=” http://schemas.microsoft.com/sharepoint/v3/fields&#8221 ; Multiple lines of text: Field ID=”{2ae59f08-0fb0-4a9c-8a31-a180161b1029}” StaticName=”PublisherDescrip...
Set time zone for sharepoint online global. https://yoursite-admin.sharepoint.com/_layouts/regionalsetng.aspx to change time zone by site: go to site settings -> regional settings -> you can change the time zone and can apply chnage to all sub sites .
Sharepoint The server was unable to save the form at this time. Please try again solution: its a permissions issues but for some reason it shows a different error message. If your user who is facing this issue has restricted read access on site change it to read and the issue will be resolved . There is some service call that is blocked for uses with restricted read  even thogh they have full control on sharepoint list or library . So changing access level to read fixes the issue for sharepoint online. On premises: this issue is caused due to memory full. RAM. So do a iss reset or stop and start sharepoint service and that should fix the issue.
Image
How to validate the special character on SharePoint List Column Step 1:  Open Column Settings for which column you want to add the validations: List Settings > Change Column > Column Validation (below Column Settings)   Step 2:  Add the following code at the Column Validation: =AND(IF(ISERROR(FIND(",",[ColumnName])),TRUE),IF(ISERROR(FIND("&",[ColumnName])),TRUE),IF(ISERROR(FIND("!",[ColumnName])),TRUE),IF(ISERROR(FIND("@",[ColumnName])),TRUE),IF(ISERROR(FIND("~",[ColumnName])),TRUE),IF(ISERROR(FIND("#",[ColumnName])),TRUE),IF(ISERROR(FIND("$",[ColumnName])),TRUE),IF(ISERROR(FIND("%",[ColumnName])),TRUE),IF(ISERROR(FIND("*",[ColumnName])),TRUE),IF(ISERROR(FIND("(",[ColumnName])),TRUE),IF(ISERROR(FIND(")",[ColumnName])),TRUE),IF(ISERROR(FIND("-",[ColumnName])),TRUE),IF(ISERROR(FIND("+",[ColumnName])),TRUE),IF(ISERROR(FIND(":",[Column...
Error 1  Error occurred in deployment step 'Activate Features': Microsoft.Workflow.Client.ActivityNotFoundException: The activity named 'WorkflowXaml_89a963f7_e111_4556_a869_e7e93faf9414' from scope '/SharePoint/default/13e35c42-cb8c-4efa-a5a0-d0b2f58f85b1/1e1e2094-774b-44bb-b8f0-c6efd9e59449' was not found. HTTP headers received from the server - ActivityId: 09339c55-cbdc-4cb3-89f1-4309531e62e0. NodeId: WINGTIPSERVER. Scope: /SharePoint/default/13e35c42-cb8c-4efa-a5a0-d0b2f58f85b1/1e1e2094-774b-44bb-b8f0-c6efd9e59449. Client ActivityId : 8fba226a-9af7-4b70- 0 0 OPCW.SharePoint Workflow Service Status is OK. Solution : Always remember to click Publish on workflows before saving the wf as a template and also make sure your workflows are associated with lists and library
sharepoint workflow to add permissions to list with rest api ​​Recently we were developing a SharePoint 2013 style workflow and faced an issue of assigning unique permissions to a list item. In Server Side Object Model we initially break role inheritance and then assign required permissions to a securable object. We tried to use the same approach and faced issues with both steps (though it’s plain how to achieve the required functionality in JavaScript CSOM) There are no activities to break inheritance/assign permissions in SP2013 Workflows. It’s possible to invoke 2010 Workflow with this activities but it’s complicated and not possible in Apps. Thus the only way is REST API. There is no documented  BreakRoleInheritance  method in REST API ( http://msdn.microsoft.com/EN-US/library/office/jj245826.aspx#methods ). Documented method  Add  of  RoleAssignmentCollection  doesn’t exist in REST API ( http://msdn.microsoft.com/EN-US/library/office/jj245278.a...
Image
resolved : sharepoint 2013 workflow with rest api. Sharepoint 2016 workflow with rest api. or APP step sharepoint workflow. Solution: Go to  Site Settings . In the  Site Actions  section, select  Manage site features . Locate the feature called  Workflows can use app permissions , as shown in the figure, and then click  Activate . Go to  Site Settings . In the  Users and Permissions  section, select  Site app permissions . Copy the  client  section of the  App Identifier . This is the identifier between the last "|" and the "@" sign, as shown in the figure. Navigate to the  Grant permission to an app  page. This must be done by browsing to the appinv.aspx page of the site. Example: http://{hostname}/{the Site Collection}/_layouts/15/appinv.aspx. Paste the client id in the  App Id  field and then click  Lookup , as shown in the figure. Paste the following...
Add iframe to sharepoint Page  2013, Online. Solution : Site settings > Site Collection Administration > HTML Field Security > add your domain that you want to be allowed to be inframed in sharepoint. Direct Url to settings page : https://yourdomain.sharepoint.com/_layouts/15/HtmlFieldSecurity.aspx for online https://yourdomain.com/_layouts/15/HtmlFieldSecurity.aspx  for on premises 
Image
Allow SharePoint 2013 site to load into IFRAME in non-SharePoint application add the code highligted to all of your master pages if you have multiple masterpages. <WebPartPages:AllowFraming runat="server" />
REST API The Basics Before it can do anything with SharePoint, your remote Web or mobile application must obtain authorized access. In SharePoint 2013 there are two general approaches to authorizing access to a SharePoint site (regardless of whether you’re using REST). The first approach involves authenticating a SharePoint user, in which case your application has the same access to SharePoint data and capabilities as the user. The different ways you can authenticate a user from a Web or mobile application are outside the scope of this article, but we’ll briefly mention two new options in SharePoint 2013 because they affect the way you construct your REST requests: If you’re calling into SharePoint from a remotely hosted application that can’t use client-side code (HTML and JavaScript) exclusively, and there’s no firewall between SharePoint and your application, you can use OAuth 2.0 tokens with Microsoft Access Control Service (ACS) as the secure token server. If client-side ...