Re: Virtual Column Results Not Consistent

Ed_Cottrell · 10-21-2024 04:59 PM

Hi there,

Today I have had a payroll client alert me that my app is providing incorrect calculated results. Not good! I have investigated and found that each time I sync the app, it is providing different results for various VCs. This has not happened before / is not a new system.

Has something changed recently (in the last two weeks) at AppSheet that has changed how/when VCs are calculated?

I turned OFF Delta Sync as I thought this might be causing the issue. The issue is still there, in fact the results differ on every sync, so the VCs are re-calculating (on sync) but not consistently. I also tried in a incognito window to ensure I wasn't getting cached results.

Please help, urgent issue.

Thanks.

fern

Same Problem here, with virtual columns

@Steve could you help us solve this problem sir T^T

Nickthodsapol

Me too! , Same Problem

Marko_Nesic

Same problem!

dawa_sherpa

same problem also for me

lukezysong

I have the same issue occurs. Could anyone please check and fix the issue?

BXtra

same problem

Pariya_Meeros

Same problem!

Ed_Cottrell

Wow lot's a people saying same problem.

I'm interested to know - is this a new issue for you all too? It's just started for me in one of my apps (that I've noticed), sometime in the last two weeks.

I believe there has been changes made as to how AppSheet is calculating VCs on the Server (upon full sync) as compared to on the user Device (upon edit of the row)... As for me, if I manually edit the row (e.g. update a timestamp column, or any column) it calculates the VCs correctly on the device, but then shortly afterward the VCs "re-calculate" to something erroneous (I think based on the Server sending changes out to the device, not sure)..

Please help, @Aleksi @AleksiAlkio @Steve

dawa_sherpa

VC calculation randomness bug since 12 hours for me. This is a SERIOUS issue for my users who rely on correct calculations for realtime product movement on production floor.

AleksiAlkio

Let me find out details for this, but it sounds a bug.

Ed_Cottrell

Thanks Aleksi - I didn't see this post until after my below post sorry..

Ed_Cottrell

I have sent a support request - i'll post back here if I have any luck there!

AleksiAlkio

Few questions?

#1 - What option have you selected with the Settings > Legacy > Blank value comparison mode?

#2 - When you open the record, is the calculated value then correct?

#3 - When you save the record, is it always changing the value after the sync is completed?

#4 - Does it change the value every time you sync the app?

fern

1. Consistent mode

2. When I add a new record, the value is calculated correctly only a row that related but others are so random.

3. yes, including the correct value that was added in step 2

4. yes it does

Nickthodsapol

Same condition

fern

1. Consistent mode
2. When I add a new record, the value is calculated correctly. Only that
row that related but others are so random.
3. yes, including the correct value that was added in step 2
4. yes

--
Disclaimer: DEMETER ICT COMPANY LIMITEDInformation in this message is
confidential. It is intended solely for the person or the entity to whom it
is addressed. If you are not the intended recipient, you are not to
disseminate, distribute or copy this communication. Please notify the
sender and delete the message and any other record of it from your system
immediately.

Steve

FYI all, I don't work for Google and have no channel to contact them outside of the same support everyone has access to. Your best bet is to contact Support yourself.

JpChapron

probably the same problem here !! see : https://www.googlecloudcommunity.com/gc/AppSheet-Q-A/MIN-and-MAX-ref-rows-are-displaying-incorrect-d...

JpChapron

thanks Steve, I'll look into it

Jonathon

Bumping this thread, experiencing major issues with virtual reference columns calculating incorrectly.

wabrian

We believe we have identified the fix and have rolled back yesterdays deployment.
Please let us know if you are continuing to experience issues

Mcampioto

It’s working for my all projects. Please don’t make that change again, because it interrupted a lot of processes in my company.

Mcampioto

The problem has returned. Please fix it again. I'm having serious problems with this in my projects.

wabrian

Unfortunately we broke things briefly again yesterday, but quickly reverted the change.
We apologize for this inconvenience and will try to ensure we do not do so again