Answered

Collection - collect only non-blank fields or remove blank fields?

(0) Share

Report

Posted on by MathiasM

Hi,

I am building an App with user interaction and integration with a third-party system via http-request. I collect all the data in big collection at the end, convert it to JSON and pass it to my Flow. The basic process is working, but I am now stuck on one particular issue:

The user input can vary, but the third-party interface only accepts populated fields. I have the situation that I have to have e.g. multiple address line inputs, but they are not always filled out (based on the use case). I can't simply pass on all of the fields, since the interface then rejects the request because fields are empty/null (both is not accepted). Example:

In such a case, I would have to leave out the second address line (AdressLine2) completely in the request/collection:

So for me that means removing it from my collection or not collecting it at all at runtime, if the field is blank. My collection would have to be dynamic with regards to the columns, based on which fields are filled in by the user.

How can I achieve this seemingly easy task?

Thanks!

Categories:

Building Power Apps

All responses (2)

Answers (1)

Sort by

Verified answer

timl 37,287 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!
@MathiasM

I'm working on the assumption that your collection can contain multiple rows - some of which will have a addressLine2 value, and others not.

On the basis that you call the JSON function to generate the JSON, there's no way to conditionally exclude fields that are null.

A possible (although non-elegant) approach to this is generate the JSON and to strip out those fields that are null.

Substitute( yourJSON, """addressLine2"": null,", "" )

You can adapt this include other possibile null fields.

Substitute( Substitute( yourJSON, """addressLine2"": null,", "" ), """cityName"": null,", "" )
MathiasM 10 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you both for the replies!
@Ali_SZ_365 This solution would work for a simpler construct, but my final JSON that I pass on has a depth of 4 levels and various sub-arrays, so constructing this from scratch via variable seems not feasible.

@timl My collection indeed only contains one row (by design) - but it has various sub-tables with multiple rows. Your proposal works like a charm, although it is not elegant as you point out. But for me that is a viable solution. Thank you so much!