Inconsistencia para valores de inicio (Initial Values)

[Cesar_Hernande1]

Inconsistent Start Values

I’m seeing an error, but I want to check if this isn’t happening to you:

I have a table called TICKETS with two columns: TICKET ID and CONSULTA URL

TICKET ID is the key, where the initial value is UNIQUEID().

CONSULTA URL should take the value of TICKET ID with the initial value [TICKET ID]

The problem is: when the form view is opened, a TICKET ID, for example 49db8fb5, was created, the CONSULTA URL column should show the same value, but instead it shows a different one, like fa582275.

I’ve tried [TICKET ID] and [_THISROW].[TICKET ID] and the result is the same, with the same error.

This is the first time I’ve seen this error.
(Sorry if my English isn’t good.)

[Steve]

How does the user get to the form view?

[Cesar_Hernande1]

Hi Steve, I have a table view directly from the TICKETS table, and from the Add action button in the default form view.

What I’m checking in my previous rows is that this issue occurred on August 12th.

I’ve tested two other apps that use the same table to rule out column configuration issues, but I’m having the same problem.

I created a virtual column named ID TICKET VIRTUAL with the formula [ID TICKETS], and it displays correctly.

[Steve]

That looks like a bug with AppSheet itself. Please contact Support.

[Cesar_Hernande1]

Update: Testing with technical support has identified the issue: Expressing the initial value in more than one column is causing this incorrect behavior. That is, if more than one column has the value of that column [TICKET ID] as its initial value, it appears to recalculate the value using the UNIQUEID() function.

I’ve been told that they’re escalating the issue to their specialist team.

Thanks Steve

[Suvrutt_Gurjar]

If I may join the discussion, I share my observation. I believe observed behavior is linked to

1. The difference between saving a computed value v/s saving the expression from the column being copied from to the column being copied to.
2. probably linked to new record form view computation.

Please look at the following scenario. In the table “orders” the [Order ID] column is being copied to [Order_Routing] column as the screenshots below show.

[Order ID] has an initial value of UNIQUEID() as shown below

The column [Order_Routing] has an initial value of [Order ID] as the screenshot below shows

When the new record is created in the form view, as we can see , the values of [Order ID] and [Order_Routing] are different.

I have enabled reset on edit on the [Order_Routing] column.

When a saved record is edited, the [Order ID] is now properly copied to the [Order_Routing] column as the following screenshot shows.

So the testing shows that the new record considers the underlying expression but once record is saved the values is considered.

[sricse]

Hi Cesar, thanks for the update

Did they give you any additional response or solution from the specialist team? I’m experiencing the same issue in one of my apps. It’s strange because it used to work fine, and only after opening the app again after a few days the same problem started to show up.

[Adam-google]

Thanks for bringing it to our attention. It looks like a change from a few weeks ago affected the internal accounting of whether a given column had already been computed and shouldn’t be computed again. In some cases this can cause the same column to be recomputed more than once during form initialization, which for things like UNIQUEID would produce different values. A fix should be coming within the next few days.

[Cesar_Hernande1]

Thanks for the reply. I know it’s sometimes difficult to explain these issues as a user, but the support team definitely needs to improve their skills. I hope the constructive criticism helps you understand us.

[Cesar_Hernande1]

I ended up giving up, my friend. I sent them several videos as detailed as possible, but they made me repeat the same information because they “couldn’t replicate the behavior.”

[Steve]

Front-line support has not had any significant technical skill since Google acquired AppSheet.

[Adam-google]

A fix has been released, please let me know if you continue to see this happening.