Filter empty values from get items to array

(0) Share

Report

Posted on by JOAS_Niels

180

Hi everyone,

I'm having trouble filtering Sharepoint records with using a filter array action. I can't filter the SharePoint items directly, because I need the full results for another part of my flow, so I want to filter the results with a filter array action. It seems quite straight forward, but I get a body type from my Parse JSON action instead of an array.

This is the first part of the flow:

I used the output of the Filter array action to generate a schema. for the Parse JSON action

I then want to append my array with the results, but I get this error:

Unable to process template language expressions in action 'Parse_JSON' inputs at line '0' and column '0': 'The template language expression 'outputs('Filter_array')['body/value']' cannot be evaluated because property 'body/value' doesn't exist, available properties are 'body'. Please see https://aka.ms/logicexpressions for usage details.'.

I can only put a Body as input for the "For each".

Output Filter Array:

Spoiler (Highlight to read)

Can you help me figuring out what I'm missing here, please?

Categories:

Building flows

I have the same question (0)

All responses (6)

Answers (1)

Pstork1 68,707 Most Valuable Professional on at

Like (1)

Report

OK, I think I've got this figured out. In the array output of the Get items there is a field called

"@odata.etag": with a value that looks like this: "\"1\"", If you look close at that value it translates to a value of "1". Its a string embedded in a string using escaped quotes. My theory is that that field value is causing the Parse JSON to fail. I was able to reproduce your issue when I used the full get items array as input for the parse JSON.

The solution was to do a Data Select of the fields I wanted in my output and not include the @OData.etag. Unfortunately that meant I needed to do another Parse JSON before the filter array so I could use the fields for filtering. but once I did that it all worked as expected.

Was this reply helpful? Yes No
JOAS_Niels 180 on at

Like (0)

Report

@Pstork1 wrote:
OK, I think I've got this figured out. In the array output of the Get items there is a field called
"@odata.etag": with a value that looks like this: "\"1\"", If you look close at that value it translates to a value of "1". Its a string embedded in a string using escaped quotes. My theory is that that field value is causing the Parse JSON to fail. I was able to reproduce your issue when I used the full get items array as input for the parse JSON.

The solution was to do a Data Select of the fields I wanted in my output and not include the @OData.etag. Unfortunately that meant I needed to do another Parse JSON before the filter array so I could use the fields for filtering. but once I did that it all worked as expected.
That seems very plausible, but I still get a body as output. This is driving me nuts.

This is my Select action:

This is the result of my Select action:
This is my Parse action:
Am I doing something wrong? I used the output of the select as schema for my Parse action.

Was this reply helpful? Yes No
Verified answer

DamoBird365 8,942 Microsoft Employee on at

Like (3)

Report

Hi @JOAS_Niels

It's a bug. The new designer is giving you a dynamic value that doesn't exist. You want body('filter_array') which is visible on the classic designer but not on the new designer. See here https://www.youtube.com/watch?v=4IphRdADJBc&t=457s

Cheers
Damien

Please take a look and subscribe to my YouTube Channel for more Power Platform ideas and concepts. Thanks

Was this reply helpful? Yes No
JOAS_Niels 180 on at

Like (0)

Report

@DamoBird365 wrote:
Hi @JOAS_Niels

It's a bug. The new designer is giving you a dynamic value that doesn't exist. You want body('filter_array') which is visible on the classic designer but not on the new designer. See here https://www.youtube.com/watch?v=4IphRdADJBc&t=457s

Cheers
Damien

Please take a look and subscribe to my YouTube Channel for more Power Platform ideas and concepts. Thanks
Thanks, @DamoBird365! That helped to resolve the issue. I couldn't get it to work with a Parse JSON action in between, but I managed to get it to work without it.

Was this reply helpful? Yes No
Syzmik 5 on at

Like (0)

Report

This needs to made more common knowledge. Spent hours looking through support pages and this comment here is what resolved it for me. Thank you

Was this reply helpful? Yes No
CM24 on at

Like (0)

Report

I had this exact same issue. I was banging my head on the desk in frustration.

Was this reply helpful? Yes No