Filter second level array

[Anonymous]

Hi community,

I have the following output in a JSON compose sample with 3 transaction IDs.

[
  {
    "id": "123456",
    "fee_details": [
      {
        "amount": 70,
        "currency": "eur",
        "type": "payment_fee"
      }
    ]
  },

  {
    "id": "258796",
    "fee_details": [
      {
        "amount": 81,
        "currency": "eur",
        "type": "transaction_fee"
      }
    ]
  },
  {
    "id": "758945",
    "fee_details": []
  }
 ]

The action I want to perform is to just keep the transactions that have type = "payment_fee". There is an additional complexity, as the "fee_details" is sometimes empty.

I've seen a lot of documentation regarding how to filter a first level array, but not about filtering a second level array.

Your support will be much appreciated.

[abm]

Hi @Anonymous 

So when you filter type "payment_fee" you expect to get the related id as well or just the fee details only?

Thanks

[Anonymous]

I would need the complete collection as I want to insert the ID later on in an excel file.

[abm]

Hi @Anonymous 

Thanks for your reply. I have made a video based on this. Please have a look.

https://youtu.be/5OPybbODtoM

If you found it useful please like and subscribe my channel.

Thanks

[DamoBird365 · Accepted solution]

Hi @Anonymous 

Can I throw a different method into the mix?  I am a fan of Select which is often overlooked.  You can achieve this in 2 actions as follows.

You can see from the screenshot below the repurposed array and the final output of a single object based on the fee type equals payment_fee.

Please consider accepting my answer as a solution if it helps to solve your problem.

Cheers
Damien

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

[abm · Accepted solution]

Hi @DamoBird365 

Thanks for pointing out the Select Action step. Of course then we could avoid that iteration which I explained but here the user mentioned fee_details[] array can be empty as well. Could you expand your first action step as well? 

Thanks

[Anonymous]

Thanks a lot for such a detailed solution, even with a video support with explanations, this was totally beyond my expectations, but it helped me a lot to keep learning how to work with arrays. You gained a new follower in your youtube channel!

[Anonymous]

Hi @DamoBird365 !

I will also try your solution as a parallel option. I never used select before, so it will also help me to understand the potential benefits for the rest of the flows I have created already. You also gained a new follower in youtube of course 😉

[abm]

Thanks a lot. This community have lots of good knowledge.

[DamoBird365]

Hi @abm 

Here's the full array in the opening compose.  It will handle the null array as the expression includes ? to return null if not found.  I think it's great to see both options - twice the learning 🙂 cheers.

Damien

[abm]

Thanks @DamoBird365