Unanswered

Power automate requiring an integer, but the information is alphanumeric.

(1) Share

Report

Posted on by KR-30071928-0

Hello! I am making a flow to go through Planner tasks, go through Sharepoint list items, find matches, and then update one of the Sharepoint list values. To do this, my shared "value" between the list and planner for mapping is the planner task ID. The value is alphanumeric. Some examples of this format are: xtQHOdQX60mt7Mwr0VBJoWUAIwVs, YQzAf8ZRzkejcr_2ZL0XiQ2UAH3JX. However, at the end of my flow, it says " Error details: Input parameter 'id' is required to be of type 'Integer/int64'. ."

However, it will not let me convert it to an integer. This is the only shared value available to me. Any ideas?

Categories:

Building flows

I have the same question (4)

All responses (3)

Answers (0)

David_MA 12,966 Super User 2025 Season 2 on at

Like (1)

Report

Please capture a screen shot of the action where the error occurred and show its configuration and post it with your question.

Was this reply helpful? Yes No
Suggested answer

Pstork1 68,707 Most Valuable Professional on at

Like (1)

Report

I think the error is referring to the SharePoint list item ID, not the Planner Task ID. The SharePoint ID is an Integer. Can you provide a screenshot of a flow run with the error?

Was this reply helpful? Yes No
ChadVKealey 1,393 on at

Like (1)

Report

It sounds like in your SharePoint list you have a column that's storing the "Planner Task ID", is that correct? If so, you'll need to use a "Get items" (plural) action with an appropriate filter to retrieve the matching SP list item. If that column is named "TaskID", your odata filter query would be something like:

TaskID eq '<planner-task-id>'

The output of Get items will always be formatted as an array, even if only one item is returned. So, for example, if you add an "Update item" action and choose the ID from dynamic content, Power Automate will wrap that in an "Apply to each" loop. This is normal, but can be annoying. I usually add a Compose action with the expression:

first(<get-items-output-value>)

which will give you that first response value as an object. It's a little trickier to access the values in it (you need to use the proper notation), but better than a bunch of apply-to-each loops.

Was this reply helpful? Yes No