Unanswered

Unable to integrate variable name in the HTML email template due to invalid expression error!

(0) Share

Report

Posted on by Dave Wi

Hello,

I have HTML email tempalte which works as expected when I do not add any dynamic variable in the body, however the moment I add dynamic variable ( e.x. UserName as indicated in the following screen) in the HTML email template, it throws following error:

Unable to integrate variable in email template.png

How can I resolve it?

Thanks,

Categories:

Building flows

I have the same question (0)

All responses (7)

Answers (0)

CFernandes 8,402 Most Valuable Professional on at

Like (1)

Report

Hey Mate,

@dave8

I would rather construct the whole HTML and pass the output of Compose action, to Send an Email

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No
Dave Wi on at

Like (0)

Report

Hi @CFernandes

I face the same error even in "Compose" action, I suspect there is something wrong in HTML!

Thanks,

Was this reply helpful? Yes No
CFernandes 8,402 Most Valuable Professional on at

Like (0)

Report

@dave8

If you try a simple HTML(with reference to my screenshot), then do you get the same problem?

Was this reply helpful? Yes No
Dave Wi on at

Like (0)

Report

simple HTML even in email body works as well as in compose, in my HTML, I have noticed that when I remove particular img tag, then it works, but if I add that, I get following error message while saving the flow:

The power flow's logic app flow template was invalid. The template language expression literal limit exceeded: maximum '131072' and actual '309602'

This happens only with particular image, in the same image tag, if I add another image source, then it works!

any clue?

Thanks,

Was this reply helpful? Yes No
Dave Wi on at

Like (1)

Report

Found out the culprit!

I am using base64 image source which is a leangthy code that is based on the image size it seems, as I minimized the image size and decoded that into base64, the same code with the expression worked out for me!

Thank you for your suggestions and attention!

Regards,

Was this reply helpful? Yes No
CFernandes 8,402 Most Valuable Professional on at

Like (0)

Report

Wohoo. I am glad that you have resolved the problem 😊

Was this reply helpful? Yes No
mpfeng 38 on at

Like (0)

Report

Thanks! I reduced the image size of the .png, then the new URI is also smaller and this time I didn't get the error.

Was this reply helpful? Yes No