“The attribute 'autoeventwireup' is not allowed in this page” issue in SharePoint 2013

Problem

Recently we deployed two wsp solutions in an environment. One wsp consists of master page and the other one consists of a site page with code behind where I use events like onclick and all.

After the deployment when I try to access the aspx page we got the above error.

Solutions

Solution 1.

Remove the code behind file and create a web part and add the web part in the page.You can see my blog post on how to create site page without code behind.

Solution 2.

Go to Site Settings page, under the Site Action section, click Reset to site definition.

Then give your page url and click Reset.

Check your page.

If its still the same give your master page url (which ends with .master) and repeat the above step.

Now your page should work fine.

How to disable client side people picker using JQuery in SharePoint 2013 | SharePoint Online

Problem

I had created SharePoint people picker using the example from msdn in my aspx page. I had to disable people picker through JQuery in order to full fill my client’s requirement.

Solution

According to above mentioned msdn post people picker is initiated on.

  <div id="peoplePickerDiv"></div>

So the id of the div is peoplePickerDiv. So with that I will show the solution.

Step 1:

Create an object of people picker.

  var peoplePicker = this.SPClientPeoplePicker.SPClientPeoplePickerDict.peoplePickerDiv_TopSpan;

Step 02:

Set Enable state to fasle.

peoplePicker.SetEnabledState(false);

This will disable the people picker. But you can remove the people objects with X sign. So in Step three we have to remove X.

Step 03:

Remove the X image.

$('#peoplePickerDiv_TopSpan_ResolvedList').find('.sp-peoplepicker-delImage').hide();

Conclusion

Now the people picker is disabled.

PowerApps for iPhone

Wishing you a Happy New Year with the hope that you will have many blessings in the year to come.

These days I was looking into PowerApps and I installed PowerApps app from iTunes in order to test PowerApps.

Step 01

Search PowerApps in iTunes and Get It.

Step 02

Your screen will be looking something like below. Sign in with your Office 365 account.

Step 03

Once you login you can see all the apps which you have the permission for.

Then you can navigate through the apps and can use them.

 

 

I’m looking forward to write more on PowerApps in upcoming days.

Save my email attachments to a SharePoint document library using Microsoft Flow

Introduction

I was trying Microsoft Flow and I thought of sharing how I did my first Flow App using the template provided by Microsoft.

The template I’m using is “Save email attachments to a SharePoint document library”.

Steps

Step 01

Go to https://flow.microsoft.com/en-us/ and find the “Save email attachments to a SharePoint document library” using the search box or by navigating through all template.

Step 02

Click on the app and you will get a screen as below. Then you have to select “Use this template” option.

Step 03

Click Sign In and then use your Office 365 username and password.

Step 04

The template will be created for you as below.

 

Step 05

Select Inbox for the folder option. You can select the Inbox by clicking on folder icon.

 

Step 06

Site URL: Provide the SharePoint site URL

Folder Path: Give the name of the document library where you would like to store the attachments.

File name: You can give any dynamic value or static value. Please note that you can’t store two documents in the same name. So please make sure the name is dynamic.

File Content: Select “Content”

Step 07

Click on “Create Flow” from the top.

Conclusion

Send a mail with attachment and check your SharePoint Document library. There you can find the attachments.

Usage of HTML field security in SharePoint Online and SharePoint 2013

Introduction

HTML field security in SharePoint (Office 365 and SharePoint 2013) controls inserting iframes on the pages of the particular site.

You can go to HTML Field Security by going to Setting Page and under “Site Collection Administration” you can find “HTML Field Security” option.

You can edit the page and select “Edit Source” from the ribbon in order to add iframe into a page.

Options

There are three options

Option 1. Do not permit contributors to insert iframes from external domains into pages on this site.

This blocks the contributors from adding iframes from external domains. When the users try to add an iframe through edit form they will get a notification saying “Warning: Some of your markup was stripped out. Try using the Embed command.”

