Enjoyed feeds in D7 and was glad to use it on my first D8 project. I followed this tutorials: https://petermcmillan.com/articles/drupal-8-importing-csv-data-feeds and https://metadrop.net/en/articles/import-your-content-feeds.
First attempt and I got "xxx field can not be null" error (though the title generated by https://www.drupal.org/project/auto_entitylabel worked correctly). After some research I found the reason might have been associated with csv data compatibility with field types (e.g. float numbers for integer fields). After correcting the field types it's creating the expected nodes but the fields are empty (even the expected auto-generated title). Unfortunately I cant use the Feeds import preview module.
See screenshot of my screenshot attached. Will appreciate directions on what to do or is this a bug?
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | member_details_feeds_package.zip | 48.71 KB | ojchris |
| #6 | feeds_errorCapture.PNG | 17.85 KB | ojchris |
| #3 | Screenshot_2019-10-13 Edit Member details feeds.png | 39.91 KB | ojchris |
| #3 | Screenshot_2019-10-13 Edit - .png | 23.17 KB | ojchris |
| #3 | Screenshot_2019-10-13 Mappings Member details feeds.png | 86.74 KB | ojchris |
Comments
Comment #2
ojchris commentedComment #3
ojchris commentedComment #4
ojchris commentedComment #5
megachrizDo the names of the CSV sources entered on the mapping screen match exactly with the column names from the CSV file? The names are case sensitive.
Is your site multilingual? There is an issue that if values are imported for a specific language, the UI may show empty values in the form when you view the site in an other language. (But it could be that this was an issue in the D7 version, I only remember having seen it.)
To avoid importing duplicates, it is recommended to set at least one mapper as unique.
Comment #6
ojchris commentedThanks for the response. They match exactly and I set the Member Unique Code as unique.. Here is the CSV file:

Site is not multilingual, just english
Comment #7
megachrizFrom the screenshots I don't directly see what could cause an import to fail. So I would need some more details about your setup.
Can you provide the following:
If you want to be sure that I can install your configuration, try to enable the created feature module on a clean install.
Comment #8
ojchris commentedLots of work but I guess I have no choice. D7 version was so seamless and easy to implement.
Comment #9
ojchris commentedHere is the features bundle zip written to system as "Member Details Feeds Package". I tried to setup on simplytest.me and bergste.in but installation failed. Downloading a fresh install via composer was taking forever. Does feature include depencdeny modules as the project required Feeds, Auto_entity_label, Group and Views? thank you.
24/10/19 Update:
Added omitted source file:
member details raw data
Comment #10
ojchris commentedI was knocked off by sudden health challenge.
I have been able to do a fresh D8 setup but when I tried to installed the ZIP folder the system returned error "ember_details_feeds_package.zip does not contain any .info.yml files." even though the package has info.yml in the bundle. I wonder how to fix that.
Comment #11
ojchris commentedI have been able to resolve this. I found
1) that the headers created in excel had spaces when I opened the file up in nopepad++. Example: I had " Group Code " rather than "Group Code".
2) Also the error messages of feeds in D* are not very explicit such that validation errors connected a single field can through up errors connected to other errors. The date only fields must be in the format yyyy-mm-dd else error.
3) Using existing fields in content types permits having machine names used in more than one instance. As a result feeds gets confused. Instance: I had group module fieds with field_group_code, yet one is able to create a content type field with the same machine name and this confuses feeds module in understanding which is referred. I found I had two fields in the content type sharing the same machine_name. This might be
4) The feed mappings somehow have a way of rearranging things as you work such that a mapping of "Designation" / "Designation" magically changes itself to "Date of Birth" / "Designation" hence you get error "this value cannot be null"
5) feeds is unable to import into the autocomplete fields of entity reference fields, hence fields are empty in the nodes.
I still have a textfield posing a challenge as it refuses to be imported.
Generally, I do believe the feeds module in D8 is a work in progress confirmed by the alpha status. Thanks to the current maintainer MegaChriz as it is clear feeds in D8 is far more complicated as the most mature CSV importer on Drupal I have come across.