SharePoint Online, lets you create BCS connections to data sources that are outside the SharePoint site, like SQL Azure databases or Windows Communication Foundation (WCF) web services. Once you’ve created these connections, you can manage or edit BCS information in the SharePoint admin centre.

Understanding BCS Permissions

SharePoint Online uses BCS along with Secure Store Services to access and retrieve data such as BDC Models from external data systems.

BCS has two types of permissions:

• Object Permissions
• Meta Data Store Permissions

These are shown in the figure below.

1. Understanding Object Permissions

Object Permissions apply only to a specific External System, BDC Model, or External Content Type (ECT).

2. Understanding Metadata Store Permissions
Metadata Store Permissions apply globally to the whole BCS store. This includes BDC Models, external systems, ECTs, methods, and methods instances that are defined for that external data system. You can set permissions on the metadata store to determine who can edit items and set permissions for the store.

FIGURE 3:SET METADATA STORE PERMISSIONS

The next section explains the various options to connect SharePoint Online to SQL Server On-Premises with BCS/SharePoint Apps using Hybrid Connection and WCF Services.

Exploring Ways to Connect SharePoint Online With Online Data Sources

SharePoint Online cannot directly connect to on-premises data sources such as SQL Server. A recommended approach is to use Hybrid with SharePoint 2013/2016 but adds an overhead of infrastructure and maintenance costs. Using Azure Hybrid Connection and BCS with Azure Web App hosting WCF endpoint, it is possible to expose on-premises SQL data to SharePoint Online and Cloud by External Content Types (ECTs) or SharePoint Hosted Apps.

Connecting Different Data Sources to SharePoint

This section presents two approaches by which BCS can connect on-premise data sources to SharePoint:-

1. Azure Web App hosting WCF Service and External Lists
2. Azure Web App hosting WCF Data Service and Hosted Apps

Connecting Azure Web App hosting WCF Service and External Lists

Using this approach, you can host an Azure Web App hosting WCF Service in Azure which will connect to the SQL Server on-premise using Azure Hybrid connection. After having the data exposed via Azure WCF Service, you can use SharePoint BCS Service to create an External Content Type using SharePoint Designer based on a Web Service.

FIGURE 4: CONNECTING SQL DATABASE (ON-PREMISE) TO MICROSOFT AZURE

Connecting Azure Web App hosting WCF Data Service and Hosted Apps
Using this approach you can host a WCF Data service in Azure Web App and then create a SharePoint hosted app that will consume the fields in the WCF Data service to create an external list. After the external list is created in the SharePoint App, you can use the App Hope page to display the content as needed.

FIGURE 5: CONNECTING AZURE WEB APP HOSTING WCF DATA SERVICE AND HOSTED APPS

Exploring Seven Steps to Connect Office 365/SharePoint Online with External Data

This section explains the seven steps needed to connect Office 365/SharePoint Online with External Data:

1. Selecting an appropriate Microsoft Plan
The first step is to ensure that you have an appropriate Office 365 plan. Microsoft Business Connectivity Services are only available in the Office 365 Enterprise E3 or E4 plans for business or, if you are in the education sector, you can use Education E2 licenses.

2. Considering the Limitations
Compared to the on-premises editions of SharePoint, there are still some limitations vis-a-vis cloud edition. These limitations are:
• No profile pages for external content types
• No offline availability or rich-client integration
• No search integration
Beyond these limitations, you can use BCS to connect to different data sources like WCF web services, O-Data sources and SQL Azure databases.

3. Creating a Security Store Application
The first step is to create a target application in the Secure Store Service. This is needed in order to map a group of users to a single, external data account that can act on their behalf. In SharePoint Online, the only group restricted credentials are possible. In on-premise versions, there are also individual and mappings available. For SQL Azure Databases, the credential type needs to be set to “Windows User Name” and “Windows Password.”

