Table limitation

How many lookup fields do you have? At some point performance will be a problem in edit mode, because every field is executing a query to retrieve the initial set of options for the field. But there are no hard limits on number…

Can you be more specific in what is happening? And maybe post some pictures of your setup? Reference fields have lots of configuration options, and lots of ways the can go wrong…

Hi @Rob_Hatch ,

I have only 2 lookup field under property object which is related to accounts. But the state field is not showing in the skuid page. When I go to that specific property record (lightning page), the state has a value.

Are you sure in the model that the table is referencing you are pulling both the lookup field (eg. Lookup__c) as well as the lookup’s name (eg, Lookup__r.Name)? The lookup won’t display properly in a table without the name. I’m not sure about V2 but in V1 when adding fields to tables directly that are not yet in the model, it would not automatically grab the Name for you of a lookup that you select to add, you’d need to do that yourself (this is different from how it works when adding a field directly from the model’s field list).