Power Platform Community Forum Thread Details

Hi There,

We’ve noticed that our Enrolments Power Automate flow, which was previously working fine, has recently started failing unexpectedly. The error message is:

"The value cannot be null. The action type 'AppendToArrayVariable' only supports values of types 'Float, Integer, String, Boolean, Object'."

This is occurring during an Append to array variable step where we're appending the course LMS number to an array. Given that the flow has been functioning as expected until now, there should be a value present, so it's unclear why it's suddenly failing.

Could someone please assist in identifying the root cause and help resolve this issue?

Happy to provide additional details or screenshots if needed.

Thanks in advance,

Categories:

Building flows

Hi @MV-09050036-0

We will not be able to tell you why you don't data all of a sudden that is not really feasible.

What you need to do, is simply look at your list rows 12 action.

You are assuming that you are settings its output (value) to the Apply to each (a guess as its not explained clearly)

1. So its honestly as simple as taking the output of the List rows 12 raw output and poppin it into a JSON viewer, or notepage or visual studio, aka any text reader, but its better to put it into a tool that can format it as JSON

2. Then in your flow run, You need to click through the 72 iterations to specifically see what column it is saying is null s you have the action closed and no specific data points for us to see.

3. After you do that, you will clearly be able to see what "column" of data (for that row/iteration), you tried to append, and it was in fact null.

Then go look at your data in your JSON view I express above and you will look at that column and go hmm it is blank.

4. The flow will not make it blank, thats impossible. If there is data it would be there.

So back track from there by going to the Dataverse table, and see why they column has nulls.

Just in the flow run you shared, you should have no issue click through the 72 to see which failed, or just click Next Failed and go right to it.

You will then know what data point you are on and can compare that to the JSOn which will probably be blank. then use that to go into Dataverse via the power apps portal UI to look at the Table. Click edit and it will list all the rows.

Something maybe not have changed in your flow, but something changed in how data is being created in Dataverse for the missing null column