4. Setting Up Connection and External Content Type (ECT)
The easiest way to create a new external content type is to use SharePoint Designer 2013, which can be used to create external content types for Microsoft SQL Azure ta-bles, views or stored procedures. For this you just need to open it and connect it to your site collection using credentials having site collection admin permission. On the left-hand side is a menu item, “External Content Types.” The connection and all CRUD methods such as read list, read item, create, update and delete can be created from here.

5. Understanding the Read / Write Operations
The Read/Write operations are explained in detail below.

Read List Operation: The Read List operation is like a select statement without a where clause. It returns by default all columns and all rows from the selected table. Filters can be created allowing the results to be trimmed.
Read Item: The Read Item operation is created so that a specific row of data can be identified and used. Each table, view or stored procedure will require a column where-by each of its values is unique, such as a primary key
Create Operation: The Create Operation is used by the external list when data is being created. The Create Operation contains the statement allowing data to be inserted into the table.
Update Operation: The Update operation provides the ability to make and submit changes back to the external data source via the external list and some Office applications such as Microsoft Excel.
Delete Operation: The Delete Operation provides the ability to select a specific row and delete it via the external list.

6. Creating Public Content-Type and Create List
The next step involved in this process is to create an external list that enables users to see and use the data.
To do this, click “Create Lists & Forms” in the Ribbon. You can specify a name and the default operation for this list.

7. Granting Permissions
To make the newly created external content type available to business users, it is important to set the permissions in the Business Connectivity Service application. This is done through the SharePoint admin center. To do this,

Select Manage BDC Models and External Content Types.

Check the box next to the name of the content type you just created, and then click the Set Object Permissions button. In the dialog box that appears, select the checkboxes for all the permissions that the SharePoint Online users need.

Conclusion
This blog showcased some key steps to connect to Business Connectivity Services in SharePoint Online. To know more on this topic, feel free to write to us at reachit@aqltech.com. To check more on customized solutions for Office 365 do visit our website http://aqltech.com.

The post Connecting SharePoint Online with BCS appeared first on AQL Technologies.

SharePoint SPFx Development Model is designed to help both new and existing devel-opers better acquaint themselves with the new set of tools required to do the job, as well as providing clear instructions how some of the server-side full trust development model practices can be achieved with this new framework.

Moving into the cloud and away from server-side takes away certain customization capabilities, but enhances the client-side look and feel. Relying on the SPFx framework, this new model can be used to create modern lightweight web applications in Share-Point Online.

Building your SharePoint Framework (SPFx) web parts
You may choose to use @pnp/sp library when building your SharePoint Framework (SPFx) web parts. This library provides a fluent API to make building your REST que-ries intuitive and supports batching and caching.

PnPJS is a fluent JavaScript API for consuming SharePoint and Office 365 REST APIs in a type-safe way. You can use it with SharePoint Framework, Nodejs, or JavaScript pro-jects. This is an open-source initiative provided by Microsoft offering developers an an-other way to consume information from SharePoint and Office 365.
The next section enumerates the steps to build a SPFx web part which uses MS Graph API through PnPjs.

Getting Started
This section focusses on Building SPFx webpart using MS Graph API through PnPjs.
Before running the steps mentioned below, check the version of Node JS and NPM in your environment as shown in the figure below.

FIG 1: CHECKING THE VERSION OF NODE JS AND NPM

Building SPFx webpart using MS Graph API through PnPjs
1. To create a SPFx web part project first create a scaffolding using the command yo @microsoft/sharepoint. The yeoman generator will ask questions like including which type of framework you want to choose .Select React as framework and press enter.

FIG 2: CREATING A SCAFFOLDING USING YEOMAN GENERATOR

2. For using PnPjs, it is necessary to Install PnPjs dependencies. Run the below com-mand in Node JS command prompt

npm install @pnp/common @pnp/odata @pnp/logging @pnp/graph @microsoft/microsoft-graph-types –save

This command will also install useful type definitions for MS Graph types.

