Steps to enable Multi-Language for Portal

1) Enable the required language on the Dynamics CRM instance

The user would need to have ‘System Customizer’ OR ‘System Administrator’ role to perform the action below

Go to Settings -> Administration -> Languages

Select the desired language to be installed and hit the ‘Apply’ button

In the screenshot below ‘Spanish’ language has been enabled.

Note: This action can take time depending on the number of languages selected and is ideally recommended to be performed during non-peak hours.Lag-setting

2) Within your Dynamics CRM instance go to Portals -> Websites and open the required website record which needs to be enabled for multi-language.

3) Click on the ‘+’ button next to the ‘Supported Languages’ sub-grid to add a new ‘Website Language’ record.


4) On the ‘Website Language’ form set the below fields and save the record.

Portal Language: Newly added language in #1 above

Publishing State: Published


Note: This action would automatically generate new records (related to newly provisioned language)  for all the language enabled OOB Portal records, however, it won’t have the translated values. The translation would need to be done manually.

E.g.: There will now be 2 records for each ‘content snippet’ record. Open these records (related to the newly provisioned language)  and update the values with the translated text. Do the same for all the other required entities.


5) The language menu should now be available on the Portal. Changing the language on the Portal would automatically refresh the portal with the translated values.


Microsoft CSP Pain Points Lead Partner To Develop Partner-Facing Solution

Recent press coverage and article from Scott Bekker at Redmond channel partner details a conversation with Ismail Nalwala and the value of Work 365 as a solution for CSP partners. Whether you are direct or indirect Work 365 can help partners run an efficient cloud business as described by Rosalyn Arntzen from Amaxra.

Being Customer Zero On Dynamics 365 – A Microsoft Partners Perspective

Digital Transformation and Customer Experience are two areas that are on top of mind for executives and CIOs everywhere. Dynamics 365 is one of those applications that is at the center of Digital Transformation for Microsoft and its partners. Being a Microsoft partner is not an exclusive club. It’s a challenging marketplace with tight margins and innovation happening rapidly both at Microsoft and with partners. However, there are some perks of being a partner like receiving the Internal Use Rights (IURs) to some of the best technology products like Office 365 and Dynamics 365. The idea is that Partners need to be customer zero, use the products to be able to sell the products. Dynamics 365 formerly Dynamics CRM or CRM online, is one of those products which can be used to run your entire business! As we released Work 365 for Partners I was recounting our journey– which involved us trying to make the most use of the application to keep us relevant and stay ahead. In reflecting back, we were Digitally Transforming while attempting to deliver great Customer Experience.

As a Microsoft Partner, we had access to early versions of Dynamics CRM. Today we are using Dynamics CRM in every function of our business but it wasn’t always like that. I wanted to share in this article our own journey to see if I can relate this back to other partners who are thinking of where to start or get feedback from those that are ahead of us on what we could be doing.

We started with the Sales module to have a contact management system in place in late 2010. We went from Contacts to Opportunity Tracking and then onward with implementing one thing after the other and eventually getting the whole company to use the system from Sales, Service, Delivery to Accounting. As a Dynamics app developer, we needed a way to deliver and manage Work 365 licenses. The manual license delivery and trial processes were time-consuming and error-prone. Once we built this license delivery mechanism in Dynamics CRM, our system was no longer just a data repository but more of a provisioning and business critical application. The graphic below depicts the different functional pieces we implemented over the years to digitize our business.


After we implemented a piece of functionality we would then continue with the rounds of

  • Tweaking and adding fields and forms
  • Setting up notifications and workflow automation
  • Fixing and managing permissions

The most important thing for us was the more functional areas we added the more user adoption we had and the greater the ROI. We started to see the complete 360Degree of our customers and provide better customer experiences with every new service and functional line. We integrated 3rd Party Partner applications like ClickDimensions for marketing Automation, Xperido for document generation, DocuSign for signature and contract management. And every year we had to work with the inevitable upgrade cycles with new feature and compatibility.

Our approach to Digital Transformation was not to invent a Digital strategy but to digitize our current strategy. As a Microsoft CSP, we needed a way to keep up with the growth, provide great service, differentiate ourselves and keep our costs low. We used the Netflix model which I will discuss specifics in a separate article. Our strategy was:

  1. Create differentiated products and services
  2. Streamline our service offering and our systems to manage the cost
  3. Provide multiple service channels to customers including self-service

To that effect, we leveraged our experience of developing apps for Dynamics, e-commerce and Dynamics 365 configuration to create Work 365 to manage our CSP and customer-facing services.

Back to the Beginning

Our biggest learning along with our Digital transformation journey as a Microsoft CSP partner:

