Some modules, such as noderefcreate, can reference another node and create one if it doesn't exist already. This is usually done by typing text into an autocomplete field that checks for matches against existing nodes, and if none found, the new node is created.

I'd like a rule (or rules) that allow me to redirect the user to that second new node as they submit the first, passing one or more fields' data to the referenced node NOT just to the title field as already done by noderefcreate.

Use case: I have an event that takes place at a location ("venue"). Many locations are already entered as nodes, but this one isn't - I learn this by typing the venue name into an autocomplete that checks it against others already in the system. So a new Location node is created (by noderefcreate) and the venue text is used as the title for that new Location node, but Rules takes the user to the edit form for the new Location upon submitting the Event and places that text in the Location:Name field, not the title field of the new Location.

Comments

itangalo’s picture

itangalo commented
Assigned: Unassigned » itangalo

This seems like a worthy second component in Rules Bonus Pack for D7. Challenge accepted!
I will try to make the action work regardless of which entity type you want to copy field values between -- not only node to node.

itangalo’s picture

itangalo commented

Question:

In the Drupal 6 version there are two different actions that potentially could be used for this: One that (a) copies values from all selected fields to another node/entity, presuming that it has the same fields, and another that (b) copies the content of one selected field to another field of the same type.

Which of these use cases would you find most useful?

glottus’s picture

glottus commented

I'm only beginning to understand the nuances of entities now, and I guess that in my use case scenario, the transfer of information from one content type to a new content type (assuming they share the same fields) is the more useful function.

My potential need is more about migrating content into smaller, but related containers, and in this case it is a separate content type. I have a bunch of events with venues fields describing locations that many events have in common (a typical scenario, I imagine), and I'm thinking about how much more functionality the site could have if I could consolidate and reuse those fields in their own content type - one that is in essence completely different than the original content type.

Thanks for your work on this!

summit’s picture

summit commented

Subscribing, greetings, Martijn

marcoscano’s picture

marcoscano
Primary language Portuguese, Brazil
Location Barcelona, Spain
commented

subscribe

Jboo’s picture

Jboo commented

Hi,

Has this been integrated into this module yet? I'm just trying to find a way of passing field values to new nodes using rules as this seems like what I need.

itangalo’s picture

itangalo commented

No, this is not added to the module, and I will unfortunately not be able to add it in a forseeable future.

Rules Bonus Pack is looking for a new lead maintainer. Anyone interested?