Forum Discussion
WarrenWillits
6 years agoQrew Trainee
OK, so I have run into another issue. When I try to create a Summary Field on my Parent Table (Aircraft table) from my Child Table (Location table), I am getting an error that states "you cannot create a summary field using a relationship where the reference field is a lookup field". The issue is that the foreign key in my Child Table (Location table) is set up as a look-up from the Parent Table (Aircraft table) so that the user doesn't have to remember the detailed Aircraft codes when inputting a Location. Is there any way around this or do I have to create a new input that requires the user to manually type in the Aircraft code every time they input the Location data?
QuickBaseCoachD
6 years agoQrew Captain
Warren, can you describe the relationship between Aircraft and Locations? What is the Key field of Aircraft? Is it a simple relationships where 1 Aircraft has many Locations?
But if you have a legitimate reason for the setup you have, then the solution will be to have a mirror field which is maintained which has a duplicate of the related Aircraft field, so that it is not a lookup field.
Then typically I set up a save table to table copy to copy the locations table into itself merging on record ID#, and updating that mirror field.
Then I have an Automation fire to run that saved import whenever locations are added or edited and the lookup field does not match the scalar mirror field.
But if you have a legitimate reason for the setup you have, then the solution will be to have a mirror field which is maintained which has a duplicate of the related Aircraft field, so that it is not a lookup field.
Then typically I set up a save table to table copy to copy the locations table into itself merging on record ID#, and updating that mirror field.
Then I have an Automation fire to run that saved import whenever locations are added or edited and the lookup field does not match the scalar mirror field.