CRM implementations are never done and you must work at it endlessly to improve and fine-tune the processes.

Leverage the IURs and create application density to realize the investment. Application density happens by implementing connected processes in one system where users across different functions have efficiency gains from access to data, reduced training costs and process automation.

Don’t worry about developing a digital strategy- but more importantly digitize your current strategy. Be the customer zero in using the Cloud services and products so that you can train the teams and serve it up to your own customers.

Please share your thoughts about how you use your application IURs, tackle Digital transformation and provide exceptional customer experience.

About the author
Ismail Nalwala

Click on the link to view the original post –

Framework For Business to Evaluate Tools For Business Process Automation

Business process automation (BPA) is the automation of manual paper-based processes using tools and technology. BPA can help an organization reduce cost and increase efficiency.

Once a decision to implement business process automation has been taken, choosing the right tool is the next significant consideration. While there are many tools available for BPA, and a discussion around these is imminent; the criteria for evaluating these tools must first be identified. Each organization may weigh these criteria differently and a framework has been provided to adjust the relative weight of the criteria against each other later in this series.

1 In-House Skillset

Organizations often have dedicated IT teams for improving and enhancing their internal systems. Selection of a tool should consider the level of the skillset of the in-house team and Power Users. Often, BPA vendors claim their tool make it easy for business users to create or modify processes that require some understanding of logic and being aware of basic programming constructs like conditions, loops and such. Alternatively, the organization may choose to outsource the requirement to an external vendor. In the case of the former, not considering this criterion in the tool selection process may often lead to an expensive and long drawn learning curve.

2 Form Complexity

Forms are the user interface element of a business process and have a key impact on determining the success of any business process automation. The complexity of a form designer varies from a simple drag-and-drop configuration to development by backend coding. Complexity also depends upon the type of data that needs to be populated as well as the data that needs to be captured by the end user. A complex form may have custom validations, parent/child relationships between data elements or require data from external systems.

3 Process Complexity

Gauging the complexity of the actual business process is another evaluation criterion. The process can either be sequential (series of steps performed one after the other) or it may require a non-sequential graph like behavior (often called as a state machine). A complex process may fetch or store data from an external system or even have an external trigger. Consider the case of a business process where a contract must be digitally signed upon creation of a customer record in an external CRM system. A typical business process will entail multiple outcomes, for example, the reviewer may not Reject the request but send it back to the author for changes; this could go around multiple times and so on.

4 Mobile Enabled

Today’s business environment is becoming increasingly diverse and remote. Businesses expect their employees to work from anywhere, either online or offline. Mobile-enabled forms can prove to be that secret sauce for the adoption of the system organization-wide. The added benefit of using the native mobile functionality like the camera or GPS opens new possibilities that are just not possible using a traditional PC based approach.

5 Document Generation

Paper-based record-keeping is an expensive and time-consuming part of any business. Often businesses print copies of ‘approved’ digital records because the automation is ineffective at generating the full document as required by the business. Even after automating the business process, one may still need the physical document for contract signatures, or to create a template before sending to the external vendor. Document generation allows the creation of a digital document from data, eliminating the need for paper altogether.

6 External System Connectivity

Business processes often require integration with systems outside the scope of the automation environment, either to leverage the data, services or as a trigger to initiate the process. Consider an example where a business process makes decisions on information available in an external HRMS system, such as approval levels for expenses. The number of connectors available for a tool will provide flexibility to integrate with current and future systems that the organization may adopt.

7 Requirement Stability

Business requirements regularly change with an ever-evolving business landscape, an introduction of new external influencers (regulatory requirements, market changes, competitive situations); business processes must adapt to embrace these changes. The selection of a BPA tool should consider this inevitability and the organization should favor a tool that allows for an agile implementation process. Not considering this may lead to re-work which will eventually increase the cost and cause unplanned delays.

8 On-premise, Cloud or Hybrid

Businesses should review the application landscape. Are they primarily on-premise based or have they embraced cloud technologies or have a mix of both? What are plans for the near term and long term? Running a process on either premise may require working with data/services on the other. For example, a process (in the cloud) may require HR data sitting in an ERP on-premise. While the cloud provides many advantages, there are specific use cases where this may not be the right choice. There are different architectural considerations when deploying on-premise or on cloud and being cognizant of these upfront will help avoid brittle workarounds in the future.

9 Insights

Someone once said, “you can’t manage, what you can’t measure”. This is true with business processes as with all things in life. The effectiveness of a business process is measured through adoption, adherence to SLAs and other metrics. The BPA tool should lend itself well to providing analytics for your business process that can be reviewed by the process owner as well as the organization leadership. This can help iron out kinks in the process, identify and eliminate bottlenecks, define a framework to drive performance and overall get a sense of the return on investment.

