Archive for the ‘SharePoint Development’

Introduction

The Microsoft Search functionality provisions the end user to search a wide range of content like documents, images, videos, audios, etc. within a SharePoint site. In SharePoint On-premise, a user can configure the Search Service Application and crawl the content of the various sites. While SharePoint Online provides both modern and classic search experience to an end user.

Nowadays, users are using the different version of SharePoint On-premise and there is need to get the content of one version into another. To achieve this, SharePoint development team is providing support to crawl the content from the below versions refers below the table.

Users are also using SharePoint On-premise and SharePoint Online, so there is a need to search the content among them. The content is searched inside the SharePoint server and Office 365 separately and they have their own search index repository.

Microsoft has introduced a concept of the cloud hybrid search and in this concept, the crawled content is indexed in the search index which resides in the Office 365.

Let’s configure the Cloud Hybrid Search with Office 365 and SharePoint 2016, and understand it in more depth.

Pre-requisites before configuration

Below are the pre-Requisites which are needed to be fulfilled before configuration of SharePoint 2016 Hybrid Search.

Register a public domain with Office 365

There is a default domain in XXXX.onmicrosoft.com format when a user signs up for the Office 365. This default domain works perfectly fine for the trial version and to carry out some testing on an environment. When there is a circumstance in which a user is required to deploy the Office 365 service to an organization, the user must require to use a custom domain thus the customers and users can identify the organization by URL itself.This procedure contains three main tasks:

1.Add a Domain

• Go to Office 365 Admin and click on the Domains tab by expanding the Setup section.
• Click on Add domain from Domains page.
• Specify the name of the domain in the text box and click on Next.

2.Verify Domain

• The next step after adding a domain is to verify it.
• There are two ways to verify the domain:
  • Sign in to GoDaddy (recommended)
  • Add a TXT record instead

  

• Based on a user’s requirement, he can choose any one of the verification approaches. Here, we are proceeding with the recommended approach i.e. Sign in to GoDaddy.
• Log into GoDaddy and confirm access for Office 365 to makes changes to the domain at GoDaddy.
• GoDaddy automatically contacts to the Domain registrar and also proceed with the verification.
• After the verification, it displays the success message.

3.Update the DNS Settings

• Once verification is completed, update the DNS settings. For updating DNS settings, again there are two options to provision it and they are:

1. Add the DNS records for me (recommended)
2. I’ll add the DNS records myself.

• Based on a user’s requirement, he can update the DNS settings by choosing any option. Here, we are proceeding with the recommended approach i.e. Add the DNS records for me and click on Next.

• From “Choose your online services” screen, check all 3 options (Exchange, Skype for business and Mobile Device Management for Office 365) and click on Next.

• Provide valid credentials in the Domain Manager Login screen and click on Sign In.

• It displays the DNS records which are added to the newly created domain at GoDaddy and click on Next button.

• It displays the success message. Click on Finish.

Add User on newly created domain

To add a new user in the newly created domain walkthrough the below-mentioned steps.

• Click on Users Active users from Left panel.
• From Active users page, click Add a user.
• Enter requires details for a new user and choose the newly created domain. Click on Add.
• The new user is listed on the Active user’s page. Click on the newly created user.
• Click on Manage roles.
• Select the user role as Global administrator & save it.

• Head over to Office 365 to check the synchronization status. All the On-premise users have been added to Office 365 as part of the synchronization process. Click Users  Active users  Refresh and check On-premise users.

Create a content source to crawl for cloud hybrid search.

• As a final step in configuring the Cloud hybrid search, a user is required to create a content source and run a full crawl in SharePoint 2016 On Premise Server.
• Click the Cloud Search Service Application which was created from Central Admin in 6.1 section.
• It will open the Search Administration page. Select Content Sources under Crawling from the left navigation pane.
• From the Content Sources page, create New Content Source. This will open up the page, where a user can provide the Content Source Name, its type and the start addresses i.e. site URLs from where the crawling needs to start.
• A user can also schedule the incremental and full crawls to take place in the Server.
• The incremental crawl is scheduled to run daily, weekly or monthly. We have set the incremental crawl to run daily at 30 minutes intervals.
• On the other hand, the full crawl can also be scheduled to run daily, weekly or monthly. We have set it to run every day at 12 AM.
• After scheduling the crawls, the configuration will look like as shown below in the image.
• Now, let’s go ahead and run a full crawl.
• We are running the craw for the first time so even if we click on incremental crawl then also a full crawl will take place and the time taken will depend upon the amount of the content within the content source.