3. Open your webpart (i.e. main webpart file – PnPGraphWebPart.ts) and import setup method:
import { setup as pnpSetup } from ‘@pnp/common’;

FIG 3: IMPORT SETUP METHOD

Add onInit (method which is called before the DOM is rendered) and configure spfx-Context with an instance of web part’s context (i.e. current context).

FIG 4: CONFIGURING SPFXCONTEXT

4. To access Microsoft Graph API, one needs to specify READ permissions to request data in the web part. Open ./config/package-solution.json (from the config folder) and add permission requests, as shown in the figure below:

FIG 5: ADDING PERMISSION REQUESTS TO ACCESS MICROSOFT GRAPH API

Note: This example uses Group API to show Office 365 groups so that all the groups which are created at tenant level (O365) will be shown in the client side web part.

5. Once the web part is developed, it needs to be bundled to create a package which will create .sppkg package in the sharepoint folder. Run the commands given below to bun-dle and package your solution.
gulp bundle –ship
gulp pacakge-solution –ship

On running the above commands, .sppkg file will be created, as shown in the figure be-low.

FIG 6:CREATING THE .SPPKG FILE

6. The package created in the previous step needs to be uploaded on your tenant-scoped App Catalog. Upon uploading you will see a screen as shown in the figure below.

FIG 7: UPLOADING YOUR TENANT-SCOPED APP CATALOG

The message means that you should approve all permission requests which we added earlier.
The next section explains how to approve app permission requests.

Approving App Permission Requests
There are different ways to approve your permission requests (UI, PowerShell, and O365 cli). The simplest one is through the new UI of SharePoint central administration. You can navigate to your old SharePoint admin center and click “Try new” UI from there. Or you can simply open a page https://-ad-min.sharepoint.com/_layouts/15/online/AdminHome.aspx#/webApiPermissionManagement (replace “ with your real organization name), please find be-low the screenshot:-

Go ahead and select your APIs and click Approve. Once approved, you will see the screen as shown in the figure below.

FIG 8: API MANAGEMENT SCREEN

graph.groups.get<Group[]>().then(groups => {
this.setState({
groups
});
});
The code mentioned in the image below is used to access Office 365 groups using Graph API (Groups API)

FIG 9: ACCESSING OFFICE 365 GROUPS USING GRAPH API

On completion of the above steps, simply run gulp serve and open SharePoint hosted workbench (it only works in hosted one) to see the output. The output will be as shown in the figure below.

FIG 10: GROUPS AT YOUR TENANT

Cross Verifying the Output
To cross-verify the output, check the below screen where Office 365 groups are shown. Go to Office 365 admin center and click on Groups on left and check the groups which are created.

FIG 11:CROSS VERIFYING THE OUTPUT USING GROUPS

Note: Web part in this solution illustrates the following concepts on top of the SharePoint Frame-work:
1. showcases PnPJS configuration inside SharePoint Framework
2. showcases how to use MS Graph with PnPJS
3. showcases how to correctly configure SharePoint Framework solution and tenant to allow PnPJS to call MS Graph

Important Tips
1. Please use http://aka.ms/sppnp for the latest updates around the whole SharePoint Patterns and Practices (PnP) initiative.If you want to learn more about PnP JS Library, refer the URL – https://pnp.github.io/pnpjs/
2. The following packages comprise the Patterns and Practices client side libraries.
@pnp/common: Provides shared functionality across all pnp libraries
a. @pnp/config-store : Provides a way to manage configuration within your application
b. @pnp/graph : Provides functionality to query the Microsoft Graph
c. @pnp/logging: Light-weight, subscribable logging framework
d. @pnp/nodejs: Provides functionality enabling the @pnp libraries within nodejs
e. @pnp/odata: Provides shared odata functionality and base classes
f. @pnp/pnpjs: Rollup library of core functionality, mimics sp-pnp-js
g. @pnp/sp : Provides a fluent api for working with SharePoint REST
h. @pnp/sp-addinhelpers: Provides functionality for working within SharePoint add-ins
i. @pnp/sp-taxonomy: Provides a fluent API for querying taxonomy in-formation
j. @pnp/sp-clientsvc: Handles generic communication with client.svc endpoint, removing SP.*.js dependencies

