I'm finding that "Replace Field Contents", when chosen based on a field on a layout that is actually a related record, does not seem able to create related records.

I'm trying to populate a Join table and it would seem that the easiest way to do this would be to (A) find all records without children, (: Replace Field Contents with the key field in the related table (which should create all the child records and populate them with the right key field).

When I do this, I get the "Replacing field contents" dialog box, but nothing happens.

I can do a work-around with a looping script using "Set Field Contents" and this works fine, but seems less elegant to me.

Anyone else found a way to bulk-create child records without a looping script?

Followup: It appears that the behavior of "Replace Field Contents" is such that if the related records don't exist, they will not be created. I suppose one could argue this is a feature, but it seems more like a bug to me...

Replace Field Contents does just what it says. The name implies that the field already exists. What you want to do is "Import". That is the step that creates records.

[color:"blue"] Hi Fenton,

I was going to respond with a similar answer to what you gave in your first two sentences. However, I'm always relectent to give an answers as it would apply to earlier versions than v7.

[color:"blue"]

Hi xochi,

To add a little to what Fenton said.

In the Import Dialog Box, there is an option to update existing records, and add new records. Maybe that is the "Replace" you were looking for?

Lee

"... populate a Join table and it would seem that the easiest way to do this would be to (A) find all records without children, (: Replace Field Contents with the key field in the related table (which should create all the child records and populate them with the right key field)."

Make sure your relationship has "Allow Creation of Related" then simply set a related field (using Set Field [Related::whatever field ] with whatever you wish. If a matching (on ID) record doesn't exist, it will automatically be created and the related ID populated when you set a non-ID related field.