Lately, we have been using collaboration tools depending on the type of communication. When it comes to Microsoft space, we use

1. Outlook and Exchange for persistent messaging.
2. Lync/Skype for Business for real-time communication.
3. SharePoint for effective document sharing and team collaboration.

A new-gen collaboration tool

Above tools work in sync to cater our communication need whether it is message based, real-time or documents and other information sharing across boundaries. They work relative to each other but still they’re separate programs which we have to run and juggle between continuously. It demands a lot of context switching to access information organized in each tool i.e. to view email in Outlook or Exchange, Skype for chat and SharePoint workspace to access files or pages. Microsoft Teams aka Teams brings together all these facets of communication under a single roof.

Benefits of Microsoft Teams include:

• Real-time and quick access to messages, documents, notes, and meetings.
• Communication with teammates who are online.
• Reducing the need to send redundant emails while it provides a notification for uploaded documents across the channel.
• Conversation across or outside the organization through chats, meetings, file sharing, host audios, videos, and conference calls, thus relegating the need to send information using Skype or Outlook.
• Share and host files with Office 365 apps such as SharePoint, Word, Excel, Power BI and more.
• Increase teamwork and productivity by integrating Microsoft and various third-party services.
• Security and compliance capabilities.

Relation with SharePoint

Both Microsoft Teams and SharePoint team site are common in a way that both are streamlined by topic, project, collaboration or team of people. Teams and channels often follow a structure that is similar to the SharePoint team and project sites. To store the channel documents, it is adamant with the fact that every Microsoft Team has a modern team site working in SharePoint development. Also, there is an associated folder inside SharePoint document library for each channel in Microsoft Teams.

SharePoint documents in MS Teams

There are a number of positive collaborating Teams’ documents in SharePoint. Files in Teams are easily discoverable in SharePoint search. SharePoint supports previewing documents for more than 300 file types which can be accessed directly from the Files tab in MS Teams. Users don’t have to juggle between tabs to access their files as there is an “Open in SharePoint” option that browses to the SharePoint modern team site.

SharePoint Pages in MS Teams

You can also add SharePoint page as a tab in MS Teams. Building a tab is a much simpler approach compared to the typical approach of building a whole website. SharePoint team site’ home page can appear in the same user interface thus providing the intuitive user experience.

It also provides an interface to add the whole document as a tab that is easily accessible by all the members in a team.

Conversations and News

SharePoint’ Discussion and Newsfeed lists satisfy conversations to some extent but due to their usability issues, they were never able to satisfy most customer needs. Now it is also possible to integrate Yammer with SharePoint within Office 365 but it does not provide an extensive approach.

You can directly have a conversation regarding a document and other shared information in MS Teams.

The conversation is also shown directly under the Conversations tab in the channel so that all the members of the team are aware of it.

Microsoft Teams also bubble up team news that helps transcend the conversation. To easily highlight an update and announce news items. SharePoint news can be configured as messages in the conversation thread and Modern SharePoint news as web parts in hub sites.

How to determine if your SharePoint site is connected to MS Teams?

First, you need to know whether you are on a modern or classic team site collection.

Click on the Settings gear on the root site to find Site information option is available or not. If you cannot see the option, you have a classic page on a classic site.

Classic Vs Modern Page

If Site information option is available, you are sure that you have a modern page. But wait, still, you may have a classic site. Click Site information link. A panel Edit site information will be opened on the right. If it contains Privacy settings then you have a modern team site connected to an Office 365 group. If not, you have a classic team site containing a modern page.

Site information panel – Classic site (modern page) vs modern site

Now, you can easily determine if you have a classic or a modern team site. To add a Team for a classic site, you need to groupify the site by adding an Office 365 group. For modern team site or classic team site after adding Office 365 group, you can easily add a Team.

Connect Office 365 group with the classic team site

You can control whether global or SharePoint admin can connect classic team site to Office 365 group.

