summary field not working in cross app table to table relationship

Hi Dante,

For the cross application relationship do the users who aren't seeing the value have permissions to see that field in the child app? What you might want to do is make sure you have a role in the child app that is able to see the records on that table and then in the cross application section of the app permissions for the child app make sure to add the parent app in with the role that is able to see the values on that table and if this field relies on any other tables or fields within that app to make sure it also has permissions to those. It sounds like most likely it isn't seeing the values in the child table due to the parent app not having permissions set up for it. I hope this info is helpful. 

I actually tried setting it up on a table within the same app and it still is not working. I'll double check all of the permissions but I think they are set up correctly. I think it must have something to do with the field itself. I'm going to try copying the data from that field to a new one and see if I can get that to summarize instead. It's weird because I am using dozens of summary fields in another app and I have never run into this problem before..

I must be doing something fundamentally wrong. I just can't get it working. I created a new table specifically for this relationship. I can create a report in the table where the field is that works with no issues, but when I try to summarize that same field in the new table I get no data.

Hi Dante,

If you open up the Related field displayed in that relationship and look at the usage does the usage show it is the field that is on your forms you are viewing on and also does it show that values are filled in for that field? In the usage you can see an option that notes how many records have a value in this field under the field settings. Sometimes this happens with the field being used for the relationship and the field being filled in for a value have almost the exact same name but are slightly different and the wrong field gets used as the reference field. 

I checked the usage and it is looking at the right field but showing there are no records with data. I tried creating a new field with the same data, changed the relationship to reflect that and it still says there is no data. Could it possibly be the key field (which is the default)? That thing still confuses me.

Hi Dante,

If you are looking at the reference field that feeds the relationship and it is showing no data that means there isn't a selection made in the field that is used in the relationship. Do you have more then one relationship showing up to the same table or possible more then one field that are named similarly that could be causing confusion?

I think the reference field is the issue and this is where I get a bit lost. My other relationships use name as the related field. However, name is not selectable as a proxy reference field on this table. This table is also different in that is has the user selected where the other apps I am working with have a name field that does not list users. but has their names typed into a list (I don't know why, this was put together by a number of people over the last decade or so). So I need a reference field, ideally the user, but that does not appear to be an option.

Hi Dante,

I'm a bit confused by what you mean about the reference proxy field. So the proxy would be what you are using to make it so users can select the right record to relate to but wouldn't typically automatically relate records, usually that is just used to help users when they are selecting related records manually. The field that actually matches your records is the reference field, and in the image you displayed the match should be from Record ID# in the parent table to the Related NVG report in your child table, if that related NVG report field has no data that means someone needs to go in and relate all the records before any summary fields would work.

It is possible some of your other relationships have been set up to use formula reference fields or a reference field that gets updated via an import or had pre existing values, etc.  In this instance it might be a manual relationship. If you want to use a different field for your relationship that might already have data in it you want to make sure the field in the parent table and the field in the child table are the exact same type of data. So if one is a user and the other is text for example then they wouldn't be available as the reference field option since they do not match. I hope that information is helpful. 

If you are finding yourself stuck and would like some one on one help to look at it you can also submit a ticket to our Care team to have them help you with a screen share and walk through it with you if that would be helpful. You can submit a ticket to the Care team while signed into Quick Base by clicking on the ? question mark icon that appears in the upper right hand corner when signed into Quick Base or directly here.