Yes you need to pick a database field indeed. This is because CMSImport currently only looks at the mapped properties. This is because of performance reasons. Maybe it will change in a future release for now it might be a nice work around to havecolumns with null data in your datasource for those properties.
Default value for ignored fields
It would be real nice to be able to fill fields that aren't available in the source data, with a default value.
By choosing --ignore-- at the database column AND adding a default value with aditional mapping options
This is already possible but now results in an error message stating that you should choose a database field.
Hi Gijs,
Yes you need to pick a database field indeed. This is because CMSImport currently only looks at the mapped properties. This is because of performance reasons. Maybe it will change in a future release for now it might be a nice work around to havecolumns with null data in your datasource for those properties.
Thanks,
Richard
Thanks for the reply. That's indeed the approach I've taken. So it worked out in the end. :D
To have a work around for your performance issues, you could add an extra option to the dropdown list next to --ignore--: --default value--
Just a thought.
is working on a reply...