Importing to a table with relationships
I?m hoping this isn?t going to be a ?I missed it in the documentation? post, I did have a good search around before posting! New to QB and I'm putting together a PM app, currently with 9 tables, th...
Forum Discussion
If you change the Key field of those two tables to be the Customer name and the Project name, then yes, you will be able to do the import without needing work out the [Record ID#]'s in advance.
Note that if you have a Key field set as the name and change the name even slightly, then the children will not longer be Attached to their Parent records.
That is why in most cases it is better to stick with [Record ID#] or perhaps a Customer number as opposed to a name. But if you need to be doing imports on an ongoing basis, there is there merit to changing the key field for those two tables.
To change the key field you go to the field list and check the checkbox beside the name field and select set Key field at the top. it will give you a couple of scary warnings, but will keep everything attached. Be sure to check the data entry on the child records to be sure that you can still properly select the Parent record. You may need to adjust the form slightly.
You may want to consider making a form rule to make the customer name and the project name non editable, if, respectively, those two parent tables have any children.
Note that if you have a Key field set as the name and change the name even slightly, then the children will not longer be Attached to their Parent records.
That is why in most cases it is better to stick with [Record ID#] or perhaps a Customer number as opposed to a name. But if you need to be doing imports on an ongoing basis, there is there merit to changing the key field for those two tables.
To change the key field you go to the field list and check the checkbox beside the name field and select set Key field at the top. it will give you a couple of scary warnings, but will keep everything attached. Be sure to check the data entry on the child records to be sure that you can still properly select the Parent record. You may need to adjust the form slightly.
You may want to consider making a form rule to make the customer name and the project name non editable, if, respectively, those two parent tables have any children.