Option 2. Permit contributors to insert iframes from any external domain into pages on this site.

This option will lead the contributors to add iframes from any domain.

Option 3. Permit contributors to insert iframes from the following list of external domains into pages on this site: Allow iframes from this domain:

The contributors can add iframes from the domain given in the area. And also the subdomains of the given domain are trusted.

So this is how we use the HTML field security in SharePoint. But again let’s discuss some scenarios on HTML field security.

Scenario 01.

In the setting, Option 1 is selected and can I add an iframe to the page?

Yes you can. Add the iframe through “Script Editor” web part. Edit the page, go to insert and click “Embed Code”.

Scenario 02.

What will happen to the exiting iframes if the Option is set to 3?
Nothing will happen to the exiting iframes. It will continue to work.

Scenario 03.

What will happen to sub sites?

The setting in the site collection level will be applied to sub sites as well.

Auditing in Office 365 Sites

Introduction

The audit feature in SharePoint helps you track user activities. It tells you Whochanged What, When and Where.

Providing accurate information and keeping it accurate is critical to any business. Tracking user activity and ensuring data changes are audited is important so that when mistakes happen you can quickly fix them. In most business scenarios, Auditing is a critical business requirement.

In Offcie 365, The SharePoint Online environment provides you with 3 primary configuration options for audit at the Site collection level:

1. Audit Log Trimming
2. Audit settings for Documents and Items
3. Audit settings for Lists, Libraries and Sites

Audit Log Trimming

The Audit Log Trimming settings Allow you to specify whether you want to automatically trim the audit log for the current site collection. Audit log trimming might be worthwhile if you have a very active site and are concerned about the size of the log.

Optionally specify the number of days to retain:

• The number of days to store the audit report.

Also you can select the location to store the audit report.

The audit log captures the following information for the events that are selected to be audited.

Documents and Items Level

• Editing items
• Checking out or checking in items
• Moving or copying items to another location in the site
• Deleting or restoring items

Lists, Libraries, and Sites

• Editing content types and columns
• Searching site content
• Editing users and permissions

How to Configure audit settings for a site collection?

• Go to Site Setting on the root site collection
• On the Site Settings page, under Site Collection Administration, select Site collection audit settings.

• On the Configure Audit Settings page, in the Audit Log Trimming section, set Automatically trim the audit log for this site? to Yes.
• Optionally, specify the number of days of audit log data to retain.
• You can also specify the document library to save audit reports to before the audit log is trimmed.

How to View Audit reports?

The events you selected are captured in the audit reports. You can export the report on Microsoft Excel 2013 format and can be accessed from the Auditing Reports page.

1. Go to  Site Settings page
2. Under Site Collection Administration, Select Audit log reports
3. From here, you can run the available Content Activity Reports, Information Management Policy Reports, Security and Site Settings Reports or create Custom Reports.

Give this a try and see it for yourself.

"Your domain doesn't match the expected domain for this app deployment." issue in provider hosted add-in

Problem

One of my friend had an issue after deploying his provider hosted add-in in SharePoint on premise environment. He was not able to access list data from the add-in web of the Add-in. I looked at the code and the error was something as below.

Solution

Step 01

Get the add-in id by navigating to

http://<SharePointWebsite>/_layouts/15/AppPrincipals.aspx

App identifier was something like the below and the text which was bolded will be the add-in id.

i:0i.t|ms.sp.ext|21ed123y-b1u9-4d54-9cb1-ee36b5f91304@9d2c9af1-aa54-42rf-ab8d-37d639b3f6ed

Step 02

Get the App Domain by going to below url and giving the add-in id which we got from the above.

http://<SharePointWebsite>/_layouts/15/AppInv.aspx

Step 03

My observation was that the App Domain which was given during registering the add-in was different from the url where the add-in has been hosted.

So, I registered the add-in again in the SharePoint site with the correct IIS host header and redeployed the add-in; which lead to work perfectly.

References

https://msdn.microsoft.com/en-us/library/office/jj687469.aspx