Conclusion
This article explained how we can use PnPJS in SharePoint Framework (SPFx) client side web-part by using React as JavaScript framework. If you’d like to know more on this topic write to us today at reachit@aqltech.com.

To get latest updates and hear new on Office 365 subscribe to our blog section now.

The post Using PnPJs with React framework In SPFx appeared first on AQL Technologies.

Understanding SharePoint’s Responsive Frame-work and Offering
SharePoint has embraced the responsiveness and simplistic design that the modern applications and design landscape demands. Unlike the other offerings of Microsoft, SharePoint also boasts of the intuitive UI, sleek designs and interactive web experiences.

The Microsoft SharePoint app takes care of key elements like:
• resizing as per different resolutions
• screen sizes,
• alternate image mapping,
• CSS media queries

SharePoint 2013 onwards and SharePoint online supports Bootstrap, one of the leading responsive and mobile friendly CSS frameworks. The sites and pages can be accessed by any Desktop, mobile, tablets on any browser without any loss of functionality or page designs.
 
Leveraging SharePoint’s Mobile Responsiveness Features
In terms of mobile responsiveness, the Microsoft SharePoint app has come a long way in terms of delivering enterprise capabilities and applications on the go, within your pocket. Microsoft offers a dedicated and free of cost app for the following three major mobile platforms:
• Windows
• Android
• iPhones

The app can be installed without any hassles and supports both online and on-premise versions (SharePoint 2013 and above) of SharePoint.

Installing the App
Once a user installs the app, the app will ask for the credentials to authorize. This is a onetime activity. In the case of on-premise versions, users can type in the URL directly and authorize themselves by providing the credentials. The credentials page appears as shown in the image below.

Fig 1: User Sign in page

After logging in to the app, one finds the mobile version to be very fluid and not much different than the browser-based experience. In case the user is within a SharePoint Online site in the app, he is presented with the following three sections:
· News
· Find
· Me

Exploring the News Section
The news section displays all the news posts across your various sites. The news section lets a user do the following:
• save the posts to view later
• share it internally or externally via Facebook, WhatsApp, etc
• view more details of the news posts
The news posts can be further filtered to show items across these sections.

Fig 2: News Section

Exploring the Find Option
Find is synonymous to the out-of-the-box search that SharePoint offers in its web versions. The Find screen lets the user search for contents. SharePoint offers an extensive search that filters the results across the following sections as shown in the figure below.
• All
• Sites
• Files
• People
• News

The Find landing screen also displays the frequently visited sites, People, recent files, etc.

Fig 3: Find Section

Exploring the Me section
The Me section is the people section of the app where a user can view all his details. The section has two tabs- Recent and Saved. Recent display the items that a user has recently accessed. Saved displays all the items saved by the user.

Fig 4: Me section

Understanding Additional Features in the SharePoint App
SharePoint offers smooth navigation in the app. For example, if the user has to visit any site, he can directly use the Find screen. In case the site does not open from the Find section a user can also use the “More sites” option.
On opening the site, a user can work with files, documents, lists, etc. There is a mobile menu for site content navigation. Clicking on it will open the available options as shown in the next image. 

Fig 5: List Menu on opening a site

SharePoint also allows users to add documents and folders with ease. Users can perform the following options on the documents
• Download
• Delete
• Copy link
• View
• Manage version history

Fig 6: Managing Documents within a site

Conclusion
These were some of the key highlights from the SharePoint app. The app lives up to the pocket-sized gateway to your enterprise applications. As we have seen, SharePoint allows many useful actions that can be performed on the go.

