Help

The Community will be undergoing maintenance from Friday February 21 - Friday, February 28 and will be "read only" during this time. To learn more, check out our Announcements blog post.

Re: Creating a new record in externally sync'd table

82 0
cancel
Showing results for 
Search instead for 
Did you mean: 
Sean_Murphy1
7 - App Architect
7 - App Architect

So as we know, we can now enable the creation of records in tables that have been synced from other bases. It's great. Massive improvement. But can someone confirm for me whether we should be able to do the same using the Create Record action in Automations? Should spend my time doing a workaround or bug hunting? Because it isn't working for me.

thanks,

5 Replies 5
scp
4 - Data Explorer
4 - Data Explorer

I'm running into the same problem. I can create a new record in synced table manually, but the Create Record automation action insists it can't use that synced table because it is "synced from an external source."

can create new records in my synced table, but the automation is convinced it cannot.

omf
5 - Automation Enthusiast
5 - Automation Enthusiast

Having the same issue here, would love to know if there's something simple I'm missing or need to create a workaround.

huismax
4 - Data Explorer
4 - Data Explorer

Same issue here. I reckon it's a limitation - kinda ruins the usefulness of synced for me. So much for upgrading to business....

omf
5 - Automation Enthusiast
5 - Automation Enthusiast

I ended using Make to create the new record - annoying to have to go outside AT for something simple, but it did the trick ðŸ˜Š

laurenCTCL
6 - Interface Innovator
6 - Interface Innovator

Running into a similar thing where I'm getting an error when I try to use a synced table in a separate interface. I cannot toggle on "Add records through a form" or "Link/unlink records" because I get an error that users can't link/unlink existing records because this table is synced. I've got the syncs set up to allow for edits, but I guess it's a limitation, which is too bad. 

Screenshot 2025-02-18 at 11.45.42 AM.png