Forms Upload to Planner Task: URL with @ gets missinterpreted

(1) Share

Report

Posted on by wengerit

I have built a flow that takes the data from a users Forms submission and converts it into a Planner Task. So far so good. I'm also trying to attach the attachment the user provided in the Forms to the Planner Task. That worked well in my Dry-Runs (with the Flow Component "Invoke an HTTP request" and a Graph Call against https://graph.microsoft.com/v1.0/planner/tasks/TASKID/details). But now if I'm using this within the flow, the step always fails, because the Attachments coming from Forms have the Username in the Filename (MyPDF.pdf gets renamed to MyPDF_user@domain.com.pdf). Power Automate and or the Graph API now thinks I'm trying to do something with odata-Instances:

The request is invalid:
The annotation 'TENANTdomain.io.png' was targeting the instance annotation 'https://TENANTname-my.sharepoint.com/personal/rolf_TENANTdomain_io/Documents/Apps/Microsoft%20Forms/FLOW%20TEST/Question/Screenshot%202025-04-01%20at%2014.42.26_rolf'. Only the 'odata.type' annotation is allowed to target an instance annotation.

Even with the URL encoded again we have a similar Error:

The request is invalid:
An unexpected instance annotation name 'https%3A%2F%2FTENANTname-my.sharepoint.com%2Fpersonal%2Frolf_TENANTdomain_io%2FDocuments%2FApps%2FMicrosoft%2520Forms%2FFLOW%2520TEST%2FQuestion%2FScreenshot%25202025-04-01%2520at%252014.42.26_rolf%40TENANTdomain.io%25201.png' was found when reading from the JSON reader, In OData, Instance annotation name must start with @.

Also using ' instead of " in the body of the Graph Request does not help. The Graph-Request looks like this:

{"references": {
        '@{variables('formUrl')}': {
            "@odata.type": "#microsoft.graph.plannerExternalReference",
            "alias": "attachment.png",
            "type": "Other"
        }
    }
}

Does somebody have a new Idea for me?

Regards, Rolf

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Michael E. Gernaey 53,928 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @CU01041619-0

I am not following this:

But now if I'm using this within the flow, the step always fails, because the Attachments coming from Forms have the Username in the Filename (MyPDF.pdf gets renamed to MyPDF_user@domain.com.pdf). Power Automate and or the Graph API now thinks I'm trying to do something with odata-Instances

Can you please share this? I am unaware of what you mean here. It would help to see some pictures.

Please share pictures of your flow, your configuration of the steps etc. Multiple things do not make sense, and would so if I saw them.

Then you can use an image to call out what is wrong with it.

btw, I do not like use @{ } I take that out anytime it gets put in.

Was this reply helpful? Yes No
ronaldwalcott 3,847 Moderator on at

Like (0)

Report
Copy link

Link copied!

Attachments are weird with their naming. Have you tried renaming the attachment before creating the planner task call?

Was this reply helpful? Yes No
wengerit 2 on at

Like (0)

Report
Copy link

Link copied!
Hi everyone

@ronaldwalcott well it makes kind of sense to add the username to the file user submits via a form. It makes the filename unique and human readable. I have not tried the renaming approach yet. That will be my second priority, because I try to not mess with forms (if I'm renaming the attachment, the reference in the form submission probably gets invalid).

@Michael E. Gernaey I did a dry run, applying a attachment to a planner task, with a hardcoded test-URL:

This works fine and does what I want: attach the png to the planner task.

But now with the URL taken directly from a form-Submission:

I get the above mentioned error, because the URL looks like this:

https://TENANT-my.sharepoint.com/personal/rolf_TENANTdomain/Documents/Apps/Microsoft%20Forms/FLOW%20TEST/Question/Screenshot%202025-04-01%20at%2014.42.26_rolf@TENANTdomain%201.png

The Variable formUrl gets populated this way:

no matter if with our without the encodeUriComponent function, I'm getting one of the above mentioned errors, because the Flow or the GrapAPI is trying to do something with the @ and the tenant-domain that contains of course a dot.

This is the whole flow for reference:

Regards

Rolf

Was this reply helpful? Yes No