10 Budget, Licensing, and Support

This is an obvious one, but one that often takes a high priority for most businesses. There are many tools available, some cost good money, some even free! The other factor for consideration is the licensing model. Does the tool incur an upfront capital expense or does it allow for ongoing operational expenses? Which is better suited for your organization? What are the upgrade paths and release cycles? What sort of support is provided by the organization? There are multiple licensing models, per-server, per-workflow, per-user and even per-run – mapping this against your business use-cases will help to make a decision that is cost-effective and a right fit for your organization.

How to Identify the Right Business Process Automation (BPA) Tools for Your Organization

The previous blog provided a framework for a business to evaluate tools for business process automation. This blog explores some of the popular business process automation (BPA) tools that are popular when working with Microsoft SharePoint technologies and how they fare against the criteria that we defined in our previous blog. Ratings are provided on a scale of 1 to 10, with 1 being least favorable and 10 being most favorable.

SharePoint Designer Workflows

According to Microsoft, SharePoint Designer (SPD) is a tool for rapid development of SharePoint applications. SPD includes the ability to create workflows native to the SharePoint platform. These are no-code workflow solutions that manage simple to medium complexity business processes in an organization. Forms created for SPD workflows often use HTML and/or InfoPath as their underlying technologies. Please note that since SharePoint 2013, Microsoft has introduced the Workflow Manager, where workflows can be designed visually using Visio. For this blog, we refer to both these technologies under the SPD moniker.

Microsoft PowerApps & Flow

Microsoft defines Flow as “a cloud-based service that enables business users to automate business tasks and processes across applications and services”. PowerApps is defined as “an enterprise service for innovators everywhere to connect, create and share business apps on any device in minutes”. PowerApps & Flow are in many ways Microsoft’s successors to InfoPath & SharePoint Designer. They are included as part of most of Microsoft’s cloud offerings (premium versions are chargeable separately) and are geared towards regular business users partaking in the automation process.

Nintex Workflow & Forms

Nintex is a third-party workflow automation tool, primarily used for SharePoint and Office 365. It leverages SharePoint’s native workflow engine and does not require additional infrastructure or client software. They feature drag-drop user experience for creation and modification of Workflows and Forms along with a plethora of other features that make it seamless to create, manage and monitor business processes in the organization.

The comparison presented below is based on the features that the individual product offers out-of-box or after minimal customization efforts. It does not possibilities that are an outcome of applying for extensions via custom coding.

1 In-House Skillset

Strictly speaking, all three options do not require custom coding. Having said that, SharePoint Designer presents the least visually interactive way of developing workflows. (Visio can be used as a tool to enhance this experience). SPD workflows are created using the SharePoint Designer tool and provide basic workflow capabilities. There are a limited set of built-in actions and anything more will require custom coding. The forms built for SPD workflows face the same issue as these are designed using either HTML/javascript or using InfoPath, which requires considerable skills and understanding to get anything more than the basics accomplished.

SharePoint Designer Workflows

Microsoft PowerApps & Flow

Nintex Workflow & Forms




Both other options provide intuitive drag-drop interfaces along with a gamut of other techniques that make it easier for users to implement business process automation. Most vendors portray BPA tools as easy for end users to make changes. While this is true to some extent, implementing BPA does require a sense of logic programming and is really geared towards power users.

2 Form Complexity

When using SPD to create forms for data collection there are two solutions available (SharePoint out-of-box forms and InfoPath forms). InfoPath provides the ability to develop forms with multiple input elements: text boxes, radio boxes, drop-downs as well as repeating groups/sections of controls. However, InfoPath is not intuitive to use and deployment of the forms require administrative access once you go beyond the basics. The alternative is SharePoint ‘out-of-box’ forms which can be used to create simple forms.

With PowerApps it is possible to create forms by writing Excel type functions for the business logic. It also supports HTML coding for branding but does not allow JavaScript which limits the ability of Power Users. However, PowerApps provides a bunch of starter templates that may be a good place to get started.

Nintex forms allow for different layouts depending on the users’ device. Furthermore, complex forms with repeating sections, two-way automatic data binding and easy access to SharePoint APIs (to name a few) can be built.

SharePoint Designer Workflows

Microsoft PowerApps & Flow Nintex Workflow & Forms
3.5 8.0



3 Process Complexity

SharePoint Designer provides multiple pre-built actions that can be configured to create simple to medium complexity workflows. SharePoint Designer workflow is sequential which means that it only allows the creation of workflows that have a forward-only path.

Microsoft Flow is targeted towards actions performed by individual end users. It also has

