This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When in Chats in Teams we used to copy conversations and paste them into other docs. This brought across name/date and chat text.
Now when we do this it only brings across the text; name/date are missing. This causes issues for us as we cannot keep accurate records.
Has this facility been changed/withdrawn in an update? Is there a workaround?
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Without the workaround, this really needs to be fixed. The Export API is overkill for grabbing a few messages.
yes, and the work around only worked briefly for me using the web version and then stopped working. Same thing happened at home - worked briefly and then stopped.
I've completely lost the ability of documenting conversations for my notes w/o taking twice as long to do it.
When will this be fixed?
There is a large segment of IT Support, Customer Service and other professions that need to be able to EASILY and SIMPLY copy and paste the conversations, INCLUDING the person and time stamp.
The work around does not work reliably, causing one to attempt to copy a couple of times before we capture the missing data.
As I understand the reason to remove that capability, a basic and handy functionality within the entire scope of Microsoft products, was to appease developers and programmers who only wanted the text.
I would politely suggest those user groups use their skills to strip out the data they do not want and let the rest of use have the use of one of the most basic of processes, cut, copy and paste.
I agree. Ultimately, why does it have to be so cut and dry. How about an OPTION? Check boxes are wonderful. It solves the problem to just give people the choice. Why take out a feature instead of just allowing a choice?
Or, as any product company would easily guess, provide a setting to choose from. With a default set on what is perceived to be the most common use for the feature, maybe, which I STRONGLY doubt is to strip out arbitrary information from a copy text operation.