Answered

Unable to process template language expressions...at line '0' and column '0'

(0) Share

Report

Posted on by DecoyGOODz

I've built a flow following these instructions: youtube.com/watch?v=Om4beefKmV0&t=1201s

The relevant section starts at 14:20. I believe I followed the instructions correctly. However, I changed the flow a little to meet my use case.

The flow errors out on the second step with the error:

InvalidTemplate. Unable to process template language expressions in action 'Get_item' inputs at line '0' and column '0': 'The template language expression 'parameters('$connections')['shared_sharepointonline']['connectionId']' cannot be evaluated because property 'shared_sharepointonline' doesn't exist, available properties are ''. Please see https://aka.ms/logicexpressions for usage details.'.

I have verified the connections exist. I have tried exporting the flow and importing as new. I don't know what I'm missing. The error message seems vague to me but I am new to this.

Error messageFlow overviewRelevant stepsConnections

Categories:

Using flows

I have the same question (3)

All responses (8)

Answers (1)

v-xiaochen-msft on at

Like (1)

Report

Hi @DecoyGOODz ,

The reason for this error is that you are test running the flow using data from a prior test . So you could test it again manually.

Best Regards,

Wearsky

1 people found this reply helpful.

Was this reply helpful? Yes No
Verified answer

DecoyGOODz 13 on at

Like (1)

Report

Thank you for the response! Unfortunately, I would get the error no matter if the flow was triggered through power apps or run manually.

I was not able to resolve the problem and had to rebuild the flow from scratch. The rebuilt flow was identical, except with a new name. All tests ran flawlessly.

Was this reply helpful? Yes No
v-xiaochen-msft on at

Like (0)

Report

Hi @DecoyGOODz ,

There might be some issues with the previous flow... Anyway, the new flow solved it. Congratulations.

Best Regards,

Wearsky

Was this reply helpful? Yes No
RonaldLaan1984 2 on at

Like (0)

Report

I had the exact same error and had to rebuild the Flow as well. However I experienced it when after exporting the Flow. I hope Microsoft can look into this. To me this seems like a Bug.

1 people found this reply helpful.

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

Like (0)

Report

I tried all of the above and it didn't work. I was using the PowerApps v2 trigger in the flow. When I changed that to the original PowerApps trigger, it worked.

Was this reply helpful? Yes No
IT5 3 on at

Like (0)

Report

Thank you it helped, I did the same thing and it worked after rebuilding the flow

Was this reply helpful? Yes No
ialbasheir-kbr 87 on at

Like (0)

Report
This is an actual issue when moving away from PowerApps V1 to V2. Reverting to V1 solved the issue. Now with V1 is going away this Bug needs to be fixed. Any SharePoint action is not adjusting to the new trigger seen below in peek Code: I would try to export then fix the Json file then import it and see if it fixes it.
{ "inputs": { "host": { "connection": { "name": "@parameters('$connections')['shared_sharepointonline']['connectionId']" } }, "method": "post", "body": { "method": "GET", "uri": "rew" }, "path": "/datasets/@{encodeURIComponent(encodeURIComponent(''))}/httprequest", "authentication": "@parameters('$authentication')" }, "metadata": { "operationMetadataId": "xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx", "flowSystemMetadata": { "swaggerOperationId": "HttpRequest" } } }
SP with peek Code using a power App V2
{ "inputs": { "host": { "connectionName": "shared_sharepointonline", "operationId": "HttpRequest", "apiId": "/providers/Microsoft.PowerApps/apis/shared_sharepointonline" }, "parameters": { "dataset": "", "parameters/method": "GET", "parameters/uri": "" }, "authentication": "@parameters('$authentication')" } }

Was this reply helpful? Yes No
pappwrapp 7 on at

Like (0)

Report

I just figured this out!

I recently learned about V2 and thought I would convert a V1 flow to V2. That's when I got the error. 😞

Save your work in Power Automate then open your flow from Power Apps. Delete the V1 (or v2) trigger and add it back in. This won't delete everything that follows, but you may have to re-do a couple bits here and there. Save your flow in Power Apps. When you go back to edit in Power Automate the system recognizes the update. That's what worked for me, anyway. 🙂

1 people found this reply helpful.

Was this reply helpful? Yes No