This article is contributed. See the original author and article here.
Microsoft Teams is where work happens, and now we’re excited to announce new Copilot in Teams enhancements that will supercharge collaboration and make hybrid meetings even better. Read on for all the details.
The post AI-powered collaboration with Microsoft Teams appeared first on Microsoft 365 Blog.
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
This article is contributed. See the original author and article here.
1. Overview
When gathering SharePoint data through Microsoft Graph Data Connect in a large tenant, you might be pulling many thousands, millions or even billions of objects. If you want to get just a subset of the results, there is a mechanism to filter the results at the source.
A common example is to pull the data just for one site (filtering for the site id) to get started with a large tenant. This way your results will be smaller, cheaper, and easier to handle. You can also use this to get just specific types of sites, like OneDrive or Communication sites.
In this blog, we’ll investigate how you can apply a filter to a dataset in Microsoft Graph Data Connect for SharePoint.
2. What is filtering?
When you request data from the Microsoft Graph Data Connect for SharePoint, you get the full dataset. For instance, if you request the Sites dataset, you get all the sites in the tenant. This is described in the yellow paths below.
If you provide a filter with the request, you can get a partial dataset based on a filter expression. You could, for instance, request all sites with a template id of 21 (that means a OneDrive). This is shown by the green paths above.
In short, filtering delivers a partial dataset based on a filter expression specified in the request. Only objects that meet the criteria are delivered.
The main uses for filtering include:
Filtering is available only in these specific SharePoint datasets:
Note: Microsoft Graph Data Connect also offers an option to exclude specific columns from the results, which is another mechanism to protect sensitive data.
3. Datasets and Columns
This filtering feature applies only to the SharePoint datasets listed below. You can filter by Site Id in all SharePoint datasets. You can also filter by Template Id in the Sites, Files and File Actions datasets:
Dataset | Site Id column | Template Id column |
Sites | Id | RootWeb.WebTemplateId |
Permissions | SiteId | N/A |
Group | SiteId | N/A |
Files | SiteId | WebTemplateId |
File Actions | SiteId | WebTemplateId |
For WebTemplateId, refer to this blog post for details on the codes used:
https://barreto.home.blog/2023/04/17/sharepoint-on-mgdc-faq-is-onedrive-included/
If you’re interested in filtering for additional SharePoint dataset columns, please let us know in the comments.
4. Expressions and Operators
Filters are specified using an expression. The expression usually includes a column (as described in the previous section), an operator and a constant.
The main operators supported include:
Type | Operator | Description |
Equality | eq | Equal |
Equality | ne | Not Equal |
Equality | in | is IN a list |
Relational | lt | Less Than |
Relational | gt | Greater Than |
Relational | le | Less than or Equal |
Relational | ge | Greater than or Equal |
Logical | not | Not |
Logical | and | And |
Logical | or | Or |
Here are a few sample expressions you could use:
Dataset | Description | Filtering Expression |
Sites | Include only a specific site | Id eq ‘a123’ |
Sites | Include all sites except a specific site | Id ne ‘a123’ |
Sites | Include only a specific list of sites | Id in (‘a123’, ‘b456’, ‘c789’) |
Sites | Include everything but OneDrive sites | RootWeb.WebTemplateId ne 21 |
Permissions | Include only a specific site | SiteId eq ‘a123’ |
The expression language is patterned after the Microsoft Graph filter query parameter. You can read more about it at https://learn.microsoft.com/en-us/graph/filter-query-parameter.
5. Including the Filter expression in the request
To add a filter to your request, you must specify a DataFilter property in the JSON representation of the request. Start by selecting the Copy Data task you are using and going to the “Source” tab of the Copy Task properties.
Click on the “{ }” button on the top right (indicated above with a red arrow), which brings up the JSON definition for the request.
In the JSON definition, find the “source” section under “typeProperties”, where you can find the “dateFilterColumn”, the “startTime” and the “endTime” properties. Add a new “DataFilter” property with the expression you want to apply. Save the changes to the JSON and make sure to publish the pipeline to apply the changes.
In the screenshot above, you see the definition indicated by the red arrow:
acitvity >> typeProperties >> source >> DataFilter >> RootWeb.WebTemplateId eq 21
Be very careful. If you specify the filtering expression in the wrong place in the JSON, the request may fail, or it could just run without filtering anything from the dataset. If you’re running this in a large production tenant, it is recommended to try this first in a small test or dev tenant.
6. More Request Metadata
As a result of this extra property in your request, the results will be filtered, and you will see fewer rows/objects in your output. Another way to see this is looking at the metadata file that is produced with any Microsoft Graph Data Connect run. Look for a folder called “metadata” in the same place you assigned to receive the data (your Azure account container and folder).
In the job metadata file associated with this request, you will see a few additional properties:
Here’s a sample of a job metadata file:
{
"CopyActivityId": "00000000-0000-0000-0000-000000000000",
"JobSubmissionTime": "2024-01-10T21:27:18Z",
"JobCompletionTime": "2024-01-10T21:32:44Z",
"RequestStartDate": "2024-01-06T00:00:00Z",
"RequestEndDate": "2024-01-06T00:00:00Z",
"ColumnsRequested":"ptenant, Id, Url, RootWeb, WebCount, StorageQuota, StorageUsed, StorageMetrics, GroupId, GeoLocation, IsInRecycleBin, IsTeamsConnectedSite, IsTeamsChannelSite, TeamsChannelType, IsHubSite, HubSiteId, BlockAccessFromUnmanagedDevices, BlockDownloadOfAllFilesOnUnmanagedDevices, BlockDownloadOfViewableFilesOnUnmanagedDevices, ShareByEmailEnabled, ShareByLinkEnabled, SensitivityLabelInfo, Classification, IBMode, IBSegments, Owner, SecondaryContact, ReadLocked, ReadOnly, CreatedTime, LastSecurityModifiedDate, Operation, SnapshotDate",
"ExtractionMode": "Full",
"IsFilterApplied": true,
"Filter": "RootWeb.WebTemplateId eq 21",
"NumberOfRowsExtracted": 4,
"TableName": "BasicDataSet_v0.SharePointSites_v1",
"ApplicationId": "00000000-0000-0000-0000-000000000000",
"OfficeGeo": "NAM",
"DataFactoryName": "mgdc-synapse"
}
7. Combining Filters with Deltas
It is possible to combine the filtering and the delta features of the SharePoint datasets in Microsoft Graph Data Connect.
When you specify a filtering expression and two different dates, the dataset will be first filtered and then the differences between the two dates will be calculated.
For more details about Delta datasets, see this blog post:
MGDC for SharePoint FAQ: How can I use Delta State Datasets?
8. Filtering Errors
If you pass an expression for filtering and there is a problem with it, Microsoft Graph Data Connect for SharePoint will fail the request and no data will be returned. An error message will be returned so you can understand what happened.
Here are some of the common error conditions:
Operation on target Copy_Sites failed:
ErrorCode=UserErrorOffice365DataLoaderError,
'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,
Message=Office365 data loading failed to execute.
office365LoadErrorType: PermanentError.
Not Supported: Both DataFilter and AdditionalDataSetProperties with 'top' can not be specified at the same time,
Source=Microsoft.DataTransfer.ClientLibrary,'
Operation on target Copy_Sites failed:
ErrorCode=UserErrorOffice365DataLoaderError,
'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,
Message=Office365 data loading failed to execute.
office365LoadErrorType: PermanentError.
[1]: Invalid schema specified in filters.
Only few columns are supported for filters.
Supported Columns: ['Id', 'RootWeb.WebTemplateId'].
Usage Example: Id eq '00000000-0000-0000-0000-000000000000'
or RootWeb.WebTemplateId eq 21'
,Source=Microsoft.DataTransfer.ClientLibrary,'
9. Conclusion
I hope this blog post will help you get started with Filtering. For more information about Microsoft Graph Data Connect for SharePoint, please visit the collection of links I keep at Links about SharePoint on Microsoft Graph Data Connect.
This article is contributed. See the original author and article here.
In the dynamic field of service management, efficiency, accuracy, and streamlined processes are key. The new work order experience in Dynamics 365 Field Service, introduced in the 2023 release wave 2 (release plan), offers a refreshed user interface that revolutionizes work order creation, management, and scheduling. We’ve continued to refine and add new features based on your feedback, and starting wave 1 2024, the new experience will be the default for all organizations (release plan).
The new work order experience is a complete revamp of the existing work order management system within Dynamics 365 Field Service. It simplifies the entire lifecycle of work orders, easing seamless collaboration among service managers, technicians, and dispatchers. Here are the key features:
Let’s explore each of these capabilities in more detail.
We’ve rebuilt the work order grid from the ground up to increase performance and enable new capabilities such as inline editing of commonly changed fields like priority. We’ve enhanced the visual appeal of the status field and recently added the ability to see booked resources too. You can now configure whether you want just the work order ID or all linked entities to be clickable in the grid. Lastly, we’ve built inline actions and introduced a side pane for quick edits within the flow of work.
We’ve updated the work order form to reflect how most organizations manage their work from start to finish. The most vital information is now in the General tab, we’ve merged billable work into a unified Products and Services section, we’ve grouped tasks and inspections under Tasks, and we’ve pulled all reference materials – such as knowledge articles, Dynamics 365 Guides, and timeline media – into the References tab.
We reorganized the general tab into a two-column setup for improved readability and better usability, focusing on the most essential information for service organizations. These enhancements are designed to make your daily tasks smoother and more efficient, based on user feedback and telemetry. Key improvements include:
We’ve unified the Product and Services into a single tab, with a unified summary of financials atop it. Service managers can easily switch between the products and services view, make changes to used inventory and services inline, and open the side pane for more detailed changes.
The tasks section captures the steps that need to be done to complete the work. A summary card keeps count of scheduled vs. completed tasks and duration. You can also visualize if a tasks includes linked items to help technicians complete their work with Dynamics 365 Guides or capture their work result with inspections.
You can now find all your references in a unified experience that includes knowledge articles that capture fixes or known issues for commonly encountered issues, Dynamics 365 Guides that are linked to tasks, and media that has been attached to the timeline.
The introduction of the side panes is one of the biggest changes in the redesigned work order experience. Side panes allow you to see more details or make minor tweaks to related content in the context of your work. From being able to make tweaks to work order instructions from the work order grid, to updating product inventory financial data in a form, side panes keep you productive. Side panes are available in the work order grid, products and services grids, tasks grids, and when opening related items such as assets.
Embracing change can be daunting, but the benefits are worth it. Starting wave 1 2024, the new experience will be the default for all organizations. There are several reasons why organizations should consider transitioning to the new experience starting now:
The new work order experience in Dynamics 365 Field Service isn’t just an upgrade—it’s a leap forward. Embrace it, empower your team, and elevate your field service operations. Efficiency, collaboration, and customer satisfaction await!
Ready to take the plunge? Start your journey today to ensure your organization stays competitive and prepared for the future of field service management. Explore the official documentation to get started, download our adoption playbook to aid you in the deployment process, and don’t forget to share your feedback using the Feedback button in the app header. Together, we’re shaping the future of field service management.
The post Introducing the new Work Order Experience in Dynamics 365 Field Service appeared first on Microsoft Dynamics 365 Blog.
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
This article is contributed. See the original author and article here.
The potential for AI at work is practically endless—and understanding how your teams can accomplish more with generative AI is more important than ever. Every day, more companies are turning to AI features to help their employees work more efficiently, provide positive customer experiences faster, and stand out among competitors.
See what’s new at the Microsoft Business Applications Launch Event
Join Microsoft product leaders and engineers on April 10, 2024, for an in-depth look at the latest AI features and capabilities in Dynamics 365 and Microsoft Power Platform. You’ll learn how advances in AI and Microsoft Copilot can help you connect teams, processes, and data, and respond to changing business needs with greater agility—and see how organizations across several industries already take advantage of the newest AI features to streamline business processes and accelerate low-code development.
Register now to see key presentations from Microsoft leaders, including:
That’s just a small sample of what we’ve got planned. You’ll also hear directly from other Microsoft leaders about their vision for AI, customer service, and operations, and get timely tips on how to use these new technologies to take on your business’ toughest challenges. If you have questions about new AI features, how Copilot experiences work, or what’s new in low-code tools, take advantage of the live Q&A chat with Microsoft experts throughout the event.
We’re excited to share the latest AI features for Dynamics 365 spanning across end-to-end customer experiences, sales, finance, supply chain, commerce, and other areas. Here are just a few of the new features in 2024 release wave 1:
Microsoft customers are already doing amazing things with the new AI features in Dynamics 365, and we can’t wait to inspire you with their stories. Register now and join us to see what’s new in the 2024 release wave 1.
Microsoft Business Applications launch event
Wednesday, April 10, 2024
9:00–10:30 AM Pacific Time (UTC-7)
The post Explore the next wave of AI innovation at the Microsoft Business Applications Launch Event appeared first on Microsoft Dynamics 365 Blog.
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
This article is contributed. See the original author and article here.
In this snackable you will learn how to quickly take a professional journal publication in PDF format and convert it to Microsoft Word where you can use Copilot to query and summarize the contents. Then you will learn how to turn that professional journal publication and leverage Copilot to create a PowerPoint presentation in order to present its contents to colleagues and staff.
To see all HLS Copilot Snacks video click here.
Resources:
Have questions you would like to have us address in a snackable? Let us know!
Thanks for visiting – Michael Gannotti LinkedIn
Recent Comments