• Log in to Office 365 using global or SharePoint admin account.
• Click app launcher icon at the top-left corner and select Admin to open Office 365 admin center.

• From the left pane, select SharePoint under Admin centers to open SharePoint admin center.

• Select Settings from the left pane.

• Click Allow site collection administrators to connect sites to new Office 365 groups option next to Connections from sites to Office 365 groups property. Click OK to save the changes.

Once the setting is applied, it enables site collection administrator to connect classic team site to Office 365 groups and an option to create a team with Microsoft Teams.

• Select Connect to new Office 365 Group from Settings menu.

• Click on the link from the group creation experience and select Let’s get started.

• If needed, update group name and email address and change privacy settings. Select the Connect group.

• Add additional owners and members, if needed inside Add and assign people panel. Click Finish to open new site home page.

Create a team from an existing Office 365 group in Microsoft Teams

• Navigate to Microsoft Teams and click Join or create a team at the bottom. Then click Create a team button.

• To create a team based on the created group, click Create a team from an existing Office 365 group.

• Select the newly created group from the list of available Office 365 groups and click Choose team.

• Click + sign to add the home page as a tab to the channel.

• Choose “SharePoint” and select a page to display.

• As a result, the home page is displayed perfectly as a new tab.

SharePoint web parts as tabs

You can use SharePoint Framework web parts as tabs in MS Teams. This will leverage SharePoint users to use Teams tab to easily reach their web-parts. This considerably eases Teams tab building process as the hosting of SharePoint Framework web parts is automatic without having to call external services. The tab also provides familiar web part edit panel to set tab properties.

Surfacing your SharePoint Framework solution as a Microsoft Teams tab

You can build Microsoft Teams tabs using SharePoint Framework v1.7 and later.

Note: Use npm install -g @microsoft/generator-sharepoint command to install/update to latest SharePoint Framework version. The functionality is only applicable in targeted release tenants.

Create a new web part project in your framework environment

• Create a new web part by following Step 2 – To Create SPFx web part from this link.
• One can do modification in the Web Part as per his/her requirement.

Packaging and deploying your web part to SharePoint

Make sure that you are in the project directory inside the console.

• Bundle your solution by executing below command

gulp bundle –ship

• Package your solution by executing below command

gulp package-solution –ship

The above command creates a package teams-tab-webpart.sppkg in sharepoint/solution folder in your project directory.

Now, you will need to deploy the generated package inside your tenant app catalog.

• Navigate to the app catalog site for your tenant.
• Upload or simply drag and drop the client-side package to the app catalog i.e. Apps for SharePoint list.

SharePoint prompts a dialog to deploy client-side solution package because this is a full-trust solution.

You can observe that the domain in the dialog says SharePoint Online because the content is rendered from the Office 365 CDN or served up from tenant app-catalog, based on tenant settings.

• Click Deploy.

Please note that there are no error messages inside the App Package Error Message column inside the app catalog.

Once deployed, the web part is directly available across SharePoint Online sites.

Packaging and deploying your web part as a Microsoft Teams tab

Your tenant needs to support Side Loading of external apps for Teams in order to deploy an app. You need to explicitly deploy Microsoft Teams app to a Team.

Below setting has to be enabled only once in a tenant to configure side-loading of apps in Teams.

Select Admin inside the app launcher to navigate to Microsoft 365 admin center.

Select Services & add-ins option under Services from the left menu.

Choose Microsoft Teams from the list of available services you can manage.

Under Tenant-wide Settings, expand Apps.

Note that the setting Allow sideloading of external apps is enabled under External Apps.

Click Save to save the changes.

Once we confirm that the side-loading is enabled, we can package Teams application to configure SharePoint Framework tab available in Microsoft Teams.

• Navigate to the Teams folder in the project directory for your solution.

• Create a zip file MyFirstSPFxTab.zip consisting manifest.json file and the images file in your preferred location.

Please note that manifest and images files should be at the root of the newly created zip file, else deployment will fail.

• Navigate to Microsoft Teams for your tenant by selecting Teams in the app launcher.

• Select a team you want to use to test the functionality and click Manage Team from the … menu.

• Navigate to the Apps tab.

• Click Upload a custom app from the bottom-right corner of Apps page.

