Power Platform Community Forum Thread Details

hello!

I attempted to set up this project management template for my organization's teams and sharepoint site- https://community.powerplatform.com/galleries/gallery-posts/?postid=2dcb2c20-9f8a-4e49-a1aa-82247d8a1455
but have encountered trouble at the initial install flow [TemplateProjectTrackerList]. I have followed the instructions provided in the video and restarted the process twice to be sure. I looked for anyone having similar issues in the comments of the original post and attempted to ask for help there. I appreciate the help.

This is the error message that appears-

Action 'ListGUID' failed: Unable to process template language expressions in action 'ListGUID' inputs at line '0' and column '0': 'The template language expression 'body('SP_HTTP_Create_list')?['d']?['id']' cannot be evaluated because property 'd' cannot be selected. Property selection is not supported on values of type 'String'. Please see https://aka.ms/logicexpressions for usage details.'.

The step of this flow is titled "ListGUID" and this is the code behind it-

{
"type": "Compose",
"inputs": "@body('SP_HTTP_Create_list')?['d']?['id']",
"runAfter": {
"SP_HTTP_Create_list": [
"Succeeded"
]
},
"metadata": {
"operationMetadataId": "170b1cf2-3ee2-4b4d-a9ee-d88f902c0955"
}
}

Screenshot 2026-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Power Automate Mobile App

Power Automate Desktop

Hi,

I’ve run into this before with older SharePoint REST-based templates. The issue isn’t actually the Compose action itself it’s that the SP_HTTP_Create_list step is returning a string, not a JSON object, so the expression can’t access ['d']['id'].

Here’s how you can fix it.

Step 1: Check the HTTP action headers

Open your flow → edit → expand SP_HTTP_Create_list and make sure these headers exist:

Accept: application/json;odata=verbose
Content-Type: application/json;odata=verbose

Save and test again. This alone fixes it in many cases because it forces SharePoint to return the expected structure.

Step 2: If it still fails, adjust the Compose expression

Sometimes Power Automate treats the HTTP response as text. In that case, update your ListGUID (Compose) action from:

@body('SP_HTTP_Create_list')?['d']?['id']

to:

@json(body('SP_HTTP_Create_list'))?['d']?['Id']

Note: SharePoint often returns Id (capital I), not id.

Step 3: Confirm what SharePoint actually returned

If you're unsure, check a failed run:

Go to Run history

Open the failed run

Expand SP_HTTP_Create_list

Look at Body

You should see something like:

{
"d": {
"Id": "..."
}
}

Use whatever field name appears there (Id vs id) in your Compose expression.

This usually happens because the template was built against a specific SharePoint REST response format, and newer environments sometimes return slightly different metadata unless the verbose headers are explicitly set.

Once the Compose step can read the ID correctly, the rest of the template install flow should continue normally.