BUG? Column & Inline Action Missing From View, Replaced with _RowNumber (and No Action)

One of my clients has seen this happen in two different apps today:
Screen Shot 2021-04-06 at 4.07.48 PM

Screen Shot 2021-04-06 at 4.07.38 PM

Several columns with inline actions in table views have been replaced with _RowNumber and no inline action.

Is anyone else seeing this?

4 Likes

Someone else reported this same issue in spanish

2 Likes

Escalated.

2 Likes

yo tengo un problema similar, tengo acciones que estan en vista de linea de columna, mi aplicacion funcionaba correctamente pero ahora las acciones no se muestran en la columna, el problema es que tengo a 17 personas trabajando con estas aplicaciones y todas no pueden capturar información por que debido a que las acciones no se muestran en la linea de columna toda la vista de la tabla cambio y es un caos!!!

2 Likes

I am also experiencing the same problem.

1 Like

Qick clarification — is this after opening the app in the editor? Or is this just in the browser/device with no change to the app in the editor?

Could one of you please share app name or file a support ticket so we can look into it? Thanks

1 Like

Actualyt, we have a support ticket to investigate, so looking at it now.

2 Likes

Could one of you please confirm … if you go back to an older version of the app definition (via Manage → Version history), does it work? Thanks

1 Like

ya lo hice a una versión anterior y no pasa nada

1 Like

No, we tried to go 6 previous versions and all of them are showing this change instead of the real one

1 Like

Thanks you @Stephanie_Estradariv for clarifying. Continuing to investigate. If you have the app name, please share so that we can look into it. if you’d ike to send it privately, please send to pravse@google.com (the app name will be something like myappname-163506). Also, please share any steps to reproduce the problem (eg: open view X, click on row Y, etc). Thanks

1 Like

yo tengo mas 5 aplicaciones y en todas presenta el mismo error el nombre de una de ellas es:

Usuario01–1561-1135272
nombre corto: Libre demo 01–1561

1 Like

So here is a description of the problem…

*) It only affects Set Column Value actions (eg: ColumnX = 5)
*) And only if this action has been explicitly attached to a different column (i.e. not to ColumnX but to something else)

Right now, our code is ignoring that information and assuming the action is always associated with ColumnX.

This problem was introduced because we are refactoring some of the code for actions in the system and didn’t adequately test for this case. We have a fix coming. Don’t have an ETA at the moment. Definitely will be in tomorrow’s deployment. We’re trying to get a sense of the severity of the impact — eg: if any of you are drastically affected and need an emergency deployment, please let us know.

Thanks

2 Likes

Yo tengo a 17 personas que no han podido trabajar
te explico:

La aplicación que usan para trabajar las acciones son indispensables ya que al presionar una accion captura pagos o creditos, entonces no han podido trabajar estan anotando todo en una libreta pero la aplicación no la han usando por que no es posible trabajar

1 Like

We have a fix for the problem and are kicking off a special deployment to release this. I expect this will happen within approximately 4 hours from now.

5 Likes

It rendered my app for invoice management impossible to use, as the affected actions covered up two vital columns (quantity supplied and unit cost).
I have had to hide those actions, one of which is needed to refresh the invoice line, others which drastically reduce keying time in an already laggy app (which is being looked into by Appsheet separately).

When you say there’s no ETA, but it will definitely be in tomorrow’s deployment, does that mean at most it will be 24 hours? And you will try to deploy sooner?

Hopefully we don’t get too many insufficient testing scenarios again… :crossed_fingers:

3 Likes

Hi @Josephine , yes the deployment process has been kicked off. It takes a few hours to finish though. I will notify this thread when it is complete.
If you edited the app in the interim, you will need to manually fix up the actions in question. Basically, the problem is:
*) the action is set ColumnX to some value
*) the action was explicitly associated with ColumnY in the action definition
*) the bug caused this to be overwritten and associated again with ColumnX

If you had not opened the app in the editor earlier today and tried to save it, make any changes, etc, then our deployment will just fix the problem. If on the other hand, you did make edits (as I imagine any of you who ran into trounle would have tried to do), then you have to do one of the following things:
a) use Manage → Versions to go back to an earlier version and restore it, or
b) go to the specific actions in question (Behavior → Actions) and explicitly set the column that it is attached to

Again, I do recognize this is a big mess and lots of disruption for you! This will cause us to flesh out our test suites to cover this case better.

2 Likes

Thanks for the detailed information Praveen,

We are having the same issue - I did lodge a support request and detailed a video of the testing.
However, I found the exact same thing you mentioned - only affecting the “set column value” actions.

We’ll get staff to hold off using the Apps for now to avoid confusion for them.
Please update ASAP here once you think we can look to test again, and bring back old versions if needed.

1 Like

Gracias

The deployment is mostly complete — many of the servers have received the update. If you refresh/sync your app, it should now avoid the bug. Basically, the bug description is:
*) the action is set ColumnX to some value
*) the action was explicitly associated with ColumnY in the action definition
*) the bug caused this to be overwritten and associated again with ColumnX

If you had not opened the app in the editor earlier today and tried to save it, make any changes, etc, then our deployment will just fix the problem. If on the other hand, you did make edits (as I imagine any of you who ran into trounle would have tried to do), then you have to do one of the following things:
a) use Manage → Versions to go back to an earlier version and restore it, or
b) go to the specific actions in question (Behavior → Actions) and explicitly set the column that it is attached to, and Save the change in the editor.

5 Likes