I am using XPATH node processor to parse XML feeds and it works fine. However when a XML feed contains the same data it goes ahead and creates new additional nodes. I want the old one matching to be overwritten with the new one.

So I tried to check a SOURCE / TARGET as UNIQUE TARGET in the MAPPINGS. However the checkbox is completely missing and I cannot assign a target element as unique to avoid duplicate nodes.

This is mentioned in this thread also http://drupal.org/node/991386 but looks like issue has not been fixed. Please help.

Comments

shrop’s picture

shrop commented

I think this may be partially fixed in http://drupal.org/node/1206042. See the commit here: http://drupalcode.org/project/feeds.git/commitdiff/314921ef5007d59900741....

Using the 7.x-2.x-dev version gives me a checkbox for the title field in the RSS importer. The one question I have is should I have checkboxes for all of the mappings? I am only seeing the checkbox for unique target for the title field, but I do have other fields in my use case.

Any insight will be appreciated.

Thanks!

franz’s picture

franz
any
Location Montréal
commented
Category: bug » feature
Priority: Critical » Normal

Those checkboxes are only availabe for some targets, such as GUID.

RollWhisTler’s picture

RollWhisTler commented
Version: 7.x-2.0-alpha4 » 7.x-2.x-dev

And why is that you say shrop?

Why number and text cck fields cannot by marked as unique? sounds like a huge limitation to me... not really complaining, great job here, but i don't understand this limitation.

Thanks.

oceanos’s picture

oceanos commented

I have the same problem. I want to import (and update) nodes automatically. In the data source, each item has a unique ID (not a GUID) which I store in a CCK text field and which I want to use as unique target in order to determine if an item already exists or not. This should really be possible!

Mapping the source's unique ID to the feeds item GUID does not work (because of the format validation). So I have to map the unique ID to the title field - the only field I can select as unique target. Very clumsy.

oceanos’s picture

oceanos commented

Sorry, I was wrong. Populating the GUID field with any text value is possible - thus the unique ID from my data source can be mapped to it. For some reason, this didn't work the first time.

twistor’s picture

twistor commented
Status: Active » Closed (duplicate)

#661606: Support unique targets in mappers is where this feature is being developed.