No SharePoint Properties Found in Word 365

Sean Achim 6 Reputation points
2021-05-04T21:27:18.75+00:00

This is immensely frustrating.

Mail Merge has been available in MS Word since it was in DOS! We could mail merge fields from SharePoint Portal Services from as far back as I can remember. I've thought that getting SharePoint Properties available in Word should be easy by now. I've had this problem before and it was resolved with an update, only to find that in May of 2021 it is still a problem to link fields in your document library into a document in Word.

This is not a new problem by any means.

Take a look at https://social.technet.microsoft.com/Forums/en-US/d1d1baf1-c8b8-4d0c-8aa0-0e1488ccb094/no-sharepoint-properties-found?forum=sharepointadmin
which was closed by the OP because she solved it without explaining how. This request was then moved over to the following link:
https://social.technet.microsoft.com/Forums/office/en-US/df984493-186e-49bf-aa2e-e3d05ce4ad34/no-sharepoint-properties-found-affects-only-some-site-collections?forum=sharepointadmin

As a collaboration tool the ability to mail merge large documents from a list in SharePoint into Word is an obvious choice - and yet...

Why is Microsoft dropping the ball on this so consistently year after year? This request has been repeatedly made since earlier than 2018.

I'm, like so many others, also opening this as a support ticket with Microsoft as an O365 client, but the answer should have been posted here so long ago.

It is disappointing, frustrating and infuriating that Microsoft can be so sloppy in its attempt to satisfy the user community's needs.

SharePoint
SharePoint
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
9,565 questions
Word Management
Word Management
Word: A family of Microsoft word processing software products for creating web, email, and print documents.Management: The act or process of organizing, handling, directing or controlling something.
891 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Sean Achim 6 Reputation points
    2021-05-12T20:18:54.473+00:00

    96083-ms-support-request-02.pdf

    This is an ongoing problem. I'm not backing down on the need to do something that is supposed to be part of the DNA of MS Word.

    I'm uploading my most recent feedback from Microsoft here.

    The point is that Microsoft is choosing to deprecate features that could possibly make it difficult to upsell a client to Office 365 in my opinion. They have therefore chosen to break features without any notification and without referencing any roadmap so that they can say that "that features is only supported within the Office365 ecosystem".

    That is a rubbish response. The lack of response from Microsoft in this regard is truly disgusting and I will be posting this on hellopeter as well if the answer is still unsatisfactory by the end of this week.

    1 person found this answer helpful.
    0 comments No comments

  2. Elsie Lu_MSFT 9,756 Reputation points
    2021-05-05T09:17:01.803+00:00

    Hi @Sean Achim , welcome to Q&A forum!

    Could you please let know your office version? Is your issue that columns not found in View>Properties? Screenshots will let us understand your issue better.

    Per my test, I created a new column1 in the Document library, and it will be automatically mapped to the office. Can you find the corresponding columns in File>Properties?
    93820-4.jpg

    93829-3.jpg


    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  3. Sean Achim 6 Reputation points
    2021-05-05T15:51:39.073+00:00

    MS Office Pro Plus 2019
    93949-ms-support-request.pdf

    Please review the support request that I had written.

    Please note that the link to the list within this document will not work for external parties, but is included for the sake of clarity.

    0 comments No comments