Microsoft rolls out new features in its SharePoint app with every new update. If you’d like to be posted on these, learn more on this topic or are keen to get answers to some very specific queries, feel free to write to us at emailid@domainname. To check more on customized solutions for Office 365 do visit our website http://aqltech.com.

The post SharePoint responsiveness and mobile capabilities appeared first on AQL Technologies.

Getting to Know Office 365 Developer Patterns & Practices tools

Office 365 Developer Patterns & Practices (PnP), which is a community initiative originally made by Microsoft and today held by a core team of a few Microsoft internals and external community members like MCSMs (Microsoft Certified Solution Masters for SharePoint) and MVPs (Microsoft Most Valuable Professionals). The focus of PnP is to provide training, guidance articles, samples, solutions, and more to support the community of Office 365 developers.

One of the key elements of the PnP offering is a library of helper types, extension methods, and frameworks to make it easy to develop Office 365 solutions. The library is called SharePoint PnP Core library, and it is an open source library that is available for free on GitHub
Also, PnP is being used in other areas as well like SharePoint Framework (SPFx), Office 365 development, Office Add-ins and Microsoft Graph API. 

Accessing SharePoint Using APIs

From SharePoint 2010, Microsoft introduced client-side development and use of different types of client-side API’s. The primarily used API’s to access SharePoint objects are:

1) Managed Client Side Object Model
2) JavaScript Object Model
3) SPServices
4) REST API’s

Using SharePoint patterns and practices JavaScript Core Library(PnP JS Core Library)

One of the most useful libraries for SharePoint Framework developers is SharePoint PnP JavaScript Core Library. This library was created to help SharePoint developers work with SharePoint content, simplifying the common operations with a REST wrapper required in most SharePoint applications. It has a simple and powerful API, which uses SharePoint REST API under the hood, but makes operations very easy and as straightforward as possible. It also includes a number of utility and helper functions. The library is currently in version 2.0.

Accessing PnPJS Core Library

To access SharePoint PnP JavaScript Core Library open the repository URL which contains the source of PnP JavaScript core library for SharePoint as showing in the figure below:-

https://github.com/SharePoint/PnP-JS-Core

There are numerous repositories on open source code samples. You can use the URL below to access such repository:-https://github.com/PnP

Learning with Samples

This section presents an example to demonstrate three ways to write the same type of code via SharePoint JSOM, REST and PnP.js.

Using JSOM
Use the code given below for JSOM.

function getwebdetails() {
var ctx = SP.ClientContext.get_current();
oWeb = clientContext.get_web();
ctx.load(oWeb, 'Title', 'Description');
clientContext.executeQueryAsync(new function() {
var wDetails = "Web Title: " + oWeb.get_description() + " ";
console.log(wDetails);
}, onQueryFailed);
}
ExecuteOrDelayUntilScriptLoaded(getwebdetails, "sp.js");

Using REST API
Use the code given below for REST API.

$.ajax({
url: _spPageContextInfo.webAbsoluteUrl + "/_api/web?$select=Title,Description",
method: "GET",
headers: {
"Accept": "application/json; odata=verbose"
},
success: function(data) {
console.log("Web: " + data.d.Title + " - Description: " + data.d.Description);
}
});

Using PnP.js
Use the code given below for PnP.js.

$pnp.sp.web.get().then(function(data) {
console.log(data.Title + ' - ' + data.Description);
});

To Use PnP.js in SharePoint, give reference to 3 scripts on a SharePoint page. as shown below.

< script src="https://cdnjs.cloudflare.com/ajax/libs/fetch/2.0.3/fetch.min.js" type="text/javascript"gt</script
<script src="https://cdnjs.cloudflare.com/ajax/libs/es6-promise/4.1.0/es6-promise.min.js" type="text/javascript"gt</script
<sscript src="https://cdnjs.cloudflare.com/ajax/libs/sp-pnp-js/2.0.5/pnp.min.js" type="text/javascript"gt</script

Following are the three types of script files used :

