User Profile
ChrisFicek
Iron Contributor
Joined 9 years ago
User Widgets
Recent Discussions
Re: Filter reset when viewing document
Try accessing the view directly via URL instead of changing the view. It is believed a recent change has caused these headaches with the views, filters and the file viewer. It has progressively gotten worse over the last couple of days where the custom views doesn't load any documents on the fly (having to click on 'click to see more' 3 times before anything shows up).Inventory Report on Office 365 Connector Web Part in SharePoint Online
With the recent announcement made by Microsoft to retire Office 365 connector web part from SharePoint Online (MC793656) and in Use the Connector web part - Microsoft Support, is there a way we can generate an inventory of all site collections using Office 365 connector web part?Re: Result Types for Modern Search
Basically, parathesis in the filename is causing the title and the URL (link to the file) to not render or work correctly. If there is a solution that would solve this issue, I am interested in learning more about the workaround if there is one (without having to rename the files without parathesis - if possible).Result Types for Modern Search
Due to the recent Microsoft changes to modern search results (displays filenames instead of the title that is populated in SharePoint), we explored the use of 'Result Types' for modern search. We were able to closely replicate the search results with the properties we want to display, including the title. It works like a charm but then we stumbled across ones that uses special characters in the filename. The search adaptive card does not render the title, nor it is clickable due to parathesis used in the filename. Below is a JSON snippet used. It still works fine for filenames like 'Heat Stake Thermal Press Process Standards.pdf' but not 'Heat Stake (Thermal Press) Process Standards.pdf'. Any suggestions in allowing the results to render correctly and for it to be clickable to the actual file without having to go back and rename all the files? { "type": "TextBlock", "text": "[${title}](${Url})", "size": "medium", "weight": "bolder", "maxLines": 2 } Correct: Incorrect:SharePoint Cloud Search Service Application Retirement
Has there been any indication of SharePoint Cloud Search Service Application being retired in the near future? Especially for those who are still on SharePoint 2013, 2016 and 2019? I am not finding anything online indicating so but was wondering if it will retire when SharePoint 2016 and 2019 retires on July 14, 2026.Title vs Filename in Microsoft Search Results
Microsoft recently made some changes to the Microsoft Search that impacted the ability to display title metadata from SharePoint in modern search results (tenant search scope). It is now displaying the filename instead of the title in modern search results. The classic search results continues to work as expected (displays titles). We are unable to find any documentation on the recent change but was curious if anyone else had experienced the impact from this change? We've implemented some search adaptive cards to help minimize the impact but it only works for PDFs, not Office documents. Are there some options we could potentially explore that we haven't heard / seen yet that could help minimize the impact? A few additional questions came to mind regarding this situation --- 1. Was it intended for filenames to only be displayed in modern search results? A few years ago, we were able to configure the title managed property on SharePoint online to display the title instead of the filename to meet our needs and it worked until the changes Microsoft made recently. This setup is similar what can be configured for SharePoint 2013 (Show more relevant Titles in search results in SharePoint 2013 plus some other improvements | Microsoft Learn). 2. Why does the title (metadata) still show in the site level search? 3. Why does the title (metadata) of the site page show in modern search results at the root (tenant search scope)? Isn't the library set up to store site pages and documents the same? 4. Are we moving away from using search schema in modern search results?Re: Migration from Classic - redirects not works and videos are not deleted from Classic
JWiersem1925, I am not one of the Microsoft staff members looking into this. It looks like it is still being investigated and a few resolutions. Refer to the table at https://learn.microsoft.com/en-us/stream/streamnew/migration-tool-release-logs#under-investigation-to-be-fixed as it provides some updates and guidance as to what to expect. If the fix is fully out there and you still don't have the updates, I would recommend submitting a ticket with Microsoft.Stream Migration Tool: User's Personal Stream Container Does Not Contain The User Owned Video
With the Stream migration tool Microsoft provided, we noticed after the Stream video was migrated that the video in the user's (Jane Doe) Stream containing does not contain video owned by 'Jane Doe' but rather 'John Deere'. Jane does does not have ownership or co-ownership of on John's video that was just migrated. I have verified by searching Jane Doe on Stream, the video I wanted to migrate does not match what was actually migrated. Has anyone experienced this? Are we encountering a bug? This poses some concerns in accidently sharing videos with those that should not have access.Re: Redirection of Stream Classic links
From Microsoft - July 4, 2023 Some videos aren't being hidden in Stream (Classic) after they are migrated & redirection from old link to new link isn't working | Fix estimate: September 30, 2023 - After videos are migrated they're suppose to hide from Stream (Classic). Anytime you navigate to the old link or embed code for a migrated video it should redirect to it's new location in OneDrive or SharePoint However, in certain cases this isn't happening. Also, sometime the migrated destination URL isn't populated in the inventory report due to the same root cause. During our investigations, we've discovered multiple bugs that result in these same symptoms. We have already fixed several of these issues but we're working to fix the remaining known issues. Source: https://learn.microsoft.com/en-us/stream/streamnew/migration-tool-release-logs#migration-tool-known-issues--bugsRe: Migration from Classic - redirects not works and videos are not deleted from Classic
From Microsoft: July 4, 2023 Some videos aren't being hidden in Stream (Classic) after they are migrated & redirection from old link to new link isn't working | Fix estimate: September 30, 2023 - After videos are migrated they're suppose to hide from Stream (Classic). Anytime you navigate to the old link or embed code for a migrated video it should redirect to it's new location in OneDrive or SharePoint However, in certain cases this isn't happening. Also, sometime the migrated destination URL isn't populated in the inventory report due to the same root cause. During our investigations, we've discovered multiple bugs that result in these same symptoms. We have already fixed several of these issues but we're working to fix the remaining known issues. Source: https://learn.microsoft.com/en-us/stream/streamnew/migration-tool-release-logs#migration-tool-known-issues--bugsRe: Add O365 Group Owner to Site Collection Administration List
OrangeJuiceJones, its been a few years since I've encountered this issue. Have you tried going to SharePoint Admin Center > Locate the active site and select it to get to the site settings. I am curious if there is a message that is prompt to add the group owners as admins is still.Encountering 'Failed to Validate the Signature of the Actionable Message Card' Error
Hi, I am not sure if I am posting to the right group but would like to ask about 'Failed to Validate the signature of the actionable message card' error that we are encountering with the shared account when trying to approve / reject SharePoint access requests within Outlook (app/web). For a while, it worked fine until recently. We do not encounter this issue with standalone user account. Is this a known issue for the out of the box feature or is something not configured correctly on our end in Exchange? Any pointers would greatly be appreciated.
