JSON() doesnt include fields with blank values

[Anonymous]

I have a collection which is taking data from list. The collection has more than 30 fields and all fields are non mandatory. When i pass collection in JSON() , it takes the field only with value and ignore  blank field.

Set( glbExcelJSON, JSON(glbExcelColumns,IncludeBinaryData);

ExportLDMDev.Run(glbExcelJSON);

below is the screen shot of my collection (glbExcelColumns)

and JSON is (glbExcelJSON) : AllSalesPrivatePer is missing and many more..

[
{
"AllSales": "Specific Sales",
"AllSalesPrivate": "Sale Type",
"ApprovalDate": "2021-07-22",
"ApproverEmail": "neha.mittal@elders.com.au",
"ApproverName": "Neha Mittal",
"Auction": true,
"AuctionValuePerHead": 23,
"Author": {
"Claims": "i:0#.f|membership|neha.mittal@elders.com.au",
"Department": null,
"DisplayName": "Neha Mittal",
"Email": "Neha.Mittal@elders.com.au",
"JobTitle": "Contractor",
"Picture": "https://elders.sharepoint.com/sites/EldersIntranetTraining/LDMDev/_layouts/15/UserPhoto.aspx?Size=L&..."
},
"CM": true,
"CNVaulePerHead": 1,
"ClientAccountNumber": "ASZX",
"ClientTradingName": "qewdasxz",
"Coments": "qsza",
"CommercialSales": "Stud Sales",
"CostCentre": "2343",
"Created": "2021-07-22T05:59:10.000Z",
"CurrentCommisionRate": "Value Per Head",
"EX": true,
"EXValuePerHead": 1,
"Editor": {
"Claims": "i:0#.f|membership|neha.mittal@elders.com.au",
"Department": null,
"DisplayName": "Neha Mittal",
"Email": "Neha.Mittal@elders.com.au",
"JobTitle": "Contractor",
"Picture": "https://elders.sharepoint.com/sites/EldersIntranetTraining/LDMDev/_layouts/15/UserPhoto.aspx?Size=L&..."
},
"EffectiveDate": "2021-07-21",
"ExportUser": "neha.mittal@elders.com.au",
"FE": true,
"FEValuePerHead": 1,
"HO": true,
"HOValuePerHead": 1,
"ID": 30,
"LDMResourcesName": "Neha Mittal",
"Modified": "2021-07-22T06:00:25.000Z",
"Other": true,
"OtherData": "werwer",
"OtherValuePerHead": 1,
"PR": true,
"PRValuePerHead": 1,
"PendingWithEmail": "neha.mittal@elders.com.au;usman.bhatty@elders.com.au",
"PendingWthName": "Neha Mittal",
"Private": true,
"RequestType": "Permanent Commission Change",
"SaleVenue": "23ew",
"Species": "Cattle##Others",
"SpeciesOther": "3ewdas",
"Status": "Approved",
"TradingState": "NSW",
"ValuePerHead": 121123,
"{FilenameWithExtension}": "",
"{FullPath}": "Lists/LDMRequests/30_.000",
"{HasAttachments}": false,
"{Identifier}": "Lists%252fLDMRequests%252f30_.000",
"{IsFolder}": false,
"{Link}": "https://elders.sharepoint.com/sites/EldersIntranetTraining/LDMDev/_layouts/15/listform.aspx?PageType...",
"{Name}": "",
"{Path}": "Lists/LDMRequests/",
"{Thumbnail}": {
"Large": null,
"Medium": null,
"Small": null
},
"{VersionNumber}": "2.0"
},

[Pstork1]

That's the way JSON works in Power Apps.  I don't know of any way in Power Apps to force it to include fields that have blank or null values.

[Anonymous]

Thank Pstork1, do you suggest any other way to generate JSON in powerapps?

[Pstork1 · Accepted solution]

That is the only way to generate JSON in Power Apps.  The reason it doesn't add the null fields is that its normally used to send data from Power Apps to other programs.  Adding headers for null fields increases the size of the transfer for no benefit since its not transferring any information.

[viniciusgsf]

Hello!

I had the same problem, among several solutions that are very laborious, I found a simple and easy one.
in the PARSE JSON step, exclude the fields that may be null from the REQUIRED property, if this does not compromise your business rules, there is no problem.

[MathiasM]

Hi. 

I came across this thread because I have this exact requirement - only add populated columns from a collection to a JSON. But for me, it does not behave as described. Blank/null column values from my collection get added to the JSON. Was this behavior changed or is this a misunderstand on my end? See my test example attached. Thanks!

[viniciusgsf]

Hello!
Let me get this straight, you already send the fields as null or blank to your JSON, and a Power Automate captures this data, correct?
The problem must be in your Power Automate, even if you send null or blank values, the Power Automate JSON will not accept it and this will change the structure of your JSON output, so the change must be made in the Power Automate Flow and not on your Power Apps.
Tell me if this helped you?

[MathiasM]

Maybe I should have explained better: 

Yes, I basically already set the JSON with null or blank fields, as they are based on user input. The JSON then gets passed to a PowerAutomate as the input parameter. The problem is, that the interface on the other end does not accept empty fields - that is why I want to get rid of them in my JSON/collection. 

This is how I found this thread, and why I am confused that apparently I have a different experience than described here. 

[viniciusgsf]

Please send a printout of your problem so I can understand better.

However, see if in your Power Automate, in the step where you use Parse JSON, there are any fields that you send blank or null in the "Required" part, and remove them from there.

[MathiasM]

Thank you for your offer. I got a workable solution in my post here to remove the blank fields from the JSON in my PowerApp.