1) Fetch.min.js : This file is required to get the new feature of JavaScript promise work on Internet Explorer.
2) Promise.min.js: This file gives methods like “.then()” and “.catch()”, which are executed when called web service gives a response & fulfilled a promise or gives an error as response respectively.
3) Pnp.min.js: This file is required for SharePoint site objects operations
 
Tracking the PNP Journey

The PnP journey is fascinating. With a few driving forces within Microsoft and the community, the Office Developer Patterns and Practices emerged some years ago. Office Dev PnP, is a massive project aiming to provide a centralized hub to resolve common issues.In practice, the Office Dev PnP aids developers wishing to become better on their journey with the SharePoint Framework by providing a wealth of guidance and code that can be freely reused. Figure below shares some interesting insights on PnP’s journey and milestones.

Why PnP?

There’re a number of reasons why you should be using PnP. The figure below cites a few key reasons.

PnP JS Helps in
· By default follows good practices and eases Future maintenance headaches
· Benefit from code that was reviewed by multiple people
· Help by creating issues and by submitting pull requests (bug fixes, new features, new controls)
· Helps in simplifying common operations within SharePoint and the SharePoint Framework.
· Contains a fluent API for working with the full SharePoint REST API as well as utility and helper functions.
· Takes the guess work out of creating REST requests, letting developers focus on “what” and less on “how”.

Acknowledging the 3 pillars of PnP

The three pillars of PnP are
PnP Core – wrapper over CSOM.
PnPJS – wrapper of SharePoint Rest API. Also supports Microsoft Graph API. Is fluent and quite awesome
PnP PowerShell – OOTB SPO shell is geared more towards Tenant and Site Collection level events. PnP PS uses PnP Core and is more geared towards lists, files, and list items as well as the tenant, site collection and web events

Conclusion

This blog showcased how to leverage PnP JS Core in SharePoint projects. If you’d like to know more about Office 365 or PnP do write to us today at enquire@aqltech.com. For more updates on the latest from the world of Office 365 do subscribe to our blogs/newsletters.

The post Getting Started With Sharepoint PnP Engine appeared first on AQL Technologies.

External Sharing in SharePoint: –
SharePoint Online has external sharing settings at both the organization level and the site level (previously called the “site collection” level).

There are basically 4 ways by which you can share your content in SharePoint Online:-

a) Anyone – A transferrable, revocable secret key (transferrable means can be forwarded to others, revocable means access can be revoked any time and secret key means users need the link to gain access )
• We can allow some recipients who don’t want to authenticate. If you allow “Anyone” links, invitations aren’t sent an email. Users can copy the link and share it however they like. Anyone with the link (inside or outside your organization) can access files and folders without having to sign in or provide a code. These links can be freely passed around and are valid until the link is deleted or expires (if you’ve set an expiration date).

b) People in your organization – Only grant access to internal users
• To allow external sharing on any site, you must allow it at the organization level. You can then restrict external sharing for other sites. If a site’s external sharing option and the organization-level sharing option don’t match, the most restrictive value will always be applied.

c) People with existing access
• The external sharing features of SharePoint Online let users in your organization share content with people outside the organization (such as partners, vendors, clients, or customers).
d) Specific people
• When users share with people outside the organization, an invitation is sent to the person in email, which contains a link to the shared item.

Authenticated External user and Anonymous user Sharing options: –
Below table gives the difference between functionalities of Authenticated External user and Anonymous user:-

Scenarios of external sharing: –

NOTE: You can stop sharing with guests by removing their permissions from the shared item, or by removing them as a guest in your directory.

External Sharing Configuration in SharePoint

Before managing External Sharing for SharePoint, you will have to make sure it is enabled for your Office 365 tenant as a whole. Below are the steps to enable external sharing in Office 365 tenant: –

