Connected Table data update workflow question
I've built a customer success app that pulls Client and Contact data from the Main app from Headquarters via connected tables. The question - how do my users signal or flag out of date information wit...
Forum Discussion
Greetings - once again, thank you for your continued help. Here's what I'm realizing - my users need to have control over the Contacts table in their app in order to thrive in the system. They don't have permission to make changes in the main app, but should be able to make additions or corrections in ours.
I'd love to use the Contact Sync table as a data hose that pours the contacts into a new bucket we have control over. That way I can hide the Contact Sync table from end users and only show them the blended table of "imported" and corrected data.
The goal - 1 completely accurate list of contacts that our team uses and manages. I don't want users to deal with 2 lists (Contact Sync table and New Contact table), nor do I want them to have to email a new user to the admin of the Main app, wait for them to enter it in and have it sync daily back to our app. They just wont adopt that type of workflow.
Still not sure if I'm explaining myself clearly enough...
I'd love to use the Contact Sync table as a data hose that pours the contacts into a new bucket we have control over. That way I can hide the Contact Sync table from end users and only show them the blended table of "imported" and corrected data.
The goal - 1 completely accurate list of contacts that our team uses and manages. I don't want users to deal with 2 lists (Contact Sync table and New Contact table), nor do I want them to have to email a new user to the admin of the Main app, wait for them to enter it in and have it sync daily back to our app. They just wont adopt that type of workflow.
Still not sure if I'm explaining myself clearly enough...