Latest Customization, Integration & Extension topics

Backup and archive: understanding the differences Backup and archive serve distinct purposes, although many confuse them for the same thing. Backup refers to warm storage, focusing on active content and ensuring easy access to recover data if a problem arises. On the other hand, archiving is akin to cold storage, dealing with inactive content that isn’t regularly used. Syncing data does not serve as a backup or archive; it merely keeps two copies of the same data synchronized, without providing the backup or archived version.

In this Ask Sympraxis session, we expand on the foundational concepts discussed in the previous episode, focusing on the role of SharePoint Managed Metadata for Search. If you haven’t caught up on that episode yet, we recommend starting there to better understand the central role of the term store and managed metadata in building a robust information architecture. Term store vs. managed metadata The term store and managed metadata are often mentioned together, but it’s important to differentiate between the two. The term store is essentially the repository where terms are created, managed, and stored, while managed metadata refers to the method by which these terms are integrated into SharePoint. Though they work hand in hand, they serve different purposes within SharePoint’s ecosystem.

As we mark the milestone of our 100th episode of Ask Sympraxis, it’s incredible to reflect on the journey we’ve embarked on since our first episode on April 20, 2020. Back then, the world was quite different, and in many ways, so was the landscape of technology. Over the years, Ask Sympraxis has grown, evolved, and adapted, much like the tech ecosystem we seek to demystify.

When managing data in SharePoint and Microsoft Lists, understanding the various form customization options available and how they interact with these platforms is essential. Forms serve as the primary interface for collecting data, and while they might appear simple, the underlying complexity varies depending on the type of form and its intended use. This session explores the different form customization options available for SharePoint lists, libraries, and Microsoft Lists, including their capabilities and how they can be leveraged effectively.

Back in the day, SharePoint developers reveled in the ability to craft pixel-perfect intranets and websites, wielding full control over branding assets. However, this era of limitless customization came at a cost - considerable technical debt. If you built an intranet with custom branding, you had to account for every web part, how it was used, and how it was branded, often at the expense of performance. The good news is all that changes in the new modern brand center as it is slowly giving us back customization options.

In this Ask Sympraxis session we explore the vast landscape of templates within the Microsoft 365 ecosystem. Discover how templates serve as essential building blocks for evolving sites over time. A template in the conventional sense may be thought of as a guide. In Microsoft 365, we consider a template something aimed to deliver repeatability, consistency, and encapsulating institutional knowledge. Content types as templates Content types serve as templates for business objects like invoices, contracts, orders, etc. Although Microsoft provides base content types, you can create your own to suit your organizational needs. Building those in the Content Type Hub or SharePoint admin center allows you to reuse them across your tenant.

We had another highly productive “Ask Sympraxis Anything” session! Our heartfelt thanks to everyone who submitted questions and actively participated. Here are the key insights and takeaways from the session! What are the ramifications of breaking permission inheritance in SharePoint online? We highly emphasize the importance of avoiding haphazardly breaking permissions. In the past this resulted in performance issues. This isn’t as much of an issue now as the landscape of SharePoint has evolved, especially in SharePoint Online. Despite this, we still believe that breaking inheritance should be done sparingly and thoughtfully. It’s crucial to weigh the benefits against the potential management complexity it may introduce. The key takeaway is that permissions should be organized methodically, and breaking inheritance should be the exception rather than the rule. If you find yourself breaking inheritance regularly, you might want to redesign your information architecture.

Intranet owners have a wealth of resources at their disposal, catering to their needs across various aspects of intranet management. Whether you’re looking to configure your intranet, enhance your knowledge through self-guided learning, explore powerful user configurations, or seek inspiration from configuration examples, there are numerous community-driven assets available to you. Basic Configuration Intelligent Intranet by Microsoft Intelligent Intranet is a Microsoft site that offers insights into their vision for intranets, providing a comprehensive understanding of what an intranet entails. It’s particularly helpful for those new to the concept and serves as a persuasive resource when advocating for intranet solutions.

In the dynamic landscape of PnP Modern Search, fine-tuning your search experience is not just a possibility, but a powerful tool in your hands. Dive into these insightful tips and techniques to elevate your search experience. Crafting an effective information architecture To pull precise data subsets based on metadata, you first need to build a strong foundation. This is done by an efficient information architecture. The root of success lies in robust and well-defined content types. This makes searching easier. We always suggest including an interstitial content type which allows you to curate all the common site columns without editing the out of the box content types. The image below demonstrates a hierarchy that will help pave the way for the many of the functionalities of PnP Modern Search.

Is having employees complete their Microsoft 365 profiles the most effective method to enable a searchable “area of expertise” property in our employee directory? There are multiple approaches to achieve this, and your decision should depend on your long-term goals and platform extension capabilities. The simplest solution is to utilize the existing “skills” and/or “you can ask me” sections in SharePoint User Profiles. To enhance this solution, you can map the values from the skills section to a refinable string managed property, enabling the use of PnP Modern Search for a user interface with filtering capabilities. Another option is to leverage Azure Active Directory (AD) to store skills and expertise values, which can be displayed by any application consuming Azure AD. Alternatively, you can consider using a third-party solution like LiveTiles Directory or developing a custom solution tailored to your specific needs.