Performance Impact of Reverse Reference Virtual Columns

Does the Virtual Columns containing Reverse Reference created when a Ref is made between tables have performance impact on app or lead to longer sync time. Since REF_ROWS is performing some SELECT() and my table has about 10 Virtual Columns containing REF_ROWS()

Hi @jyothis_m

Virtual columns for reference columns cannot be removed, so you better keep it :slightly_smiling_face:

No impact from my point of view, and far more efficient than usual SELECT() expression when it comes to use dereferenced expressions :slightly_smiling_face:

For reference:

Dereference expressions - AppSheet Help

3 Likes

This question has come up many, many times. Consider trying the community’s search feature.

2 Likes

Sorry for that. I did a quick search but didn’t see anything related to this. May be my search string was wrong.

Not your fault mate

  • You could have the direct string that’s the name of the post you’re looking for…
  • If you tried to search for it… the community won’t find it
3 Likes

Isn’t the REF_ROWS just another name for SELECT() ? Looks like appsheet just convert it into a SELECT()

I believe system generated reverse reference columns (REF_ROWS) do not cause a drag on the sync time. Please take a look at the explanation by none other than Praveen Seshadri ( @pravse ) in this regard in a related discussion thread. In fact I have bookmarked that post thread as it has valuable information on performance. Others may want to bookmark it as well.

Solved: Improving performance by getting rid of unnecessar… - Google Cloud Community