Note: In the case where the setting is not available, verify whether sideloading is enabled in your tenant.

• Open MyFirstSPFxTab.zip from the Teams folder under your project directory.

• Make sure whether the app is visible in the list of available apps. You can observe a custom image along with the description of the solution.

• Go to a channel under the team where you uploaded the zip file.

• Click + in order to add a new tab to the channel.

• Select your newly created custom tab MyFirstTeamTab from the list of available apps.

• Observe “MyFirstTeamsTab” dialog containing exposed properties to parameterize the tab.

Note: You may be unable to change default properties of the tab or there may be issues adding a web part to the tab, as there is a known bug expected to be addressed by Microsoft in upcoming days.

You can see the code rendering in Microsoft Teams context after adding the custom tab on the channel. Web part theme will be as per respective SharePoint site.

Conclusion

MS Teams provides an effective way for users to collaborate in a team hub by bringing SharePoint functionality into it. By now, you know that SharePoint Online and Microsoft Teams are better together!

In the real world, the HR department is responsible in any organization to appoint new employee. Once he/she appoints any employee then he/she requires to contact Network Administrator and SharePoint Administrator. A Network Administrator creates this user in the AD, assign him into OU (if require) and AD group, and a SharePoint Administrator assigns this user into appropriate SharePoint group to provide him access on the organization SharePoint site. Thus, a chronological sequence is required to follow and it is time-consuming.

If HR department is having appropriate permission to access the organization SharePoint site then they can perform the tasks on behalf of Network and SharePoint Administrators through SharePoint itself via a web-part, an application page or an event receiver. Thus, the HR department can get rid of the above chronological sequence.

Before providing access to a new user in a SharePoint site, an organized user is required to perform certain steps as mentioned below:

1. Create a user in Active Directory
2. Add a user in Organizational Unit (if require)
3. Add a user in Active Directory group
4. Add a user in a SharePoint group

Ideally, the Active Directory tasks (steps 1 to 3) are performed by a user who is having permission on Active Directory Domain Services. Step 4 can be performed by a user who is having access to manage users in SharePoint groups of a SharePoint site.

Let’s see how one can provide this functionality in SharePoint site.

Note: The yellow highlighted points in below code are configurable as per the user requirement. This information must be kept somewhere where one can easily manage them. E.g. web.config, app.config, SharePoint list etc. 

Code Example

Let’s create a console application in C# to create users in the AD and assign them into SharePoint Group. The developer can also add a piece of code in SharePoint web-part, an application page or an event receiver with required modification.

First, get all the required user information from an end user and use them to create a user.

Try
       {
  // fetch the user details from input  
                Console.Write("Enter First name: ");
                var firstName = Console.ReadLine();
                Console.Write("Enter Last name: ");
                var lastName = Console.ReadLine();
                Console.Write("Enter Login name: ");
                var loginName = Console.ReadLine();
                Console.Write("Enter Employee ID: ");
                var employeeID = Console.ReadLine();
                Console.Write("Enter Email: ");
                var email = Console.ReadLine();
                Console.Write("Enter Phone number: ");
                var phoneNumber = Console.ReadLine();
                Console.Write("Enter Address: ");
                var address = Console.ReadLine();
 
                AddUserInSharePoint(firstName, lastName, loginName, employeeID, email, phoneNumber, address);
            }
       catch (Exception ex)
       {
            Console.WriteLine("Error: " + ex.Message);
       }
       Console.ReadLine();

Add User in SharePoint

 
public static void AddUserInSharePoint(string firstName, string lastName, string userLogonName,  string employeeID, string emailAddress, string telephone, string address)
{
   try
   {
      bool status = CreateUser(firstName, lastName, loginName, employeeID, email, phoneNumber, address);
 
      if (status)
      {
            PrincipalContext AD = new PrincipalContext(ContextType.Domain, "your     domain", "User Name", "Password");
            UserPrincipal u = new UserPrincipal(AD);
            // search for user  
            PrincipalSearcher search = new PrincipalSearcher(u);
            UserPrincipal result = (UserPrincipal)search.FindOne();
            search.Dispose();
            //Enter user to SharePoint group
            if (result != null)
            {
                  AddUserToDirectoryGroup(result.UserPrincipalName, "AD Group Name", "Your Domain", "DC=DC,DC=DC");
                  AddUserToSharePointGroup(result.SamAccountName, "SP Group Name"); // SamAccountName = User's AD login name
            }
       }
   }
   catch (DirectoryServicesCOMException ex)
   {
      Console.WriteLine("Error: " + ex.Message);
   }
}