many pre-built templates using which one can create simple to complex workflows. Flow does not directly support state machine workflows which allow for non-sequential execution of processes. While Flow provides many connectors and templates, it requires multiple actions to accomplish a single task, which can often be frustrating, especially for new users and an encumbering task for large complex workflows.

Nintex provides a drag and drops user interface to quickly create and edit workflows. The enterprise version has more than 200 workflow actions pre-built. Unlike other options listed here, Nintex allows you to create State Machine workflow (capable of flowing in any sequence and through any amount of iterations).

SharePoint Designer Workflows

Microsoft PowerApps & Flow Nintex Workflow & Forms
3.5 6.5



4 Mobile Enabled

SharePoint Designer forms (built using InfoPath) and HTML devices are not automatically optimized for mobile devices. While these forms may render on a mobile screen, the experience is often less than ideal. SharePoint 2013 onwards introduced the concept of device channels, but that requires the creation of mobile-specific master pages for each device channel. Having said that, the new SharePoint Modern Experience provides responsive forms. In either case, access to native mobile capabilities is not present.

PowerApps, on the other hand, provides a mobile-first view towards forms. It supports native mobile interfaces such as access to GPS, Camera, Signal Connection, Location, and Accelerometer. The PowerApps app is available from Apple and Google stores and can be installed on users’ devices. It also supports Push Notifications which are a great way to alert users to imminent actions. PowerApps also provide offline capabilities.

While Nintex forms are primarily designed for the PC, they provide adequate support for mobility. These forms can be run within a mobile browser or through a fully native mobile application that can leverage some device capabilities such as Camera and GPS signals. The Nintex AppStudio addon allows for the creation of custom-branded native mobile apps that can be mass deployed via your corporate MDM solution. Nintex also provides offline capabilities for the native mobile applications.

SharePoint Designer Workflows

Microsoft PowerApps & Flow Nintex Workflow & Forms
2.0 8.5



5 Document Generation

SharePoint Designer workflow does not have an out-of-box action to generate a document but using a SharePoint feature called “property promotion-demotion”, it is possible to inject some basic information into a document template. The generated template could then be converted to a PDF using SharePoint Word Automation services (not available for SharePoint Online).

Currently, Flow does not provide any specific Document Generation capabilities, much like SharePoint Designer workflows. However, Flow provides built-in connectors for DocuSign and Adobe Sign. Both these products allow for document templates to be defined and for signatures to be triggered on these templates via Flow.

Due to Nintex’s acquisition of Drawloop, Nintex now has a document generation feature built right into their workflow tool. The user experience is intuitive and you can quickly create a document template, map properties from the workflow into the document and generate Word or PDFs document.

SharePoint Designer Workflows

Microsoft PowerApps & Flow Nintex Workflow & Forms
3.0 5.0



6 External System Connectivity

SharePoint Designer Workflows do not have pre-built connectors for any third-party applications, however, an HTTP web service connector is available. In theory, it is possible for a developer to build connectors to other applications and expose these via an HTTP web-service, but this approach is complex, time-consuming and difficult to maintain.

Both Nintex and Flow have several prebuilt connectors for popular systems such as Microsoft Dynamics, DocuSign, Twilio, SharePoint, Exchange, Azure, and others. It is worth pointing out that currently, Flow provides many, many more connectors than those available with Nintex (some of these are only available via a Premium subscription to Flow).

SharePoint Designer Workflows

Microsoft PowerApps & Flow Nintex Workflow & Forms
1.0 8.5



7 Requirement Stability

Business Processes developed using SharePoint Designer Workflows, to a high degree of probability will involve some custom coding via Web Services or other mechanisms. We often find that these have been put together in a hurry to meet business deadlines. Compounding that effect over several iterations leads to a system that is or tending to be unmaintainable. Testing takes longer and there is a high probability of unwanted side effects.

Both Microsoft Flow & Nintex offer GUI based drag-drop interfaces, favoring visual paradigms over coded ones. This reduces, if not eliminates the need for custom coding and changes are incorporated with relative ease and stability as compared to those developed with SPD.

It is noteworthy that Nintex provides some actions over Microsoft Flow that further reduce steps required to accomplish a specific task. Consider this example, an HR executive creates entries into a list of candidates that are about to join. The system should email these documents to the candidate for review. With Flow, separate steps are required to retrieve the item and the contents of the document and can take several steps to accomplish this; with Nintex this is a two-step process.

SharePoint Designer Workflows

Microsoft PowerApps & Flow Nintex Workflow & Forms
3.0 7.5



8 On-premise, Cloud or Hybrid

