How is the object created? I probably would use a microflow that creates the object, sets the dates and also sets the reference. If this does not work edit your post with a screenshot of your domain model and the page / microflow where you create the object.
Well, the TourSchedule object is created by calendar itself, thanks to “On create microflow” setting ; I indeed use a microflow, with has the “TourSchedule” parameter.
The calendar widget creates the TourSchedule, sets the dates (depending on where the user clicked on the calendar), and is supposed to set the association I configured in “Create association” setting too. The fact is : the dates are well set, the association is not.
I uploaded the project here : https://github.com/lordlothar99/Mendix-testapp/blob/master/TestApp.mpk
My project organization :
Just to be clear :
“NoBounds” configuration (okay)
“WithBounds” configuration (ko)
I saw you created a pull request with some improvements in order to make this work. But your configuration doesn’t use “view start” and “view end” attributes in the calendar’s microflow. So it wouldn’t work for me, cause I would have too many objects..
Anyway I worked on this, I finally found a not-too-ugly way to make this work : Create a “TourSchedulePaging” object, with an ugly association to TourSchedule…
I commited the new version : https://github.com/lordlothar99/Mendix-testapp/blob/master/TestApp.mpk
Anyway, I think this is a bug (if not, why would there be a configurable “create association” ?)