Create User

private static bool CreateUser(string firstName, string lastName, string userLogonName,  string employeeID, string emailAddress, string telephone, string address)
 {
   // Creating the PrincipalContext
   PrincipalContext principalContext = null;
   try
   {
    principalContext = new PrincipalContext(ContextType.Domain, "your domain", "DC=DC,DC=DC");
    }
    catch (Exception ex)
    {
         Console.WriteLine("Error: " + ex.Message);
         throw ex;
    }
 
    // Check if user object already exists in the store
    UserPrincipal usr = UserPrincipal.FindByIdentity(principalContext, userLogonName);
    if (usr != null)
    {
         return false;
    }
 
    // Create the new UserPrincipal object
    UserPrincipal userPrincipal = new UserPrincipal(principalContext);
 
    if (lastName != null && lastName.Length > 0)
    { userPrincipal.Surname = lastName; }
 
    if (firstName != null && firstName.Length > 0)
    { userPrincipal.GivenName = firstName; }
 
    if (employeeID != null && employeeID.Length > 0)
    { userPrincipal.EmployeeId = employeeID; }
 
    if (emailAddress != null && emailAddress.Length > 0)
    { userPrincipal.EmailAddress = emailAddress; }
 
    if (telephone != null && telephone.Length > 0)
    { userPrincipal.VoiceTelephoneNumber = telephone; }
 
    if (userLogonName != null && userLogonName.Length > 0)
    { userPrincipal.SamAccountName = userLogonName; }
 
    string pwdOfNewlyCreatedUser = "abcde@@12345!~"; //Random or auto-generated password can be assigned.
 
    userPrincipal.SetPassword(pwdOfNewlyCreatedUser);
 
    userPrincipal.Enabled = true;
    userPrincipal.ExpirePasswordNow();
 
    try
    {
       userPrincipal.Save();
    }
    catch (Exception ex)
    {
       Console.WriteLine("Error: " + ex.Message);
       return false;
    }
 
    if (userPrincipal.GetUnderlyingObjectType() == typeof(DirectoryEntry))
    {
       DirectoryEntry entry = (DirectoryEntry)userPrincipal.GetUnderlyingObject();
       if (address != null && address.Length > 0)
       { entry.Properties["streetAddress"].Value = address; }
 
try
       {
          entry.CommitChanges();
       }
       catch (Exception ex)
       {
          Console.WriteLine("Error: " + ex.Message);
          return false;
       }
    }
 
    return true;
   }

Add User to Directory Group

 
public static void AddUserToDirectoryGroup(string userId, string groupName, string domain, string domainController)
{
   try
   {
      using (PrincipalContext pc = new PrincipalContext(ContextType.Domain, domain, domainController))
      {
         GroupPrincipal group = GroupPrincipal.FindByIdentity(pc, groupName);
         group.Members.Add(pc, IdentityType.UserPrincipalName, userId);
         group.Save();
      }
   }
   catch (DirectoryServicesCOMException ex)
   {
      Console.WriteLine("Error: " + ex.Message);
   }
}

Add User to SharePoint Group

 
private static void AddUserToSharePointGroup(string userLoginName, string userGroupName)
{
    //Executes this method with Full Control rights even if the user does not otherwise have Full Control
    SPSecurity.RunWithElevatedPrivileges(delegate
    {
        using (SPSite spSite = new SPSite("Your site url"))
        {
            using (SPWeb spWeb = spSite.OpenWeb())
            {
                try
                {
                    //Allow updating of some sharepoint lists, (here spUsers, spGroups etc...)
                    spWeb.AllowUnsafeUpdates = true;
 
                    SPUser spUser = spWeb.EnsureUser(userLoginName);
 
                    if (spUser != null)
                    {
                        SPGroup spGroup = spWeb.Groups[userGroupName];
 
                        if (spGroup != null)
                        {
                            spGroup.AddUser(spUser);
                        }
                    }
                }
                catch (Exception ex)
                {
                    Console.WriteLine("Error: " + ex.Message);
                }
                finally
                {
                    spWeb.AllowUnsafeUpdates = false;
                }
            }
        }
    });
}

