You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the case of select-type fields (single, multiple, tree, IRRE) it must be possible to set them to having no relations if the external data contains a null value. With #302, this became possible but not nice/official, as it implied add nullable => true to the TCA definition of such fields. Since this is not officially accepted, it is undocumented.
But select-type fields have a minitems property. If said property is 0 or not set at all, it means that the field is okay to accept no relations at all. This is equivalent to other fields being nullable.
Although the mapping configuration allows External Import to set a default value in such a case, the tool should also take into account any default value defined in the regular TCA.
The text was updated successfully, but these errors were encountered:
In the case of select-type fields (single, multiple, tree, IRRE) it must be possible to set them to having no relations if the external data contains a
null
value. With #302, this became possible but not nice/official, as it implied addnullable => true
to the TCA definition of such fields. Since this is not officially accepted, it is undocumented.But select-type fields have a
minitems
property. If said property is0
or not set at all, it means that the field is okay to accept no relations at all. This is equivalent to other fields being nullable.Although the mapping configuration allows External Import to set a default value in such a case, the tool should also take into account any default value defined in the regular TCA.
The text was updated successfully, but these errors were encountered: