Currently the Feeds module will not update an existing target node's multi-value fields by adding a value to the field.
Use case:
You import some nodes using feeds with a guid for each node. You then want to import another dataset, which has the same node guids, with some new values for a target multi-value field. You want your new feed pass to update existing nodes and add values from the new dataset as additional values on your multi-value field.
Currently feeds will overwrite all old values in the target field with new values from the new dataset. You don't want that! You want the option to append values from the new dataset to the existing values already in your target field.
If anyone knows tricks to achieve this, please speak up.
Comments
Comment #1
sonicthoughts CreditAttribution: sonicthoughts commented+1
Comment #2
tuccio CreditAttribution: tuccio commentedWhat I am doing is first exporting the current values using Views data export and then updating the csv file with whatever new values, and finally importing the new file. I guess the entire process can be automated with some scripting.
Comment #3
aelling CreditAttribution: aelling commentedIs there any update on this or workarounds people have implemented?
Comment #4
twistor CreditAttribution: twistor commentedThis would be an interesting exercise for a contrib module, but Feeds isn't going to support this workflow.
Comment #5
DevDaveUK CreditAttribution: DevDaveUK commentedAnyone found a module that could help with this yet?
Comment #6
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedSee also:
#2059995: Where to access the original value of the entity field to be imported
#2273299: How to retain existing values and append new values in hook_feeds_set_target
#1871970: Getting all the values to the same field from different lines of CSV
#2490840: Multiple records in one import overwrite each other
#2581611: Adding field items (instead of replacing) on update of existing nodes
Comment #7
sitewits CreditAttribution: sitewits commentedTry the workaround: https://www.drupal.org/node/1871970#comment-10867952