Office365Outlook.sendmailV2 failed problem

(0) Share

Report

Posted on by ramzez

312

I am sending an email with a pdf attachment which has worked fine until today.

Today I started getting the following error message:

"Office365Outlook.sendEmailV2 failed: The data returned in the response is invalid. Response data should be a valid JSON object."

The email still works as it should.

Any ideas why this error message is being displayed?

This is the code I'm using.

UpdateContext({varPDFBlob: PDF(contPDFText_1,{ExpandContainers: true})});
If(
 SendAssessmentEmail,
 
 Office365Outlook.SendEmailV2(
 If(
 cboxBlockEmail_1.Checked,
 varUserSettings.UserEmail,
 Not(cboxBlockEmail_1.Checked),
 varUserSettings.UserEmail & ";" & "another@email.com"),
 $"text text text {frmAssessment_1.LastSubmit.NameOfPersonBeingAssessed}",
 $"text text text",
 {Attachments: Table({Name: "Name of attachment " & frmAssessment_1.LastSubmit.NameOfPersonBeingAssessed & ".pdf", ContentBytes: varPDFBlob})}
 )
 );

Categories:

Building Power Apps

I have the same question (0)

All responses (8)

Answers (1)

Sort by

iAm_ManCat 18,256 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Do you have the ParseJSON/Untyped feature setting enabled for your App?

Was this reply helpful? Yes No
ramzez 312 on at

Like
a
(0)

Report
Copy link

Link copied!

Yes it is on. The email is sent and the pdf is attached and the error message is shown only after running the code.

Was this reply helpful? Yes No
Verified answer

iAm_ManCat 18,256 Most Valuable Professional on at

Like
a
(2)

Report
Copy link

Link copied!

Ok, the reason I ask is that the feature is still experimental, and as such shouldn't be used in any production/live apps (as it could break, change, or be removed at any time) - its likely that its treating the returned object as an incorrect type (UntypedObject) as I don't think its compatible with all function calls.

Have you tried casting it explicitly to JSON using the JSON() function? its kind of part of the issue with the ParseJSON/UntypedObject feature where you have to cast it explicitly - there's a feedback link here:

https://powerusers.microsoft.com/t5/Power-Apps-Experimental-Features/ParseJSON-feedback/m-p/1877977

Your second option would be to try turning off that feature and seeing if that resolves your issue?

Was this reply helpful? Yes No
ramzez 312 on at

Like
a
(1)

Report
Copy link

Link copied!

Turning off the ParseJSON/Untyped feature setting does resolve the issue.

However I would like to experiment with the ParseJSON at the same time so what would be the correct way of using the JSON function in this case?

Was this reply helpful? Yes No
ramzez 312 on at

Like
a
(2)

Report
Copy link

Link copied!
Upon further testing I'm getting the same error message with just the following basic code and ParseJSON/Untyped feature setting turned on:
Office365Outlook.SendEmailV2( varUserSettings.UserEmail, "title text", "body text" )
I'll post this on the Experimental section as it seems to be only related to the ParseJSON/Untyped feature.
Thank you for your help.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

I just started having the same issue yesterday. The only thing causing it in the app I'm working on is the Parse JSON experimental setting being turned on. hmmm

Was this reply helpful? Yes No
iAm_ManCat 18,256 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Please make sure to give your feedback at the thread for the experimental feature so that they know its affecting people 🙂

https://powerusers.microsoft.com/t5/Power-Apps-Experimental-Features/ParseJSON-feedback/m-p/1877977

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Done, thanks!

Was this reply helpful? Yes No