SharePoint Designer Workflows work within SharePoint Online and SharePoint On-premise. There isn’t much difference to these except that the workflows cannot contain server-side code with SharePoint Online. Any custom code should be written and hosted outside of the SharePoint Online environment (say, as a Web Service in Azure). For cross-premise connectivity, SPD workflows will require the use of the “Call HTTP Web Service” action, which will require some level of custom coding and a whole heap of security planning.

Microsoft Flow is a cloud-only offering. As of today, there is no on-premise version of Flow and neither has one been announced. However, Microsoft makes cross-premise connectivity much easier using the “on-premises data gateway”, which allows for connecting to on-premise business data without the need to poke holes in the firewall or writing custom services. This gateway currently supports connections to SQL Server, SharePoint, Oracle, Informix, Filesystem and DB2 systems.

Nintex provides ‘premise-specific’ flavors of the tool, there is Nintex for SharePoint (on-premise), Nintex for Office 365 (online) and Nintex Workflow Cloud (independent online offering). Despite having such a broad-spectrum product portfolio, cross-premise connectivity with Nintex requires techniques like that of SharePoint Designer Workflows. Nintex provides options for customers on any-premise but does not deliver when it comes to cross-premise connectivity.

SharePoint Designer Workflows

Microsoft PowerApps & Flow Nintex Workflow & Forms
2.0 9.0



9 Insights

With SharePoint Designer Workflows, logging and data tracks must be manually maintained within the workflow. There are no automated means by which process metrics will be tracked. For consistent reporting, a significant upfront design is required; yet the effectiveness of the reporting will be dependent on the individual authoring the process automation.

Microsoft Flow provides basic reporting using Flow Analytics, a premium feature included as part of the P2 license. In its current form, Flow Analytics provides three metrics Total Flow runs by day, Number of flow runs and Flow runs trend. For custom business-specific analytics, Microsoft Flow currently suffers from the same challenges as those of SharePoint Designer Workflows. SLA monitoring and measurement is yet another item that is currently missing from both SPD and Flow.

Nintex Hawkeye is the process analytics offering from Nintex. Marketed as “Process Intelligence and Workflow Analytics”, it features the concept of lenses which are perspectives on the process data. There are primarily two types of lenses, Usage lens which provides low-level consumption based metrics and Process lens, which provide information that is specific to a business process. There is some work required on part of the process author to provide effective data for a Process lens, but this is as easy as ensuring certain ‘beacons’ are placed within the workflow (using a drag-drop paradigm).

SharePoint Designer Workflows

Microsoft PowerApps & Flow Nintex Workflow & Forms
1.0 3.0



10 Budget and Licensing

For organizations with SharePoint on-premise (2010 and later) and/or SharePoint Online, SPD workflows are free to author and run. If the organization chooses to author workflows using the Workflow Manager capabilities, a Visio 2013 Professional license is required for each user that authors the workflow.

There are currently four plans of Microsoft Flow, ranging from Free Plan (no-cost) to Plan 2 ($15/user/month). Each plan offers different maximum runs of Flow per day and different frequencies of the Flow runs (interval between each run of the Flow). There is no SLA for the Free Plan, whereas the other plans offer a 99.9% availability SLA by Microsoft. While the base cost for Flow is per-user, there is an underlying cost associated with Flow Runs – each unit of 50,000 flow runs over and above the allocated quota per plan (aggregated across all users) will cost $40/month. For full details on Flow plans and pricing, please refer to

Nintex offers three licensing models, per workflow (authored), per user and per server (on-premise only). There is no additional cost for workflows run. These prices are not public but are available through Nintex Partners. They tend to be higher than Flow on a per-user basis. The per workflow model allows the use of Nintex products across on-premise and online environments simultaneously and is the most flexible option available if the organization has online as well as on-premise environments.

SharePoint Designer Workflows

Microsoft PowerApps & Flow Nintex Workflow & Forms
8.0 6.5



The table below summarizes the scores for the options against our defined criteria. It is important to note that different organizations will assign different relative importance to each criterion which will ultimately result in a choice that is a best-fit for them. To this effect, an excel sheet is attached which provides the option to assign weights to the criteria and provides a weighted average score of the options listed.


SharePoint Designer Workflows

Flow & PowerApps

Nintex Workflow and Forms

In-house Skillset




Forms Complexity




Process Complexity




Mobile Enabled




Document Generation




External System Connectivity




Requirement Stability




On-premsie, Cloud or Hybrid








Budgets & Licensing




How to Setup SharePoint Communication Site Template for a Company-Wide Intranet

Organisations think SharePoint portal as a centralized place to get various information such as documents, news, team members, departments, etc.

At its core, an Intranet Portal is used to displaying information to business users and formal contents. For the majority of the organizations, SharePoint is just a common platform to come together to share information and communicate but the real motto is not only collaborating but being productive.

