When I have multiple people in a specific business and just want to duplicate one record and just replace the name I copy the original record by; Records>duplicate record.
Not all of the information flows to the new record - do not know why -
Probably those empty fields are in another (related) table ??
What kind of data is in the fields that are not 'flowing'?
Are they calculations? Are they drawing data from a related record based on a record id?
Are any fields set to auto-enter data?
Are the same fields that are not 'flowing' consistently the same fields?
More information would be good.
The fields are text, they are phone numbers
They are stored in a related table and the calculation is to separate the area code from the rest of the number and produce a format as follows; xxx-xxx-xxxx
They are drawn from a database of phone numbers that is connected to the base record by a contactID
The fields are not auto- enter
Yes the fields that are not flowing are consistently the same fields
Thank you for your response
OK. So you are showing data from a related table - via a portal or just placing the related child record on to your layout?
Check that the contactID that you are using to draw this information is actually being duplicated as well - is it blank? Is it an id that does NOT exist in your phone number database, i.e. check if the id field is actually being populated by an auto-enter on record creation. Some where in there I think is the problem
Thanks for responding!! You made a light bulb go off in the old brain - when I duplicate the record the new record has a new contact # so the phone number information that is linked by the contact id is no longer applicable because we now have a new contact id.
Now I have to figure that out - but at least now I know why.
434 973-7018 - work
434-974-6191 - fax
4785 Burnley Station Lane
Barboursville, VA 22923
Glad to help. It is really important that an id on a 'base' record (generally called a 'parent' record) is always unique and that no other record in that table shares it. Even if your parent record may have the same phone number contact as another parent record, you should always create a new record in the related phone record table (generally called the 'child' record) and use the new parent record id to link that new child record to the parent record
At some stage, the parent record's phone numbers will change and you will need to change the child record accordingly.
It can be tricky to get your head around the way relationships work but it's one of the really important things to learn when you're building databases. This principle applies to all databases, not just FileMaker.
Good luck and have fun! Once you start doing this stuff you're hooked for life!
Retrieving data ...