Checks if all properties of an object exist and adds them if they are missing

[3tsolutions]

Sometimes it happens that we receive an object, but not all the properties have been defined, and the flow fails and throws an error because the property does not exist.

Since we know what properties we are going to use in the flow, what we have to do is create an object with all properties null and then perform a union of the two objects.

First I created a flow, in this case the trigger is manual, then I initialize two string variables:

The first is the string of the json object with all properties set to null

In this example an object is defined with three properties: year, month, day

{"year":null,"month":null,"day":null}

The second is the string of the json object that has arrived, in this case simulated that one of the three properties is missing

{"year":2022,"month":12}

Then I parse the two json strings to get the two objects

Finally I define using Compose the union of the two objects with all the properties

union(body('Parse_JSON_Property'),body('Parse_JSON_String'))

The result as you can see is the object complete with all properties and with all values, and for missing properties it will be assigned null values

If you have nested objects, the child properties will not be automatically merged

In this example I added the time property with an object with three other child properties

{"year":null,"month":null,"day":null,"time":{"hour":null,"minute":null,"second":null}}

and I simulate that the object that arrived has no main properties and no child properties

After doing the parse of the two string variables (see above)

I perform the union of the child properties separately from the main ones

union(body('Parse_JSON_Property')['time'],body('Parse_JSON_String')['time'])

As you can see merging two objects fails to merge the child properties

So we need to set the property with children

setProperty(outputs('Union_JSON_Property_'), 'time', outputs('Union_JSON_Child_Property'))

[grantjenkins]

@3tsolutions 

It's normal for properties to be missing from your JSON if they don't have values.

Can you specify in what circumstances you get errors?

Note the two ways to retrieve a property - the second one won't fail if the property doesn't exist.

//expects the property to exist and thows an error if it doesn't
item()['name']

//property may or may not exist - notice the ? used here for optional. If the name property doesn't exist it will just return null
item()?['name']

[3tsolutions]

There are many cases where the absence of a property causes errors in the flow.
From logical to mathematical operations, from operations with dates to more.

Using the ? if the value of a property is not present it returns a null value,
but in many cases you need a default value that is not null.

For example if you perform a mathematical function

add(body('JSON')?['missing_property'],1)

or in a date and time function

formatDateTime(body('JSON')?['missing_property'],'yyyy-MM-dd')

or in a string function

substring(body('JSON')?['missing_property'],5,2)

When you try to use the value of a property the create a condition

When creating or updating an item in a Sharepoint list, if using formulas

Using my system I can define the correct default values ​​of object properties so that no errors occur during the flow.

[grantjenkins]

@3tsolutions I was probably more referring to this post where you are defaulting all of the values to null which would still encounter all the errors you listed above. And using ?['property_name'] would already return null anyway.

If you were talking about setting valid default values to get around these errors, then that would make sense.