Skip to main content

Updating a Synced Table from an automation

  • March 7, 2024
  • 6 replies
  • 181 views
P
Forum|alt.badge.img+5
  • pdxbug
  • Participating Frequently
  • 12 replies

I am attempting to update multiple records in a single automation in a Synced Table. I am unable to update Synced Records from RunScript as I get 'Error: Edits to synced field "Stories Automation" (fldxxxxxx) are not allowed from this origin'.

I know I can use the native update record functions to update a single record, but if I put the items into a list attempt to repeat group I am given the error `Synced fields can only be updated in the last action in an automation. Move this action to the end of the automation, or remove the synced field.`

What are the options? I'm considering just using an API call to make the changes directly to the original table but am hoping I can do them locally.

 

6 replies

D
Forum|alt.badge.img+2
  • David_Schwartz1
  • New Participant
  • 3 replies
  • April 22, 2024

I'm getting the same error, in a somewhat different situation.  This is the error:

"Edits to synced field \\"Artwork Requested\\" (fldUxxxxxxx) are not allowed from this origin"

In my case I'm attempting to update the field in the Synced table via the API.

 

S
Forum|alt.badge.img+4
  • Saulo_Soares
  • New Participant
  • 2 replies
  • May 8, 2024

Same problem here as David Schwartz. @David_Schwartz1 

Have you found any workarounds yet?

MikeD
Forum|alt.badge.img+6
  • MikeD
  • New Participant
  • 3 replies
  • May 8, 2024

Same here ... have bumped into both these errors today (first one in AirTable, second one in MAKE.com)

But as it stands I am not able to achieve my goal ... is this a bug ?

P
Forum|alt.badge.img+5
  • pdxbug
  • Author
  • Participating Frequently
  • 12 replies
  • May 8, 2024

Currently the only solution I have is to create a new field in the synced base, make changes to that field that is then synced into the original base and updates via automation on the original base. NOT ideal. 

MikeD
Forum|alt.badge.img+6
  • MikeD
  • New Participant
  • 3 replies
  • May 22, 2024

Anyone know if there is an update on this? Proposed workarounds are clever, but cumbersome - feels like a bug to me

dedigital
Forum|alt.badge.img+2
  • dedigital
  • New Participant
  • 1 reply
  • June 27, 2024

Running into the same issue here.  I'm trying to update a synced field via API and getting the same error message.  Definitely not ideal to have to create the field on the synced table either..


Terms & ConditionsAccessibility statement