'Optional' child object

[Chicagoan2016]

We have a working object graph, today I found out the UI (and data) that corresponds to one child object are optional.
There is a field in the parent object where I know that the child object is optional but as far as I could tell there is no easy way to make a child object optional.

Kind Regards

[StefanOssendorf]

I quite didn't understand your objective here.
What do you expect our want to achieve with that?
Isn't it automatically optional if it's not there and no rule checks that?

[StefanOssendorf]

Mhmm. I can think of two solutions out of my head.

1. Create a rule with a higher priority as the rest and shortcut time execution when everything is empty.
2. Detach the child before calling save when it's optional

[Chicagoan2016]

I ended up using rule chaining, In the past short-circuiting worked per property.

How do you detach a child object? That could be very interesting since I suspect I will deal with this child object scenario in other projects.

[StefanOssendorf]

Mark it as deleted or set the property to null. That's what I meant with detach.

[StefanOssendorf]

Well deleted still has a big with being rejected ob the server when having errors. I think there should be an issue somewhere for that

[Chicagoan2016]

I have never tried making a child object property null but If I recall correctly from the days of Csla 3.8x making a child object property null was an 'involved' process.