The only thing that makes any organization a successful one, only by choosing the right tools to achieve their goals. The productivity tools make business users lives well-organized, exciting, easier and more productive.

Let’s ask one question

The SharePoint Modern workplace may consist of the home page, Procedures, and manuals, corporate news or announcement but does it provide the relevant information as per the business users need or interest.

Next step

The motto of an organization is to provide push information through publishing, select collaboration tools, work together and smarter.

How to achieve

Organisations need to move towards a new world with three components.

1. Communicate using Communication Portals

2. Modern workplace for productive tools

3. Personalized workspace with Dashboard

In a real-world scenario, when you want to broadcast a message, share a story or publish the content for readers, or launch a product or service then the Communication site is for you. You also need to understand the various parameters while setting up the SharePoint intranet and extranet, the nature of the line of businesses, governance, content authors and quantity. We helped numerous organization to setup SharePoint intranet in accordance with their requirements, respective branding, and audience, so that they become more productive in a smart way.

Communication site can be used for Training, Policies and guidelines, a new initiative or marketing campaign and so on.

You can select any one of the templates to start with, nonetheless, you can add, remove, or rearrange web parts anytime.

Create a Communication site

1.       Sign in to Office 365

2.       In the top left corner of the page, select the app launcher icon and then select the SharePoint tile. If you don’t see the SharePoint tile, click the Sites tile or All if SharePoint is not visible.

3.       At the top of the SharePoint home page, click + Create site and choose the Communication site option.


4.       Select one of the following site designs:

  • Topic to share information such as news, events, and other content.
  • Showcase to use photos or images to showcase a product, team, or event.
  • Blank to create your own design.


5.       Give your new communication site a name and, in the Site description box, add some text that lets people know the purpose of your site.

6.       Click Finish. Your site will be created and will appear on the sites you’re following. Your site will not inherit the permission settings or navigation of other sites.

Setting the Layout for Communication Site

The new layout section offers you to change the page layout for any of the site designs to display your content effectively.


Note: You can’t really disable Communication site creation unless you remove the Create site button from the SharePoint home.

While these are the high-level guidelines for helping you to choose the right type of site, however, richer capabilities and features are on its way in coming months. Our goal is you to keep you updated with the emerging changes, you can read our SharePoint Blogs or get our newsletter directly in your mailbox.

You can now use new modern site templates to make a digital workplace and leverage Communication sites for a global SharePoint intranet.

  • Please look out for the next blog where I will be sharing more details on how to use this feature and the benefits.
  • Like this blog or share your thoughts. Have you tried using this?
  • This feature is still in preview and has been introduced for SharePoint online. If you are taking advantage of this for your intranet contact us.
  • Add information about how this fits into the Microsoft
  • Talk about how to do this without communication sites.

SharePoint Hassle Free Migration with Sharegate & Metalogix

The migration of existing business content to SharePoint 2016 or SharePoint Online (including Office 365) is not a small task. Ideally, organizations should spend time discovering and auditing the content, then creating an ideal information architecture to improve upon existing models. Finally, whenever possible, comprehensive testing before and after the migration should be performed to minimize risk. Major factors such as SharePoint customizations and external system integration need to be fully fleshed out before the migration work can begin.

Move your business to Office 365 or SharePoint

Migration and upgrade projects are an opportunity to free SharePoint content so that end-users, developers, and administrators can all benefit from improved information architecture and functionality.

To complete the migration activity successfully to SharePoint 2016 on-premises or SharePoint Online (Cloud Provider under Office 365), need good planning and analysis. Many types of migration approaches exist, it is important to organizations (Architects) understand that they do not have to stick to a particular migration approach.

Gain full visibility and understand the risks

Migrations are not so much about the technical act of moving the data (although very important) but more about the planning that goes into preparing for the migration.

Migration could be defined as three separate activities.


Migration Challenges

Phased: Should be flexible based on end-user needs and not the limitations of the technology.

Iterative: Shouldn’t be limited by the number of migrations attempts but should allow users to provide their feedback.

Error-prone: There is no simple step to “Migrate”. Keep trying until you get it right via pre-checks, customizations or third-party tools (Sharegate or Metalogix).

Not the end goal: The ultimate goal should be a stable environment, relevant metadata, discoverable content and happy end users.

Enforce your governance and compliance policies

Governance is about mitigating risks, whether managing your intellectual property from creation through archival/deletion or meeting your auditing, compliance and other legal requirements. It’s about ensuring data integrity, enforcing your change management processes, and helping you to determine the education and training needed for each role, from the end user to farm administrator.

