For the desktop design and new mobile framework (preview), update behavior of action “Data: add a new row to another table by using values from this row”. if the Row ID is specified and exists in the table to which you are adding the row, an update will be performed. Previously the action was blocked. This fix is being rolled out gradually. It is currently deployed to 100% of free users.
Rollout changes
Item
Description
Bug
Update Google Maps to take into account the user locale when rendering the map. Specifically, the region from the browser locale is being passed to Google Maps rather than using the default. See also Localize the Map.
New: Deployed to100% of free users and 50% of paid users. Previous: Deployed to100% of free users and 25% of paid users.
Preview announcements
Preview feature releases enable you to try out new app features that are not yet fully supported. See Product launch stages.
No new preview features were released today.
In addition, the AppSheet preview program lets app creators try out new app features that are not yet fully supported. For more details and to opt-in, see AppSheet preview program.
Use “Data: add a new row” as an update when ID matches might simplify some setups. Nice change.
As we are in the “Data: add a new row” theme, I can’t see why “Data: add a new row to another table by using values from this row” cannot use inputs. It would simplify dozens of cases where you need to group a “set value to a temp field” with the “add new row”, which is ugly and prone to a race condition.
I have checked on this matter and have confirmed that it has been “basically” fixed.
Thank you very much!
However, we have confirmed that in “certain situations,” the problem here still exists, and we will explain it.
As it turns out, it occurs when a virtual column is set as a key in a parent table.
There is a parent table and child tables as shown in the figure below.
The child table refers to the parent table.
The key of the parent table is a virtual column ([vcPID]).
The first execution of the action will successfully add records to the parent table, but the second and subsequent overwrites will result in an error.
edit(Japan time 2025/6/11/18 19:00)
In the above post, I used the example of a parent table and a child table, but it does not matter whether the tables are related or not.The problem is that the key columns in the destination table are virtual columns.
