In my organization, we have Power Automate flows that work from a List trigger. When “Publish to Calendar” is selected on the List, then a flow creates a calendar event on a SharePoint communication site. This impacts two different sites within our intranet.
Starting on 1/25/24, the flow errored out. Through investigating, it seems the WorkspaceURL, which was previously working fine, is no longer part of the schema.
Questions
- This issue just started happening, and I can’t find any resources about this issue. Any ideas as to what’s happening with WorkspaceURL in the object schema of events?
- How can I continue to automate SharePoint calendar events through Power Automate?
- Where in SharePoint are Event lists items storing the Link (available when creating an event manually in SharePoint)
Additional Details
The issue we have is why is this no longer part of the schema? This abruptly changed, and in looking at the JSON outputs of the Events lists on these sites, there is no WorkspaceURL or any hyperlink (even though these exist somewhere in SharePoint). I can still create an event manually on a SharePoint communication site and add a registration hyperlink, but where that “lives” now I have no idea. Previously, we could access that WorkSpaceURL in Power Automate; now, it doesn’t exist in the schema, in the JSON outputs, in Event list views, and nowhere that I can find. But it has to exist somewhere in SharePoint because we have live events with registration hyperlinks.
In Power Automate, I get this error: 'item/Workspace' is no longer present in the operation schema. It should be removed before the workflow is re-saved.
This was always a challenging flow—the Events list doesn’t show up under lists, and to make this Create Item action work, I had to manually paste in the Event List ID (vs finding it in the dropdown of Create Items). Why Microsoft doesn’t allow easy automated creation of SharePoint events is beyond me, but this has worked successfully for about 9 months.
Even more odd, there is a switch in this flow, and depending on the event type, there are possibly 6 naming conventions tacked on to the webinar title, and then it’s published to 1 of 2 sites. You can see the flow on the right in the screenshot shows a different layout, still identifies WorkspaceURL as an option (where the flows attached to the other site on the left flow in the screenshot now display item/workspace, indicating this is no longer available). Both sites yield the same back end results—I cannot trackdown the WorkspaceURL in the JSON outputs, views, etc.