(also posted for PowerPoint)

I love being able to take PDF screenshots or figures and paste them into documents, so that the quality of the documents remains high and the images aren't pixilated.

Unfortunately, with the latest updates to Office 2019 / Office 365 (at least with 16.21 190117), images inserted into PowerPoints and Word documents as PDFs become pixilated and desaturated as soon as the file is saved. The results look awful on any high quality display, and are unusable for presentations or reports (even sometimes illegible altogether).

This has made it capturing screenshots on a Mac or exporting high-quality images from other applications in PDF format as vector graphics and then pasting them into Word (or PowerPoint) no longer possible. It also has meant that any images previously inserted in PDF format have become irretrievably corrupted and unusable when those documents were saved -- a huge loss of a lot of important work. (The files look fine when first pasted -- they just become progressively more terrible each time the file is saved, which is when I first noticed the issue)

It would be really helpful if there was an option to NOT compress these files when they are imported, and to ideally keep them in PDF format instead (or at least avoid making into such low quality bitmapped images -- if they retained their quality, it would be fine). It's been awful trying to salvage painstakingly created document that has been ruined, and I'm always nervous now that Office is going to corrupt important documents with images in them when I save.

Thank you!

This is a particularly annoying bug. Please find a solution?

I've put a large number of older files I'm currently working on on my Mac into OneDrive. Every time I view/edit one of them using another device with MS 365 connectivity, or OneDrive online, the Creation Date changes to the current date and time.

I'm referring to the creation date of the file itself, the file metadata. It becomes the present date every time it's viewed on a different device.

For instance say I've created a file in August 2012 linked to research that is necessarily date ordered, I put it up on OneDrive, refer to it on my iPhone in the library, on 5th April 2019, and when I look at it again on my Mac the file's metadata is saying it was created on 5th April 2019.

Under normal circumstances it would be the Date Modified and Last Viewed that would change not the Creation Date.

This is how things work with any local file system as well as on iCloud Drive and DropBox,

The original file metadata is absolutely critical in file archiving, searching, reviewing and cataloguing etc. . it means that to be able to use OneDrive I have to make a copy of the original document onto it and then copy any work done on that copy back into the original doc to preserve the creation date. This is back to the days of juggling data on two machines before there were any cloud services at all.

Microsoft always manage to take something away, when it looks like they're giving you something. I regret taking out the 365 subscription. They so often run a steamroller through people's ways of working without any consideration it seems for end-user experience.

Steps to reproduce:

* Create recipent list CSV file and save it anywhere
* Create new blank Word document
* Start mail merge as letters and attach previously created recipient list CSV file
* Save and close the document
* Delete or rename the previously selected CSV file

When now opening the Word document again, Word claims about missing data source as expected. Do not save the Document when trying this to keep the non-existing data source referenced.

Execute the following AppleScript (e.g. in Script Editor, adjust path to Word document):

set mergefile to POSIX file "/Path/to/Document.docx"
tell application "Microsoft Word"
activate
set display alerts to alerts none
open file name (mergefile as text)
end tell

This will hang up Word and the AppleScript runs in a timeout.

When executing the script against a Word document without any attached data source, Word opens the document as expected

Word version: 16.13.1 (180523)
macOS version: 10.14.1

... and wanted to see that credit is given to the people who helped me.
Date: May 24, 2019
Time: approximately 2:15 PM, Eastern
Chandra at tech support gave me excellent information and was VERY helpful when we discovered I had purchased the wrong version of Office 365 for my needs. He then went the extra mile in explaining all of this to Maya in billing, who quickly and cheerfully refunded the "wrong" product and allowed me to purchase the right one (Office 365 Personal).

I was with IBM Tech support from 1981 through 1991 and only hope that I lived up the standards that these people showed me today.

Please let me know if a letter to Microsoft HQ would help these two in any way, and I'll send one.

The image distorts with every other work around. i dont understand why you would get rid of the only thing that works for apply backgrounds.

you have provided no work arounds for this and your support team can not advise of options to help or workarounds because they have no idea. instead they ask me to pledge to you to bring it back.

Please bring it back you are causing unnecessary headaches for your customers and if you plan to get rid of a tool or options you need to train your support team of the work arounds and what has been changed and why.

I am so frustrated with companies beings out updates every 6 months that are in no way beneficial to your customers. just create headaches in trying to find the work arounds or the 'new way' to apply.

If you are going to update anything, work on how touchy word is with images, and how your margins distort them. maybe apply layer options or being able to lock objects/pictures.

but most importantly you need to bring back the fill option in page colour drop down menu.

Thankyou.