Multiple lines of text

[DCNehs]

All of my multlines that were set up with plain text stopped working last week.  In powerapps it shows as multiple lines and in the actual list itme it shows multiple lines of text, but when sending the email through PowerAutomate it sends as a single line now which wasn't happening before.  

Has something changed?  Is there something else we can do now?

I've tried using a Rich Text option but i don't like that on the PowerApps form, it allows an end user to change the font color, etc BUT when you save the information, it all gets deleted.  It's also a lot of space to take up on the form if it doesn't do what it's offering and will cause confusion. 

I was just on the verge of having a few forms and workflows go live, but this is an issue for them since they want the multiple lines of text in the email.

thank you in advance!!!! 

Is there any other solution so that it will email multiple

[abm]

Hi @DCNehs 

Set the email option "Is HTML" to No.

Thanks

[DCNehs]

@abm on the new send email templates, there is no longer a choice to do that unless it was moved somewhere else? I dont see it for normal send email or send email from shared mailbox which is what I'll be using for this particular need.

[abm]

Hi @DCNehs 

I was referring to Send email with options but yes you can't use that. Add a compose above the send email, then map the text under compose. Check the run history and see what format it is displaying?

Thanks

[DCNehs]

@abm I've never used compose.  Do I need to use a formula for that?  Sorry, I'm still very new to this.

[abm]

Hi @DCNehs 

Search for compose. Map the Power App description text here. Run the flow and check the history expand compose step and see the values.

[DCNehs]

@abm ok, here is what happened if i did it correctly.  In the email it still came out as a single line of text.  In the multiline column in the list it shows correctly with the names on 3 different lines.  Not sure how to get the breaks in there.

[abm]

Hi @DCNehs 

This is not the flow issue. Email is sending correctly in that format which contains the enter key. Check the below settings in your outlook and uncheck the remove extra line breaks in plain text messages.

Thanks

[DCNehs]

@abm I unchecked and had the same outcome.  Multiple lines of text came back as a single line in the email.

[abm · Accepted solution]

Hi @DCNehs 

I did tried the following way. Yes it was a bit tricky but worked for me. Please follow the below steps:

1. First I set the manual trigger for my testing.

2. Under the compose I have some text with enter keys

3. Intialised a string variable and under the value Press the Enter Key

4. Next compose I did a search and replace of enter key with <br> tag (HTML)

Here is the expression I used.

replace(outputs('Compose'),variables('EnterKey'),'<br>')

5. Under the mail body again I used the string expression to convert the output from the previous step 4

string(outputs('Compose'))

This is my result:

Thanks

[DCNehs]

@abm I'll give this a try Monday.  Today got a little busy.  THANKS!

[DCNehs]

@abm I've tried, but i think i'm just not understanding and not doing something correctly.  It wont send the initial email now.   It's unfortunate that it takes a lot of work to get multiline columns of information to be sent as multiple lines of text in the outgoing email especially when it was working a few weeks ago.   It's works fine as normal as long as I'm NOT using a PowerApp, but i'd really like for them to be able to use the specially designed form as requested.

I received the following error

Unable to process template language expressions in action 'Compose_2' inputs at line '1' and column '2827': 'String cannot be of zero length.
Parameter name: oldValue'.

[abm]

Hi @DCNehs 

Looks like you have null values getting some where. It's the data issue. Check your run history of your flow steps.

Thanks

[DCNehs]

@abm thank you so much for your help!!!

[abm]

Hi @DCNehs 

Thanks for your reply.

If your problem has solved, please go ahead and mark the post as solved by clicking “Accept as Solution” so that this thread will be marked for other users to easily identify!

Thanks