Sharepoint (2013) is making new versions without saving or changing the document
Sinds an update from Microsoft in Februari we have some problems in our Sharepoint list. When you open a Word document by clicking on the name of the document (wait for the document panel to appear), than close it without any changes, a new version is made. Note: When opening the document a message with read only appears. We don't click on 'edit document'. When closing the document, the message is still there, so we still have it open in Read only mode. When the approval workflow has been started, it is impossible for the approver to check the content of the document. When the approver opens the document and closes it after checking the content (without changing anything!) the workflow rejects the document. -) This part is solved by changing the workflow. On item change -) do nothing (in stead of reject item on change) Deleting documents, version history, or workflow history does not help. We found 3 workarounds: 1. Open the document by clicking on the menu (...) and then 'open'. Opening the document like this wil not give a new version. Read only message is not there. Document panel gives no problems. Not easy for our users that are used to click on the name. 2. Open the document by using download a copy Even more complex for users that the previous option 3. Change the column 'Name (linked to document with edit menu)' to 'Name (for use in forms)' You are now missing the edit menu. It is not easy to open a document and publishing is even harder. Not an option for our users. 3a. Add the column 'Edit (link to edit item)' Will give the result of columns that are not in line with the content anymore. Summary: - Only Word documents - Opening by clicking on the name - If you close it before the document panel (Sharepoint properties) appears, there is no new version. - A message with Read only appears (we don't click on edit document) Does someone has the same problem? And can someone help us?
Latest thinking displaying SharePoint version number in a Word document
This seems to very unreliable or unpredictable. [Many years ago, I think it used to work fine - I sued it]. There are various incantations out there involving the using {Version} or {_UIVersionString} in Information management policy settings (having enabled) it and using label from Quickparts. Some say you need to make a content type for the library, other don't think this is necessary. Some report that the whole feature is deprecated. So can it be done in the lates version of everything? (Please don't link me back to one of the many old articles describing a method unless you are using it an up to date environment and it works) At the moment I have some documents that sometimes work and sometimes don't with docuemtns in the same library using the same template behing differently - a randomness I hate - I cant even build a reliable truth table for what makes it work or not: it's like a table lamp with a loose flex, flickering on and off. I keep think there must be an easier way to do this - surely we can't be the only orgnaisation who wants the same version number as the user sees in SharePoint as a field in the footer or the Word document? Why doe sversion (the column that appears when you enable version control) simply not appear as a document property or a field in Word? (Is there a way to add it without lables? Although the option to control the document information panel in word seems to have gone.)Can I use a High Trust SharePoint App as a Word Plugin?
Hi I've created a high trust sharepoint app that basically acts as a front for my 365 sharepoint site but gives extra functionality. This works well and although not currently live I'm confident will do the trick. I've been reading up with regards the Word app and using SSO https://learn.microsoft.com/en-us/office/dev/add-ins/develop/sso-in-office-add-ins There are some great examples here https://github.com/OfficeDev/Office-Add-in-samples/tree/main/Samples/auth/Office-Add-in-ASPNET-SSO Which allow the user to effectivily sign in and then the web part of the plugin can act accordingly. So basically the question is - can I do something similar with my SharePoint plugin? I.e something like the above, with probably some other controller/Model/View to control the Word App. It feels like this could work - however would like some 'direction' to see if this is a good model. Apologies for posting in SharePoint - seems like it could belong in both SharePoint and Word Plugins!
Sharepoint file properties - additional Word labels?
Hi all, I know there's the function to be able to display a Sharepoint file version number in Word through the use of a Quick Part label. Got that to work. Now, I'm trying to find a way to use more than the version label in Word. A question I have: Which Sharepoint metadata can I use and what are the internal names, such as {Version}? {Version} corresponds to {_UIVersionString}: How to I know the names and which Word can accept? Any ideas? Thanks!
Error with Login
Hello SharePoint Community! Question for you all. I have access to a few different SharePoint accounts for various clients, and I keep running into issues loading the apps when I'm switching between different accounts. This is the latest error message that I've been getting when I try to open the Word application on my computer. Access to the web version is just fine. Does anyone have a workaround?
In Word unter "Mit mir Geteilt" eine Datei entfernen
In meinen Word wird eine Datei angezeigt (unter mit mir geteilt), die ich nicht entfernen kann. Die Datei ist alt und nicht mehr existent. Der Support konnte mir leider nicht helfen und verwies mich auf diese Community. Ich kenne keinen SharePoint Admin den ich fragen könnte und ich bin mir nicht mal sicher ob die Datei auch wirklich von SharePoint aus geteilt wurde. In meinem OneDrive taucht die Datei nicht auf, auch nicht unter den geteilten Dateien. Nur in Word und Office Online Dashboard. Die Datei kann man auch nicht öffnen oder in Outlook finden wie die Seite es suggeriert. Ich bedanke mich für Hilfe!
SharePoint Word document linked from another Word document doesn't display properties
Hi, There seems to be an issue when linking Word documents placed on SharePoint from other Word document. Document properties are not displayed (quick parts) in that case. When opening the document directly from SharePoint, everything is fine. To reproduce the issue one can just open a new blank Word document and paste a link to the SharePoint document using its Document ID, for instance: http://tenant/site/_layouts/15/DocIdRedir.aspx?ID=XXX123 Then, when the hyperlink is clicked, document opens without properties populated. If, however, I create a direct link to the same file using document name, all properties are loaded, for example: http://tenant/site/documentlibrary/filename.docx Of course we would prefer to use links with document ID, so they stay valid if the document's name or location changes. Would anyone have any solutions to this? Thanks It is SharePoint 2016 Word version is 1809
power automate excel template
All, I am sure every one like the power automate capabilities with word template files. First we create a word file with several "Plain Text Content Control" from with in Developer Tab -> Design Mode. This is a lovely feature (Unfortunately a Premium Feature). While the use of word file is premium, not sure if you guys noticed that the Excel file is not a premium. Does any of you guys know of a way to use excel file to create "Plain Text Content Control" from with in Developer Tab -> Design Mode Possible?
SharePoint properties in Microsoft Word not accepting a date field
Hi SharePointers, I have an Office 365 tenant and I have recently noticed a much needed update to MS Word for Office 365. When I create a file in the desktop version and want to save it to a SharePoint document library, I was pleasantly surprised when the SharePoint Properties dialog box appeared on the right side of the screen. When I fill in the required fields for my document, and click "Retry Save", nothing happens. Here is an example of the screen. Upon further investigation, I have discovered that when the field is date/time field, that's when retry save doesn't work. If the field is a choice field that is required, the feature works fine. Is anyone else aware of this situation, and can you provide any insight into working out the problem. Thanks in advance.