Once you have mapped your requirements against SharePoint’s capabilities, you’ll be in a much better position to be able to determine whether you should build or buy to meet those requirements. Document your environmental constraints, such as your data retention and compliance requirements, as well as Microsoft’s recommendations around site and storage limitations, performance tuning, and other SharePoint standards.

You need to review all the changes on a regular basis as you add your new workloads and refine your governance strategy until you find the right meeting cadence going forward and iterate on your strategy, as needed.

Protect your enterprise content

Archiving – An act of hiding content from users for a specific time period which could be accessed post time expiration.

Retention, protection and auditing Policy – help you guarantee your records are properly retained. Audit trails are in place to provide proof to internal and external auditors that records were retained appropriately.

Discovery and Record Management – To store and protect business records.

Migration Approach

  1. Microsoft introduced the SharePoint Migration Tool which could help Organizations to achieve the milestone. However, this product is still in BETA release.
  2. Using Third Party Products (Sharegate, Metalogix)

We not only helped our various clients to just migrate their legacy system to the latest SharePoint platform but also transforming the existing processes to meet their business requirements and operational processes. The planning and strategies could differ for each organization but primary roadmap remains the same.



Migration is not just about moving data to a new platform but using the move as an opportunity to realize your true operational vision and to get your end users and other stakeholders involved in the process. It’s a time to consider all of your business and environmental constraints, thinking about security, compliance, performance, and simplifying the platform for your end users and administrators alike.

How to Setup Communication Site in SharePoint Online

Microsoft recently announced the rollout of modern Communication sites in Office 356. This new template is available only for those who enrolled for “First Release user in your tenant“. You will now have a new site template “Communication site” along with the Team site.

The good news is that in coming months it would be released full worldwide for all Office 365 customers.

In the past, SharePoint publishing sites were “Classic” SharePoint Online (SPO) sites where publishing feature providing you with features as publishing pages in your intranet site, richer navigation configuration experience, etc.

Classic SPO sites lacked few key features such as responsiveness, dynamic content and provided a limited user experience.

Communication sites are intended to showcase your product or service, inform and engage others with the enhanced user experience. You can share news, stories, statistical reports and other information in a visually compelling format.

It’s a site collection that is responsive, mobile friendly and adapted to display information in a dynamic way.

Just keep in mind, Communication sites are not intended to build Intranets, they are just additional blocks for you overall Intranet. You also need to understand the various parameters while setting up the SharePoint intranet and extranet, the nature of the line of businesses, governance, content authors and quantity.

Create a Communication site

  1. Sign in to Office 365
  2. In the top left corner of the page, select the app launcher icon and then select the SharePoint tile. If you don’t see the SharePoint tile, click the Sites tile or All if SharePoint is not visible.
  3. At the top of the SharePoint home page, click + Create site and choose the Communication site option.


4. Select one of the following site designs:

  • Topic to share information such as news, events, and other content.
  • Showcase to use photos or images to showcase a product, team, or event.
  • Blank to create your own design.


5. Give your new communication site a name and, in the Site description box, add some text that lets people know the purpose of your site.

6. Click Finish. Your site will be created and will appear on the sites you’re following. Your site will not inherit the permission settings or navigation of other sites.

Setting the Layout for Communication Site

The new layout section offers you to change the page layout for any of the site designs to display your content effectively.


Note: You can’t really disable Communication site creation unless you remove the Create site button from the SharePoint home.

The motto of an organization is to provide push information through publishing, select collaboration tools, work together and smarter.

How to achieve

Organisations need to move towards a new world with three components.

  • Communicate using Communication Portals
  • Modern workplace for productive tools
  • Personalized workspace with Dashboard


Organizations think SharePoint portal as a centralized place to get various information such as documents, news, team members, departments, etc.

You can now use new modern site templates to make a digital workplace and leverage Communication sites for a global SharePoint intranet. By choosing the right tools, you can make business user’s lives well-organized, exciting, and easier.  You can implement and transform your business process automation (BPA) to achieve your goals.

There are richer capabilities and features are on its way and I will be covering and sharing those features in details at “SharePoint Blogs”.

In my next blog, I will talk about “Modern Team Site” template, stay tuned…

Custom Icons for List View in Dynamics 365

Visualization is always helpful when it comes to identifying and highlight the set of data. With the new feature provided by Microsoft in Dynamics 365, it is possible to display list views with Icons or any kind of graphical representation to make the desired data stand out.

Here are the steps to follow.

In my example, I want to display indicators for active accounts list according to their membership statuses in Green (Current), Grey (Dropped) and Blue (Prospective).Therefore, the things which we need are:


First, we will need some images to store in Web Resources for icons. I have used 16*16 pixel .png format images. So, I have used three images and stored them in the Web Resources in my Solution.

