Trying to sync one table to another (ERROR)

Using linked record fields is really by far the best option here. Syncing across tables with automations is a huge pain. Creating the initial copy is usually achievable but the real problem is keeping things in line.

To reduce your linked record issues, there are several settings at the field level and then even more when included in an interface to help prevent new record creation. I’d recommend building out an interface as you can disable new record creation but allow new record linking. 

Hello,

Sorry to bother but i ahve no idea how to do this. 

Do you have a link to a guide or something that you can send me please?

thanks you so much in advance and thanks for taking your time in replying!

OK thanks for the explanation, i will try tomorrow to see where it gets me. I have not tried interfaces yet.
hope you have a great day!

Does this look right?  If so I’ve set it up here for you to check out

It uses the principles ​@DisraeliGears01 mentioned about using a linked field + lookups to handle keeping things in sync, and the automation is used just to link the Documents to the new Policy

re: Whenever a record in Insurance Policies is created or updated, find the matching record in Insurance Documents where the Policy ID matches the Policy Number.

I’m curious as to the workflow of this bit.  The Document records are being created before the Policy record?  And we already know the Policy Numbers for those Documents before the Policy record gets created?

Good Morning,

Thank you for taking the time of trying to help me out with this issue.

Here is a breakdown on how its supposed to work:

An Insurance policy is created where they get a policy ID for each type of insurance. (Health, Dental, Vision, Life, etc...)

A Client can have many insurance policies at once.

For each Insurance policy they get a carrier.

Each carrier either requires documents to be signed or provides the documents for the policy.

I have two tables at the moment, one with the insurance policies and one with the documents.

What I want to do is for the insurance document tab to be updated every time an insurance policy is modified or created to be created on the other side so I can upload the documents for each policy.

I like what you shared with me and gave me an idea on how to do them differently. 

Im going to try and replicate it with the changes i need to do.

Thank you once more!

Thanks for the details! 

Hm yeah, from what it sounds like the workflow is for a Policy to be created first, and then when a Document gets created it needs to be linked to an existing Policy, is that right? 

If so, it seems like you wouldn’t need an automation?  During the creation process of the Document you’d be linking it to the correct Policy, and once that link’s established any changes you make to the Policy will reflect in the ‘Documents’ table via lookup fields

It sounds like you’ve figured out what you need though and I hope that goes smoothly!

Hello,

At the moment I'm still struggling because I need  that when the client uploads a document or i upload a document an new entry is created on the document tab as a new entry. Policies need many documents. I guess I will have to do it manually for each client for now.

From a pure database design perspective, that’s correct. Each document is different and thereby should have it’s own record in a Document’s table. This is why linked records model one-many relationships, as each policy can be linked to multiple documents.

If you’re just trying to keep track of uploaded documents, could you instead use an attachment field on the Policies table?

Conceptualizing from your prior post 3 days ago, I might imagine this structure instead as a 3 table base Client, Policies, Required Documents. You add John Smith as a client (with his address and whatever else). Then you attach policies to John Smith (car insurance, boat insurance, etc.). In those policies then you attach a required documents record, which is Nationwide Auto or Progressive Maritime. In that Required Documents table you include the provider and insurance type, along with an attachment field that includes blank versions of the required documents. Then in the Policies table you add a lookup field for the aforementioned attachment field, so they show up in the Policies table. Then you can add another attachment field called Completed Documents (or the like) where completed versions of the documents live (and if you want to be fancy you could add a formula that counts both those fields to display when there are outstanding documents). 

Hello,

Thank you so much for the guide I forgot to reply. Everything is working now, I create a prefill form that links to the documents table and auto attaches the client with automation on a checkbox. 

Thank you so much for everything!

Best, 
Mauricio Hernandez