1) From your Office 365 home screen, navigate to your Admin center.
2) From the Admin Center, choose the “Admin Center” tab on the left-hand side and then “SharePoint.” This will take you to the SharePoint admin settings page, where you can configure external sharing.
3) Navigate to the “Sharing ” tab on the left to view all the sharing options.

NOTE: By default, external sharing is allowed, anonymously or not, in your organization. This setting should be adjusted to your specific business needs to avoid accidental data leaks.

Manage external sharing by SharePoint Administrator: –
Below image shows the functionality which an administrator can perform for external sharing.

Sharing in OneDrive
Below screenshot shows the admin center of OneDrive: –

The options in the OneDrive external sharing settings are the same as SharePoint, but the UI is a little different. The same options are available, but in a drop-down menu rather than by radio buttons.

What’s new for users – Better Sharing! –

1) Smart people picker using Microsoft Graph – Find people faster; type less

2) Link open receipts – Know when your link got opened, a confirmation email will be sent the first time when the link is opened

3) Password protected links
a. Prevent accidental re-sharing of “anyone” links
b. Require users to enter a custom password before accessing a file or folder

4) Block downloads
a. Keep your documents in the cloud
i. Avoid out-of-date copies
ii. Maintain access control
b. Available for view-only links

5) Sharing from mobile apps

6) Sharing from Word, Excel, PowerPoint mobile

7) Send via Microsoft Teams – Send links via Teams directly from the OneDrive app

8) Integration with Microsoft Teams – Full OneDrive sharing from Microsoft teams

Summary: –
In this article, we saw that what are the various option to share files in SharePoint and OneDrive.

The post External Sharing and Collaboration on SharePoint and OneDrive appeared first on AQL Technologies.

Modern SharePoint is whole new user experience. It’s more than a fresh look, it’s designed from the ground up to work on mobile devices, and it addresses dozens of usability issues. Lists and Libraries have the new look and the modern page is definitely easier to use and allows more advanced filtering and bulk editing.

In SharePoint Online, lists and libraries are modern by default; web part pages are modern if you create a “modern team site” or “communication site”.

You can also add new, modern pages to existing team sites (but not yet to classic “publishing sites”). Once a new page is set up, it can be set as the site home page, and the site will gain almost all the advantages of a fully modern team or communication site.

Differences between Classic and Modern SharePoint Features

ResponsivenessClassic SharePoint is partially responsive including all classic web part. Classic SharePoint is not mobile friendlyModern SharePoint comes with full responsiveness on all modern web parts. Modern SharePoint comes with Team sites, modern list and library structure and site pages. Modern SharePoint support all modern devices including mobiles, tablets and surface devices.Secure and FasterIn Classic SharePoint user have permission to add custom code (JavaScript), also have script editor and content editor web part that render on the server side that’s why it takes time to load on the browser with additional security issues.Modern SharePoint doesn’t allow any custom code even it does not provide any script editor web part for custom code that’s why is more secure and loads faster
The user can also edit pages in SharePoint designer.

How to Get Modern Experience

If you have an Office 365 subscription, you can go modern right now! Just go to the SharePoint Home page and click “+ Create Site” to create a modern Communication or Team site.
If you have an existing site in SharePoint Online, you probably already have modern lists and libraries. If the site doesn’t use the Publishing feature (such as a Team site), just create a new page (in the “Site Pages” library) and by default it will be modern.

List of Web Parts of Modern SharePoint Online pages

Once we add a modern page to a site, we also add and customize web parts, which are the basic building blocks of our page. These web parts are categories:
• Text, media, and content
• Discovery
• Communication and collaboration
• Business and intelligence
• Connectors

Summary:-
In this article, we saw some really cool features of Modern SharePoint experience which every developer should start using because it always better to prepare for the future.

The post Features of Modern UI that you will miss in Classic UI appeared first on AQL Technologies.

http://www.sharepointchick.com/archive/2011/10/29/finding-the-application-pool-account-for-a-web-application.aspx

The post Finding the application pool for a SharePoint web application appeared first on AQL Technologies.