Computed virtual column of computed actual column in sheet

[Tom_automated]

I have a couple of manually computed columns in my Google sheet. Full Name and Address combining columns for first and last name & street, city, zip. When I regenerate the table, AppSheet adds 2 virtual columns _ComputedFullName and _ComputedAddress. Why exactly is it necessary for it to do this? Why can’t it just use the manually computed columns (computed in Google Sheets) instead? Is it an efficiency thing or what? I’m just curious, because I apparently like to poke things that I didn’t make.

[Steve]

You’re welcome to remove the _ComputedfFullName and _ComputedAddress virtual columns. They’re added merely as a convenience when AppSheet detects the apparent components. AppSheet does not look to see whether there already exists combined values.

[Tom_automated]

Okay. But it doesn’t prevent AppSheet from recreating the virtual columns again if I regenerate the table. So I’ll probably just ignore it.

[Steve]

You might test that. My recollection is AppSheet will only add those virtual columns the first time it discovers the components.

[Tom_automated]

I have, multiple times. Every time I regenerate the table, the _computed virtual columns get added.

[Koichi_Tsuji]

My understanding your table, upon loaded, there is no suitable column which stores unique value. So appsheet is wise enough to generate the computed id as virtual column

[Tom_automated]

I already have a UNIQUEID() column in the table.