web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / BUG! Sending copy/past...
Copilot Studio
Unanswered

BUG! Sending copy/pasted text to PVA chatbot in Teams causes unexpected formatting issues

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

This bug still exists even though a previous topic has it incorrectly marked 'solved'.

 

++ I am using Power Virtual Agents (web), published to Teams.

 

PVA chatbots are designed to receive plain text user input. The expected behavior is for PVA to strip away any 'behind the scenes' formatting and only pass plain text.

 

Expecting the customer to manually strip hidden formatting by copy/pasting into a notepad is not an acceptable workaround. This is terrible UX and could not be realistically communicated to the average end user.

 

This is a bug and needs to be addressed by Microsoft.

 

Example:

I highlight and copy the text 'REQ693205' from a Teams message I sent earlier:

tim_w_0-1612291757356.png

 

I then paste this text "REQ693205' into teams and send the message to the chatbot:

tim_w_2-1612292009734.png

 

And even though it appears to have no formatting, the user response is saved as '\r\n\n\r\nREQ693205\n\n'

 

This also gets passed onto Power Automate and in my case breaks the flow as it is expecting "REQ693205"

tim_w_0-1612293481930.png

 

This is frustrating for both developers and end-users and is negatively impacting customer satisfaction and adoption.

 

This is unexpected, undocumented behavior that needs to be acknowledged as a bug so it can be fixed ASAP.

 

Thank you.

I have the same question (0)
  • CU22081450-0 Profile Picture
    Most Valuable Professional on at

    Hi @Anonymous ,

     

    Thanks for your feedback! 🙂

     

    You can do a workaround replacing \r\n and \n\n values into the workflow (Power Automate).

    Follow below some posts that can help you:

    Solved: Replace Newline in Flow Expression - Power Platform Community (microsoft.com)

    Solved: Split at \r\n\r\n - Power Platform Community (microsoft.com)

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Thanks @renatoromao for your response! I appreciate your help but I must emphasize that this is not an acceptable solution. It is not realistic to rely on a Power Automate function to correct each and every message that could possibly be copy/pasted. This would add substantial development overhead... so much that it negates much of the value gained by using PVA in the first place. The only way to guarantee consistent behavior is to correct the underlying bug.

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Hi @Anonymous @renatoromao 

    Maybe try adding the following step(s) to your Power Automate flow to convert the PVA Input(s) to Plain Text

    https://docs.microsoft.com/en-us/connectors/conversionservice/

    Simply put the PVA Input required in this:

    nick_g_0-1612446229451.png

     

    nick_g_2-1612446331600.png

    nick_g_3-1612446400340.png

     

    Note this is a (preview) feature but seems to do the trick.

    Cheers

  • Community Power Platform Member Profile Picture
    Microsoft Employee on at

    Fantastic workaround, thank you! This should hold me over until the bug is fixed.

  • hhghjhhghjhg Profile Picture
    2 on at

    jgghghjhgbhfk

    Spoiler (Highlight to read)

    @Anonymous wrote:

    This bug still exists even though a previous topic has it incorrectly marked 'solved'.

     

    ++ I am using Power Virtual Agents (web), published to Teams.

     

    PVA chatbots are designed to receive plain text user input. The expected behavior is for PVA to strip away any 'behind the scenes' formatting and only pass plain text.

     

    Expecting the customer to manually strip hidden formatting by copy/pasting into a notepad is not an acceptable workaround. This is terrible UX and could not be realistically communicated to the average end user.

     

    This is a bug and needs to be addressed by Microsoft.

     

    Example:

    I highlight and copy the text 'REQ693205' from a Teams message I sent earlier:

    tim_w_0-1612291757356.png

     

    I then paste this text "REQ693205' into teams and send the message to the chatbot:

    tim_w_2-1612292009734.png

     

    And even though it appears to have no formatting, the user response is saved as '\r\n\n\r\nREQ693205\n\n'

     

    This also gets passed onto Power Automate and in my case breaks the flow as it is expecting "REQ693205"

    tim_w_0-1612293481930.png

     

    This is frustrating for both developers and end-users and is negatively impacting customer satisfaction and adoption.

     

    This is unexpected, undocumented behavior that needs to be acknowledged as a bug so it can be fixed ASAP.

     

    Thank you.


     wrote:This bug still exists even though a previous topic has it incorrectly marked 'solved'. ++ I am using Power Virtual Agents (web), published to Teams. PVA chatbots are designed to receive plain text user input. The expected behavior is for PVA to strip away any 'behind the scenes' formatting and only pass plain text. Expecting the customer to manually strip hidden formatting by copy/pasting into a notepad is not an acceptable workaround. This is terrible UX and could not be realistically communicated to the average end user. This is a bug and needs to be addressed by Microsoft. Example:I highlight and copy the text 'REQ693205' from a Teams message I sent earlier: I then paste this text "REQ693205' into teams and send the message to the chatbot: And even though it appears to have no formatting, the user response is saved as '\r\n\n\r\nREQ693205\n\n' This also gets passed onto Power Automate and in my case breaks the flow as it is expecting "REQ693205" This is frustrating for both developers and end-users and is negatively impacting customer satisfaction and adoption. This is unexpected, undocumented behavior that needs to be acknowledged as a bug so it can be fixed ASAP. Thank you.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 309

#2
11manish Profile Picture

11manish 187

#3
chiaraalina Profile Picture

chiaraalina 101 Super User 2026 Season 1

Last 30 days Overall leaderboard