Update existing Content

Yes, with Feeds it is possible to update content that was not originally created by Feeds. In order to update content, you need to mark at least one mapping target on the mapping page as unique. Furthermore, the CSV column names configured on the mapping page needs to match exactly with the column names used in the CSV file.

How does your source look like? How did you configure your feed type? Is there a mapping target that you configured to be unique? If so, which one?

Same issue here... maybe we are not taking account of some setting...

About your questions, in my hand:

How does your source look like?

My custom source start:

Custom Columna CSV sources
riesgo_de_oidio riesgo_de_oidio
precipitacion_acumulada precipitacion_acumulada
humedad humedad
humedad_ayer humedad_ayer
codi_sigpac codi_sigpac

Last field, "codi_sigpac" is my "unique target"

How did you configure your feed type?

Fetcher: directory
Parser: csv

In fact, all the lines are processed, but all show this message "Skipped because new entities should not be created."

Well, these nodes already exist, but their fields are not populated yet or their values have changed in most of them.

Is there a mapping target that you configured to be unique? If so, which one?

codi_sigpac codi_sigpac

@calbasi
When I inspect the text that you posted I see:

codi_sigpac [space] [tab] codi_sigpac

So can it be that you added an extra space when you defined the source? codi_sigpac != codi_sigpac.

In 🐛 CSV headers with extra space don't get mapped to correct fields Needs work there is being worked on trimming CSV column names (during parsing and during entering column names), so that accidentally additional added spaces don't cause that the CSV column names do not match.

Thanks Chris, but in my CSV there are not white spaces...

But I'm right now debugging because I think the problem is due some fields, not with the mandatory field... I split my file, choosing a little bunch of fields and I can update my info. So I'm now testing with more fields trying to find a problematic field...

I post my research later :-)

@calbasi
It would be good to also check for extra spaces on the definition of the CSV sources, on the "Custom sources" tab. Especially check if there are extra spaces in the "Value" field of a CSV source. Extra spaces for "Label" do no matter.

"Custom sources" tab:

Check "Value" field of a CSV source:

Finally it was not a field match question... I think my issue was due to set "," instead of ";" as a CSV separator. In fact, you can set this parameter in 2 places, what I think could be confusing:

- at feed type settings
- at feed settings

I missed the second because I set up the first.