Forum Discussion
QuickBaseCoachD
8 years agoQrew Captain
Mark,
I suspect if there�s a problem in the design of the relationships in your application.
The reason I say that is that I�m sure in fact one site as many projects going on at one time.
So that means that you will have a list of sites for example a bunch of building addresses and they will have many project site assignments.
So in fact what you were importing are not sites but project site assignments.
In order to relate those records then you will need to know the value for related site and related project.
So that means you either need to know the record ID of those two records when you do the import, or else the key field of those records will be have to be changed to something that you could know when advance when you did the import.
For example some kind of site code that makes sense to you and some kind of project code that makes sense to you that the Excel sheet would hence know when you do the import.
I suspect if there�s a problem in the design of the relationships in your application.
The reason I say that is that I�m sure in fact one site as many projects going on at one time.
So that means that you will have a list of sites for example a bunch of building addresses and they will have many project site assignments.
So in fact what you were importing are not sites but project site assignments.
In order to relate those records then you will need to know the value for related site and related project.
So that means you either need to know the record ID of those two records when you do the import, or else the key field of those records will be have to be changed to something that you could know when advance when you did the import.
For example some kind of site code that makes sense to you and some kind of project code that makes sense to you that the Excel sheet would hence know when you do the import.