list view in microsoft dynamics 365

You can see here that the images are in PNG format and you can choose to give any name for the images.


We will also need an Option Set to display the indicators based on options selected for the record, the indicator will get displayed. Here I am using OOB Status Reason field in which I have added options as Current, Dropped, and Prospect. You can use any other option set as well.


Very important JavaScript Web Resource to store the code containing the business logic.

Here is the code. You can use this code to implement the solution.

list view code solution in microsoft dynamics 365


1.       The status code used in the script is the schema name of the column where I want to display the icons.

status code

You can see here that I have used default Status Reason field so I have used statuscode to retrieve the value of the column. You can use the schema name of the options set you are using.

status code 1

2.       In the script below.

status code 3

a.       1 is the value for Active status in the option set.

b.       imageName is schema name of the image.

active status in microsoft dynamics


Link the JavaScript to the columns in the View, by clicking on Change Property option.

microsoft dynamics membership status

column properties in microsoft dynamics 365


Save the view and Publish Customizations.


Go back to view and you will see the icons

list view icons in microsoft dynamics 365

We need to make few considerations here:

There are a few things to consider before diving in:

1.       This only works on a standard grid. It does not work on the newly introduced Editable Grid.

2.       Icons can only be displayed on the Web Interface. The Outlook and Mobile Apps will not display the icon.

3. Tooltips can be defined for multiple languages/locale ID (LCID). In this example, I’ve set Canadian English (LCID 4105) as the default and included Canadian French (LCID 3084) as the alternative. More Locale ID values can be found here.

How to Setup Search Topics in Dynamics 365 Social Engagement Tool

The Social Engagement tool is a fantastic social interaction tool for sales, marketing and customer service professionals who want to proactively engage with their audience and customers on social media. It collects data from various sites such as Twitter, Facebook, Tumblr, YouTube and relevant blogs. The visual reports help you spot emerging trends from people’s comments, whether positive, negative, or neutral. It can even read emoticons and emoji’s =)

Why Social Engagement?

Every business needs to build their brand presence and reputation in the market and to create that social media is a very good platform. There are stand-alone tools out there to help analyze your activity against success measures and objectives. They look at metrics such as clicks, shares, likes, most popular posts and so on. Ideally, you’d use a tool that maximizes existing activities to boost ROI by:

  • analyzing trends in customer sentiment
  • improving existing product lines or creating new products and services
  • creating sales lead in your Dynamics 365 system
  • automatically creating support cases for any complaints posted online

social engagement tool gives all the above features to analyze data and take proper action on it.

To collect that information from various sources user, must set up the search topics inside the search setup section.  At least one active search topic is required to acquire social data. There are different categories present in the search setup like competitor, accounts, contact, lead, campaign, & products. the user can also add their own category. Search topic gives the filtered data related to sources and different rules which user provide to it.

Steps involved to set up Search Topic:

1.    Find out the sources

Social Engagement covers multiple sources where you can track public posts, and publish messages and replies. All sources can be filtered in Analytics for an up-close look at your data. Find out what is covered by using the following available sources.

a.    Blogs

b.    Facebook

c.     Twitter

d.    LinkedIn

e.    News

f.      Reddit

g.    Videos

2.    Create Search topics

You can add search topic names that contain up to 35 characters. The search topic names are only for your reference; they aren’t included in the actual search. Search topic names are like titles for your search topics so you can quickly relate to and use or reuse them.

Microsoft Social Engagement

1.    Add a rule to the search topic

Social Engagement supports the following search rules. You need to be a Social Engagement Administrator or Power Analyst to create or modify search topics.

a.     Keyword rule

b.    Facebook page rule

c.     Twitter rule

d.    Instagram rule

e.     Private message rule

f.      Custom sources rule

g.    YouTube rule

h.    LinkedIn page rule

Microsoft Social Engagement 2

2.    Refine your search rules to find relevant content

Analyze your results and optimize your search queries regularly to make sure you get the most relevant data. Your searches may return posts that are irrelevant in the context you are looking for.

Microsoft Social Engagement 3

3.    Manage your post quota

Keep track of the number of posts that result from your search topics and count toward your solution’s post quota. Your solution is priced based on the number of posts you can acquire per month.

These are the steps which help a user to setup search topic and engage with your customer.

Advantages of Social Engagement Tool

  • A major advantage is this tool is the part of Dynamics 365 and it allows us to create lead or cases directly from social posts
  • Collect all relevant data from various social sources like Facebook, Twitter, LinkedIn etc.
  • We can track competitor’s social activities
  • What is being shared and communicated by whom, and when?
  • We can find who is the big influencer in our industry
  • We can engage with our customers, fans & Critics through social media

And many more……