Update/Overwrite contents by CSV

Created on 2 January 2018, almost 7 years ago
Updated 19 January 2023, almost 2 years ago

The present version does not handle any options on updating or overwriting existing nodes.
To be able to do this it is also needed an input of an index-key.
So my request is:
- be able to set which column that is a unique key.
- checkbox: If the node exists updated it. Not checked, the node is been overwritten.

Feature request
Status

Fixed

Version

1.0

Component

Miscellaneous

Created by

🇸🇪Sweden chrotto

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇮🇳India yamzalal

    @darshan7karia & @lashabp While I am able to import new content, using 8.x-1.15 version but not able to update the existing content/node even if I have "nid" column. Should I have to apply the patch or need to use dev version?

  • 🇮🇳India arunkumark Coimbatore

    @mohanrajthangarasu
    I too faced the same issue with the Drupal 10 core version. As per my initial debugging the First column not considering on the import.

  • 🇮🇳India harishpatel86

    Hi @kurinjiselvan v,

    It would be helpful if you could create a patch to update the node using the title, or any other unique key from the CSV instead of the node ID.

  • 🇮🇳India harishpatel86

    Hi @Neyret_Mathieu,

    A patch has been created for updating the content of node type entities. Please see the attached screenshot and patch.

  • First commit to issue fork.
  • @mehdib4 opened merge request.
  • 🇨🇳China wqmeng

    Update the patch to support both node and taxonomy entity.
    Thanks

  • 🇨🇦Canada rustyco

    Whitespace in patch

  • 🇩🇰Denmark ressa Copenhagen

    I am not sure this issue was fixed in the ideal way, since if you are using nid, you need to keep track of which ones are already used ...

    The patch in #21 works great, using for example "title" as unique key, thanks @harishpatel86.

    There's a related issue, which I'm adding.

Production build 0.71.5 2024