Output

On successful execution of the AddUserInSharePoint method, the user will be added to the Active directory. You can verify the same by logging into the Active Directory. Refer the below screenshots for same.

On completion of AddUserToSharePointGroup method, the user will be added to a SharePoint group as shown in the screenshot below.

Conclusion

A new user can be created and assigned into the respective AD and SharePoint groups by a user who is having appropriate permission on a SharePoint site. The various information related to the user which is provided at a creation time can be viewed in SharePoint if the User Profile Synchronization Service is configured. Various operations can be performed in AD and SharePoint related to a user management.

This blog is a continuation in the series of blogs for implementing offline capability in PowerApps with SharePoint.

In the first part, we streamlined the process to enable and configure offline capabilities in your applications.

The blog caters the information regarding the basic idea of PowerApps which is a tool for building the mobile apps. While creating the blog we have assumed that you have a good knowledge regarding the PowerApps so only the brief information is provided considering the same and implementation steps are mentioned right from the scratch.

What is Power BI?

Power BI is a collection of hundreds of connectors that work together to turn the unrelated sources of data into coherent, attractive and interactive insights. It converts your data from different data sources to interactive dashboards and attractive reports. Power BI provides services – Power BI desktop, services based on SaaS, hundreds of connectors and Power BI mobile apps for different platforms. Whether your data is stored in an Excel workbook or stored in SQL servers or in a collection of cloud-based plus on-premises hybrid warehouses, Power BI allows you to connect different data sources, convert it to meaningful insights and share that with anyone.

Google Analytics enables you to optimize your advertising ROI and track your sites and applications. It helps you get a better understanding of your business’ stakeholders. Google analytics brings with it open-source tools to analyze data for your applications.

From the title of the blog, the first question comes in mind is “What is PowerShell?”

The answer is: It is an object-oriented automation engine and scripting language developed by Microsoft and built on the .Net framework. It has an interactive command-line shell where the user can execute commands to fulfill their tasks.

Huge organizations have many people working in the same organization in different regions across the globe having different languages for communication. In general scenario regional language is more in to preference. As internet facilities are now easily available, websites are the most favorable and less expensive equipment for marketing purpose. Websites should be capable enough to provide content suitable to their target audiences across the globe. But maintaining the different sites with different languages is very difficult for content redundancy point of view.

The scenario to deal with creating files in document libraries, adding/updating/deleting items in the SharePoint list, at times requirement emerges to perform some action on such events like sending notification, data manipulation on SharePoint lists or libraries, etc.

Terms like Chatbot, Artificial Intelligence and Personal Assistants are in trends since past few years. All major companies have initiated to incorporate such intelligent techniques in their respective business verticals. Like – more than 11,000 chatbots in Facebook messenger app, since April 2016 and many other examples are also available in the market.

Chatbots concept is growing as the latest standard of automation in the software development by simplifying the method for a user to receive desired information. Persona/avatar – Chatbot increases work productivity, offers information, boost ROI and decreases the searching time for B2C, B2B and B2E type of organization software solutions. Chatbot not only reverts back in text format but also in form of images, files, videos, etc.

“The cloud” allows to securely access web-based computing services that reside off-premises and are supported by the third party. The Advent of cloud era is looming nowadays as cloud-based services can be accessed virtually anywhere and on any device with an internet connectivity.

In this cloud era, Microsoft surprised enterprises and developers with Office 365. In Office 365, right from information storage to computation and software are maintained and established remotely on the secured servers possessed by Microsoft. Most recent features of Office 365 – SharePoint Development, Delve, Yammer and Dynamics 365, a Cloud-based solution, nowadays are availed by clients/organization to enhance business collaboration.

SharePoint would continue to be a very effective platform for business use and for many more. The enhancements only serve to boost the performance of the platform.

When it comes to the future of SharePoint Development, Microsoft would continue to provide on-premises version of the platform as long as there is market demand. Furthermore, Microsoft recognizes that on-premises would be around for some time, if not mostly in a form of hybrid environments.