Latest PnP Modern Search Web Parts topics

At Sympraxis, we love hosting our Ask Sympraxis Anything sessions, where we answer questions directly from our audience. These episodes provide an opportunity to dive deep into the challenges, innovations, and nuances of Microsoft 365. Below are some highlights from our recent session! Can you trigger multiple edit items from PnP Modern Search web parts? Yes, you can! You can achieve this by using a custom list column. Start by creating a custom HTML anchor tag with a URL that directs users to the edit item view. When users click the link, it opens the item in a new tab for editing. Additionally, you can customize the anchor tag as a query.

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.

In this session, we explore the significant updates to Learning Pathways in version 5 and the changes to the Lookbook. Developed by Julie and Stefan Bauer, Learning Pathways has developed into a great tool for most organizations. With Derek’s help maintaining the code updates, this knowledgeable team has collaborated to bring you the latest improvements in the beta version of v5. If you’re looking for more in-depth assistance with Learning Pathways beyond this 30-minute session, we highly recommend our new 1-hour Jumpstart focused on this tool!

This Ask Sympraxis session focuses on what we are most thankful for, and that’s community-driven initiatives! These diverse and valuable resources within the Microsoft 365 community are aimed at improving user experiences and optimizing organizational workflows. Microsoft 365 Community Content The Microsoft 365 Community Content project is an open platform where anyone can contribute. It emphasizes practical content designed to help users comprehend and effectively utilize Microsoft 365 tools. Ranging from fundamental guides to advanced articles combining multiple products, the project is a collaborative effort that continues to evolve.

SharePoint Search has been available for quite some time and can be managed by a variety of flexible tools. On the opposite end of the spectrum, Microsoft Search tends to be more rigid as it’s not as mature. Although Microsoft is constantly adding capabilities to Microsoft Search, we are focusing primarily on SharePoint Search for this article. Building columns In SharePoint, a common use is to build a list or library with columns to organize information. Those columns are called list columns and they are local to that specific list or library. As you start advancing up the Maturity Model of your information architecture, we suggest you start making columns as site columns instead of list/library columns. The benefit of this adjustment is that the columns are not defined by the list or library but instead defined at the site level and therefore reusable across the site. For example, you might have a column titled “Country” with a managed metadata term set. If that column is defined at the site level, it can be used in multiple lists and libraries. Even better, if it’s defined in the content type hub, it can be used in multiple lists and libraries across multiple sites. We also suggest using an ambiguous enough name for these site columns so that they can be used in multiple places but are also specific enough, so users understand what they are. A name like “Country” isn’t particularly specific but still obvious what you are referring to. In short, you want everything to bubble up to the level at which you think it’s going to have value. A lot of individuals don’t use content types and instead just dump documents into lists and/or libraries. Instead, we like to look at site columns as building blocks for content types and highly suggest focusing on reusability.

We’ve come across many clients who express the need for an employee directory. We have learned this may mean something slightly different for each company. We always return to, what problem are they trying to solve? This week we are discussing how you’ll find people, their information, and different surfacing options. User stories

This week on Ask Sympraxis we are focusing on managing links to external resources or tools in your intranet. Join us as we dive into the current state and limitations, the Maturity Model approach, and a few customizable solutions. Current state and limitations

What is a policy center? For the sake of this session, we are discussing building a policy center. However, what’s covered can really be applied to an infinite number of other types of content. The approaches discussed would work for any distributed content management scenario, which is the ultimate goal we are seeking to achieve. Ideally, we want every department or work group to manage the policies that they own rather than having one site or document library that everyone has to submit their content into. Instead, we can create the information architecture so each department can upload their policies to their department site and then the SharePoint site will show a unified view of all those policies regardless of where they sit. This creates a search driven experience that is customized based on the content that we are working with.