sharepoint server
2030 TopicsAuto-Increment Number Field in a SharePoint List
I need to create an auto-increment field with a standard amount of digits. The format needs to be like this T000001, T000002, T000003, ......T000010, etc (7 Digits). When it gets to the 10th record it should not do this T0000010 (8 digits). I tried using the popular, often referenced solution (link below). This method does not work as I hoped. If you put it in a format like this T1000, when it gets to the 10th item it does this T100010 rather than T10010. Here is the popular solution I already tried: https://www.epmpartners.com.au/blog/how-to-create-an-auto-incrementing-number-field-in-a-sharepoint-list/Solved338KViews1like26CommentsCustom/Vanity domain name/URL for Sharepoint Online
Hi, I would like to change the default Sharepoint.com URLs to company's URLs, so: 1) contoso.sharepoint.com => sharepoint.contoso.com 2) contoso-my.sharepoint.com => mysharepoint.contoso.com 3) contoso.sharepoint.com/sites/abc => sites.contoso.com/abc How can this be configured? Thanks,206KViews6likes39CommentsKnowledge Base - setting up within O365/Sharepoint
Hi Everyone, yes I agree the O365 suite is a great tool for organisational knowledge management and collaboration. However, I have not found any official guidelines on a way to set up a knowledge base/Wiki type structure, that achieves what is offered by other software. I'm thinking that Sharepoint would be the ideal place, but am interested to hear from this community on what has been done, tried and any tips for new players. Thanking you in advanced!144KViews6likes34CommentsEmails from no-reply@sharepointonline.com are getting sent to spam by gmail/yahoo
Has anyone else had issues with emails from no-reply being sent to junk / spam. When a file is externally shared with gmail or yahoo the email is showing up in spam. If i email gmail directly from my mailbox from my domain I have no issues. The header information from gmail is as follows. Authentication-Results: spf=fail (sender IP is X.X.X.X) smtp.mailfrom=sharepointonline.com; gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=fail action=oreject header.from=sharepointonline.com; Received-SPF: Fail (protection.outlook.com: domain of sharepointonline.com does not designate X.X.X.X as permitted sender) receiver=protection.outlook.com; client-ip=X.X.X.X; helo=RD00155D7132AE;116KViews2likes9CommentsAutomatically assigning a value based on another column value
Hello All, I was wondering if there is a process in Sharepoint maybe using power automate that will help me fill a column automatically depending on another column value. As an example I have 26 Departments listed as possible choices in column A I want Column B to auto generate a DepartmentID based on the department selected in column A So every time HR (one of the 26 departments) is selected in column A it will generate a "1" in column B. Every TIme Operations is selected in column A it will auto populate a "2" in column B. And so on and so fourth, my apologies if there is a simple solution, I'm quite new to using SharePoint and power apps.108KViews0likes9CommentsFile:// Links not working on Chrome or Edge (Chromium)
We've recently encountered an issue with IE11, and are trying to move to a different browser solution on company Workstations. Our intranet is Sharepoing 2013 (On-Prem), and we have a large number of documents linked in "file://" format. I would like to avoid replacing every single document on our intranet with a different link format; does anyone know of a way for Chromium based browsers to open "file://" based links in file explorer. I am aware of the "file://" chrome extension that opens them in an index search, but we want the links to open in file explorer. Thanks for your time! ~JP106KViews1like8CommentsSharePoint Online Backup Strategies for a Cloudy Day
With an ever-growing Office 365 ecosystem, the question of data backup and recovery often arises. The data used in the apps is stored across multiple SharePoint Online sites, Exchange Online mailboxes, and other specific apps. There are two types of backup scenarios that may you need to cope with Service backup, which ensures that all the content is backed up on a regular basis in the case there is corruption or the service fails Deletion backup, where users will accidentally or purposely delete content In SharePoint Online, by default, content is stored indefinitely in your sites. Without someone explicitly deleting the content or having information management policies or other external actors that would delete content, you don't have to worry about your data disappearing. But, in reality, there will be scenarios, where content is purposely or inadvertently deleted. Whether it's a single file or entire site collection, you need ways to get your data back. Before we look at the types of solutions available, ask yourself what it is you really need to back up and why. Wiping out your intranet will likely cause disruption to your organization, but will you be able to recover from it? You can break down your SharePoint environment into several layers Documents - Word, Excel, PDF, or whatever format you work in. This is the key work product your teams depend on and one of the core reasons SharePoint, an Enterprise Management System) is being used. Documents are created and updated frequently across the sites List Items - Calendars, action items, risks registers, etc. Like the Documents, these are core to your SharePoint environment and change frequently. Metadata - Over the years, there has been a lot said about the importance of metadata. There are many great reasons for having it. Yet, without discounting any of the reasons, as long as the core metadata can be recreated from the content itself, you're probably safe. Some metadata will be manually set by users once a document is created or is modified (for example, changing a status). Other metadata, such as Modified by or Modified date will change automatically. Site structure - The site structure entails everything else that makes up your SharePoint site - information architecture, navigation, branding, custom web parts, and other elements that make the SharePoint the IT centerpiece of many organizations. Lots of effort is spent in setting it up, and once you've reached that point, the rate of change to the environment itself is lower than content itself. Now, imagine that your SharePoint environment got destroyed (picture a virtual meteor). What would it take to get your organization back up and running in the shortest time possible? Remember how you used to work before SharePoint. Like a good science fiction movie, where all metropolitan cities are destroyed and people are living out of run-down campers, you may find yourself going back to the days where documents were stored on network drives and lists were Excel worksheets (but only for a short while). Today, third party software providers offer some great options for backing up your cloud content. However, these solutions are often costly and may be too advanced for your specific use case. Let's have a look at some alternative options you have. Document Version Control This is the simplest solution available to you. As a document gets updated, new versions are created. At any time you can get back to an older version and even restore it as the current version. When using versions, you can control how many versions will be saved at any time. For instance, suppose you set the limit to 50 versions. Once you have reached 50 versions for a document and save it again, version 1 will be deleted and you will be left with versions 2 to 51. Keep in mind that for each version stored, you are storing a copy of the document, hence taking up additional space on your tenant. Using the SharePoint Recycle Bins When documents or list items are deleted, they go to the User recycle bin (first-stage recycle bin). Content remains there for 93 days, during which the user can restore the content to its original location or delete it from the User recycle bin. Content deleted from the User recycle bin moves to the Site Collection recycle bin (second-stage Recycle bin) for the remainder of the 93 days. The second-stage recycle bin can contain anything from a single item to entire site collections. To restore content from the Site Collection recycle bin, you will need to contact your site collection administrator to restore the data via the SharePoint Online Administration Center Recycle Bin (https://<tenant>-admin.sharepoint.com/_layouts/15/online/RecycleBin.aspx) Requesting Backups from Microsoft If content was deleted permanently from your SharePoint Online environment, you may still be able to get it back for a limited amount of time directly from Microsoft. In this case, a user with Office 365 global admin rights will need to contact Microsoft through the help channels to request a restore. The restore process will bring back an entire site collection with all its content to the original location. This is important to remember as you may have only lost a single file and will need to manually reconcile all the other content. Microsoft backs up content every 12 hours, and take a few days to restore, so depending on the urgency for getting the data, this may not be a viable solution. Retention Policies The purpose of Retention Policies is not to act as a backup for your data, but rather restrict what data can be deleted (or should be deleted) and when. The decisions to keep to delete content are usually bound by regulatory or legal policies. With Retention Policies you can apply such rules to all content or just content meeting certain conditions, such as content containing specific keywords or specific types of sensitive information. When content is subject to a retention policy, you can continue to modify your content in its original location. But if someone edits or deletes content that’s subject to the policy, a copy is saved to a secure location where it’s retained while the policy is in effect. To further restrict how your content is handled, Retention Policies can be configured so that once they have been turned on for a specific piece of content, they cannot be turned off or made less restrictive. To meet this requirement, you can use Preservation Lock. After a policy’s been locked, no one—including the administrator—can turn off the policy or make it less restrictive. Again, the Retention Policies are a safeguard against accidental (or malicious) deletion of content, not backup. If you introduce a Retention Policy that permanently deletes content, you will not be able to get it back once the policy takes effect. Manual Content Backup Alerts Alerts themselves are not a backup method. However, you can use them to stay informed if there is any sensitive information being deleted and allows you time to determine how to react. For instance, if there are specific document libraries you mostly care about, you can enable alerts on them for document deletion, which will then give you time to decide what to do once the documents are in either the first-stage or second-stage recycle bins Use a Flow to act on modified or deleted content Microsoft Flow offers a number of triggers and actions that can help you automatically react to events where documents or items are deleted or modified. The Flow would use an item/file deleted or item/file modified as a trigger to start the workflow. Based on your specific scenario, you could then decide what you want to do with it. For example, copy the file to another location, such as SharePoint site, Azure storage, OneDrive for Business, file system, or other service or simply send an email with the file's information (similar to an alert). To maintain the existing metadata, you can export it together with the file in the form of an XML structure or similar. This way, you could recreate it in the case you need to restore the file. Depending on the size of your organization and amount of content being created or modified, you need to consider the number of such workflows that would be triggered so that you are within the limits of your service plan. By default, a user can run up to 2,000 workflow executions in a month. PowerShell to copy data PowerShell will give you lots more flexibility, but comes at a cost of developing and maintaining the scripts. Using PowerShell, you can write scripts to automate much of these backup activities to copy files, extract metadata, and manage the content and report on it from another location. OneDrive for Business Syncing With OneDrive for Business, you're able to sync specific document libraries to your local machine. The same scenario could be set up using a service account that will sync content from SharePoint Online to a folder on a network file share. This continuous mechanism is easy to set up, but you need to ensure two things - 1) you are still responsible to back up your file share and 2) you need to also set up a mechanism that will copy the content from the sync folder to another location on your file share or other location outside of your SharePoint or OneDrive for Business setup as files deleted from the document library will also be removed from the sync folder, which is what you're trying to avoid with this backup setup. Leveraging Migration tools If you have already made an investment into a migration tool, you may be able to leverage it for your backup needs. Most migration tools allow you to do delta migrations, where only content that have changed is migrated. Furthermore, such migrations can often be scheduled to run at specific times. This lets you run the migrations when system usage is low to minimize the impact on your organization. If you are using a migration tool that offers these features, then you should set up a one-way migration/sync that will pull data from your active SharePoint environment and copy it to a backup location. Depending on your needs, you can migrate specific document libraries or entire site collections to a number of locations - another site collection in your existing tenant, a separate tenant, Azure, an on-premises SharePoint farm or file share, or more. Obviously, there are cost and infrastructure implications to each. For example, storing the content in an on-premises SharePoint farm will require you to maintain a separate farm and infrastructure to support it. If you are copying the content to another location within your tenant, your backup may be compromised if your tenant or the data center it's managed from becomes unavailable. Having an alternate tenant in a different datacenter provides a level of redundancy, but at an additional cost. You can, however, reduce the cost by adding your users to the alternate site collection but not license them. This way, the ownership of content can remain the same, but license costs are not incurred. Just remember that in order to achieve this, you will also need to sync your user accounts (minus the licensing part). Regardless of which way you go with a migration tool, one of the largest advantages you have over the Microsoft Backup request is that you can restore granular content as needed or even an entire site collection to another URL so you can pick what to keep. As you can see, there are a number of viable options available for backing up your data in SharePoint Online that don't require you to invest in an expensive solution. As with anything else in Office 365, proper governance is important to reduce the risk of inadvertently deleting content you may need and having a way to get it back if accidentally deleted.94KViews3likes5CommentsSharePoint - How to Reset Inheritance Permission set into an SP DocLib folder or file
When we are importing File Server content into SharePoint using dedicated tools for, we can import permission set configured at the sub levels (subfolders or documents). That import can create some issues due to incorrect configuration in place on original File Server. But how can we check one user complaining to not see or access the content as it was into the File Server ? That need to be reviewed at any SharePoint Content Level with Permission Management with "Administrator Permission" with the link "Manage Access". You have to select the link (at the bottom) "Advanced" to have the exact permission set configured at this level Based on that situation, you can decide what to apply at this folder or file level. You can: add a colleague or a group with appropriate permission (Read, Write or full control) Remove the specific permission of that level clicking on "Delete unique permissions" But this config could concern many other sublevels and wait the user complains is probably not the best option. How to track folders or files with unique permissions ? You can do that using the Document Library Permission Settings from: Library Settings > "Permissions for this Document Library" You will have the permission configuration in place at this root Document library level. But the first line will explain (if that is the case into your document library) the status of sublevel: Some items of this list may have unique permissions which are not controlled from this page. Show these items. When you are clicking on that link it will show you a part of customized levels. You can change the permission set for each of those level clicking on "Manage Permissions" to have the same details we look in the first part of this message. Now as you can imagine with a document library could contains thousands of folders, this manual action is really huge. How reset all customized permissions configured at sublevel ? That is the best option you can select as site admin, using PowerShell and an interesting PS Module named: SharePointPnPPowerShellOnline This following script will help IT Team to reconfigure all content customized into the document library and cancel this and reconfigure permission inheritance instead. #install-module SharePointPnPPowerShellOnline -Force #to install that module the first time only Write-Host " ---------------------------------------------- " Import-Module SharePointPnPPowerShellOnline Write-Host " ---------------------------------------------- " #Config Variables $SiteURL = "https://yourtenant.sharepoint.com/sites/YourSiteCollection/" $ListTitle = "Document Library Name" $foldertoscope = "/sites/YourSiteCollection/YourDocumentLibrary/" #Connect to PnP Online Connect-PnPOnline -Url $SiteURL -UseWebLogin $ctx = Get-PnPContext $ctx.Load($ctx.Web.Lists) $ctx.Load($ctx.Web) $ctx.Load($ctx.Web.Webs) $ctx.ExecuteQuery() $ll=$ctx.Web.Lists.GetByTitle($ListTitle) $ctx.Load($ll) $ctx.ExecuteQuery() ## View XML $qCommand = @" <View Scope="RecursiveAll"> <Query> <OrderBy><FieldRef Name='ID' Ascending='TRUE'/></OrderBy> </Query> <RowLimit Paged="TRUE">5000</RowLimit> </View> "@ ## Page Position $position = $null ## All Items $allItems = @() Do{ $camlQuery = New-Object Microsoft.SharePoint.Client.CamlQuery $camlQuery.ListItemCollectionPosition = $position $camlQuery.ViewXml = $qCommand ## Executing the query $currentCollection = $ll.GetItems($camlQuery) $ctx.Load($currentCollection) $ctx.ExecuteQuery() ## Getting the position of the previous page $position = $currentCollection.ListItemCollectionPosition # Adding current collection to the allItems collection $allItems += $currentCollection Write-Host "Collecting items. Current number of items: " $allItems.Count } while($position -ne $null) Write-Host "Total number of items: " $allItems.Count for($j=0;$j -lt $allItems.Count ;$j++) { if($allItems[$j]["FileRef"].StartsWith($foldertoscope)) { Write-Host "Resetting permissions for " $allItems[$j]["Title"] ".." $allItems[$j]["FileRef"] $allItems[$j].ResetRoleInheritance() $ctx.ExecuteQuery() } } Now you can adapt the permissions as much as you need to Fabrice Romelard65KViews1like18CommentsA new day for SharePoint Server
Posted at https://aka.ms/SharePoint/SPSE. Today we’re excited to open the window to our vision, strategy, and future for SharePoint and provide a first look at the most recent developments with SharePoint Server. SharePoint has been a key accelerator for collaboration and productivity for decades, from the business value for organizations looking to modernize their workplace and infrastructure to the technical value delivers to IT professionals and developers, and more recently with new hybrid investments for those customers looking to enrich their existing investments with cloud innovation. With the 20 th anniversary of SharePoint just behind us, it’s a great time to look back and provide a little historical SharePoint information. 20 years ago, “Exchange and SharePoint became best friends.” Exchange Server worked on a new information store (Web Store) to support document, web content, and e-mail management. Codename Tahoe (the genesis of SharePoint Products and Technologies) advanced Exchange Server introducing document management capabilities through WebDAV (Document Authoring and Versioning) in addition to an improved search and indexing engine. Exchange Server and Tahoe would represent a new, next generation messaging, collaboration, and document management platform. Now we’re delighted to share our progress towards the next generation of SharePoint, built on these same principles. SharePoint Server Subscription Edition represents the next step in the SharePoint Server journey emphasizing the specific needs of our on-premises customers. We designed SharePoint Server SE around the core principles of: Always up to date Secure and reliable Designed for you Always up to date Organizations require collaboration, communication, and productivity solutions to be both cost-effective and flexible. SharePoint Server Subscription Edition can help you achieve new levels of reliability and performance, delivering features and capabilities that simplify administration, protect communications and information, and empower people in your organization to achieve more. Continuous updates Pressure to optimize your IT infrastructure for ever-changing business conditions requires you to be agile, and that means investing in solutions that provide reliability and choice. SharePoint Server Subscription Edition provides the flexibility to tailor deployment based on your unique business needs. With SharePoint Server Subscription Edition, you'll end the cycle of long and costly major version upgrades to get new features and remain in support. Microsoft will deliver our latest innovations to customers through updates that can be installed on your SharePoint Server Subscription Edition farms. Upgrade from where you are SharePoint Server Subscription Edition makes it easy to get up and running with new upgrade options that allow you to upgrade directly from SharePoint Server 2016 without having to first upgrade to SharePoint Server 2019. Secure and reliable Complying with regulatory standards and preventing unauthorized access to business critical and personal data is a continual priority for organizations and corporate IT. Modern infrastructure support SharePoint Server Subscription Edition provides scalability, reliability, and security while allowing you to take advantage of the latest hardware innovations and computing technologies—making it capable of handling enormous amounts of data faster, more efficiently, and at a lower cost. Secure communication With the support for Windows Server 2022, you not only benefit from the latest in security, but also native support for features, such as TLS 1.3. TLS 1.3 is the latest version of the internet’s most deployed security protocol, which encrypts data to provide a secure communication channel between two endpoints. TLS 1.3 eliminates obsolete cryptographic algorithms, enhances security over older versions, and aims to encrypt as much of the handshake as possible. Designed for you SharePoint Server Subscription Edition has been designed around the unique needs of on-premises scenarios, delivering the security, reliability, and management improvements specific to those needs. New features include OpenID Connect support, People Picker improvements and more. OpenID Connect SharePoint Server Subscription Edition adds support for the OpenID Connect (OIDC) 1.0 authentication protocol. OIDC is a modern authentication protocol that makes it easy to integrate applications and devices with your organization's identity and authentication management solutions to better meet your evolving security and compliance needs. For example, you can enforce authentication policies such as multifactor authentication (MFA), conditional access policies based on device compliance, and more. Enhanced People Picker for modern authentication In SharePoint Server Subscription Edition, the People Picker has been enhanced to allow resolving users and groups from modern authentication (trusted identity providers), such as SAML 1.1 and OIDC 1.0. This allows the People Picker to only resolve valid users and groups without requiring a custom claims provider. To learn more about all of the improvements in SharePoint Server Subscription Edition see https://go.microsoft.com/fwlink/?linkid=2168262. This is just the beginning of what you can expect for SharePoint Server Subscription Edition. To download SharePoint Server Subscription Edition Public Preview visit https://go.microsoft.com/fwlink/?linkid=2168051. Language Packs can be downloaded from https://go.microsoft.com/fwlink/?linkid=2168052. Share your feedback and questions in our community forum at https://go.microsoft.com/fwlink/?linkid=2167959.64KViews17likes14Comments