User Profile
paulschaeflein
MVP
Joined Jun 27, 2016
User Widgets
Recent Discussions
Microsoft 365 Developer Podcast - Dev tools that make IT Pros smarter with Matthew McDermott
In this weeks episode Jeremy Thake talks to Matthew McDermott about the IT Pro journey and how they can learn a lot from developers on working smarter with tools developers have used for years. This episode had some great tidbits for developers and allows them to understand the difference between the roles. http://www.m365devpodcast.com/e/devs-tools-that-make-it-pros-smarter-with-matthew-mcdermott/Microsoft 365 Developer Podcast - Dev tools that make IT Pros smarter with Matthew McDermott
In this weeks episode Jeremy Thake talks to Matthew McDermott about the IT Pro journey and how they can learn a lot from developers on working smarter with tools developers have used for years. This episode had some great tid bits for developers and allows them to understand the difference between the roles. http://www.m365devpodcast.com/e/devs-tools-that-make-it-pros-smarter-with-matthew-mcdermott/Conversations link in SharePoint - What about Teams chat?
In the Message Center, item MC126033 was published last week with the following information: "... we have recently updated the site navigation of your team site with a conversations link to either a group mailbox or Yammer group (depending on where the site was provisioned)." What if the site was created in Microsoft Teams? Will the link still show? If so, will it be the chat experience in Teams on the web?Visual Studio Extension for SharePoint Framework (v1.3.2-beta) - now supporting SPFx Extensions
Just published pre-release version of SPFx extension for Visual Studio. Now supports extensions! #PnP #SPFx https://github.com/SharePoint/sp-dev-fx-vs-extension/releases/tag/1.3.2 Please provide feedback via GitHub issues.PnP: Provisioning.Framework.Console error with User field
While running the Provisioning.Framework.Console sample, I encountered an error with a SiteField of type User. The sample created the template with the List attribute pointing to "UserInfo": <Field Type="User" DisplayName="Sales Person" List="UserInfo" Required="TRUE" EnforceUniqueValues="FALSE" ShowField="ImnName" UserSelectionMode="PeopleOnly" UserSelectionScope="0" Group="Custom" ID="{bbd75b76-a9e1-4417-93cb-039554853e9c}" SourceID="{a4ae28f2-eaa4-4350-8f29-c67ba3013677}" StaticName="SalesPerson" Name="SalesPerson" /> When applying the template, the engine fails since the List attribute does not represent a list id (GUID) nor the relative URL of the list's root folder. (The User Info list is at "_catalogs/users"). My questions: 1.) Does the issue get logged in the repo for the sample, or the engine? 2.) Since the lookup list for a field of type User is a known value, the engine could correctly process them. Would the fix go in the ExtractObject method or the ProvisionObjects method? I am prepared to submit a PR along with the issue, I just want to get it in the correct place.Re: Setting up a simple Flow in SharePoint
When using the "When a file is created" trigger, you are prompted for a Folder Id. While I understand that most people will assume sub-folders are included, and the trigger should probably be updated to do that, for now you will need to select the sub-folder from the picker (or enter the relative URL to the sub-folder).Re: Microsoft Flow - Get executing user
The user who starts a flow is not known to the flow service unless the trigger provides it. You mention manually starting a trigger. Assuming that means a flow button, you can get the User email and User name properties from the "Manually Trigger a Flow" trigger. When displaying the dynamic content, scroll to the bottom of the list for the trigger.Re: State Machine Workflow in SharePoint
FYI - the Flows that you create in Microsoft Flow are all, at their core, state machine workflows. Since you asked about Visual Studio workflows, I assume you are familiar with web services. I have an article that discusses using WebAPI services to interact with Flow that may be helpful. Also, Flow is built upon Azure Logic Apps, which certainly could support a state-machine workflow.
