Hi Cookers,

I have a problem with the Builder to display the good end value from Ajax FK cascade.
Here my MCD :


The purpose of this component is to display a FrontEnd Form.
A Registered User can choose first a Category of Training (Cat_id), then a Training course (Form_id), and finaly choose between several Session Date proposed ...
This is this value (Date_time) that i want to display in the Final FK tree. But i get nothing, no dates

Here the FK cascade :

Here the Ajax Combo configuration :

A lot of values are availables in the tables, but the final values (SessForm.date_time) are not displayed and I do not anderstand why ???



Is it a builder bug, or something wrong in my design ???

Thanks,
Marc

Sorry for beeing late.

By case, do you have rows in SessForm with the FK defined to the parent group ?
In you example it would be : "Administrator MISS - Module" defined in the Formation FK of any row of the SessForm Table.

Does it work if you use a text or a number instead of a date in the base FK to display ?
Because what I am sure is that you will not get any calendar at the end of the cascad chain. Only combo box is possible because it is a place for choosing an existing value. So the user is not asked to choose himself.
But the DateTime SHOULD work anyway.

Are you sure of your tests ?
Otherwise I will have a look.

By case, do you have rows in SessForm with the FK defined to the parent group ?
In you example it would be : "Administrator MISS - Module" defined in the Formation FK of any row of the SessForm Table.

Yes of course, I have 1 or more session date for each Formation.

Does it work if you use a text or a number instead of a date in the base FK to display ?

YES, it works if I change the Field type from Calendar to String.
Result :

The combo is fully populated when the field type is String, but not if the field type is DateTime.

But the DateTime SHOULD work anyway.
Are you sure of your tests ?

Yes I am

I will treat that in the 3.2 version.
At the moment, the ajax field will not be evolved because it is already 100% rewritten, waiting for the 3.2 release.
Hold On