Data type for PowerApps parameter changes -- Why?

(0) Share

Report

Posted on by teylyn1

360

Hello,

a few weeks ago I built a flow that gets started from a button in a PowerApp. It sends a SharePoint list item ID to the flow.

The flow reads the ID into a variable and then passes it on to actions that pull that item from SharePoint. The variable was initialized with the data type string. All was good.

Yesterday, that flow threw an error, saying that the variable of type String cannot be updated with a value of type Integer.

I don't know why that happened, since neither the PowerApp nor the Flow had been changed. OK. I changed the variable type to Integer and the flow ran fine again.

This morning, the flow failed again, this time claiming that the Integer variable cannot be updated with a String.

WHAT IS HAPPENING HERE??

Can there please be some consistency? How do I resolve this?

I have the same question (0)

All responses (1)

Answers (0)

Pstork1 68,271 Most Valuable Professional on at

Like (0)

Report

Re: Data type for PowerApps parameter changes -- Why?

I suspect it happened because Microsoft tightened up the rules on data types and automatic casting. The Item ID is and always has been an Integer. I suspect in the past when you passed it to Power Automate it automatically cast it from an integer to a string and now its not doing that anymore. Since it is an integer if you want it to be a string you really need to surround it with the appropriate FormatNumber() function.

Was this reply helpful? Yes No