Forum Discussion
IvanWeiss
6 years agoQrew Captain
Mark, based on that it sounds like sync table is the way to go but a few questions:
Thanks! To your point in this case the table rarely changes, even synchronizing once a day is plenty.
------------------------------
Ivan Weiss
------------------------------
- Does the schema sync as well or do I need to remember to make any changes in both places to the table design?
- You mentioned it syncs text... If the user is in both apps will it "recognize" that or since it goes to text are we losing all of the functionality of that user key field?
- If I am an admin and a user any reason not to use my username as the sync user?
Thanks! To your point in this case the table rarely changes, even synchronizing once a day is plenty.
------------------------------
Ivan Weiss
------------------------------
AustinK
6 years agoQrew Commander
You may need to convert your text-user back into a real user with a formula. This is what has caused us to go other directions than sync tables for certain things, like where the user is a key field. We ran into a large issue doing this. It ended up not being able to sync the table properly though and I want to say it was because of nicknames in Quick Base. When a user sets that in user preferences AFTER your have already had the sync table going the key field for that user is suddenly different and wrong as it switches from their email/user to be the nickname. So your first record for them does not get updated and now you have a duplicate.
I believe we have gone the way of Pipelines for doing that specific thing now and are actually looking into other solutions as well.
Other than that connected tables have worked wonderfully for us. Just be careful what you use for the key field. Hopefully I explained the issue I had well enough above or didn't miss any parts of it.
I believe we have gone the way of Pipelines for doing that specific thing now and are actually looking into other solutions as well.
Other than that connected tables have worked wonderfully for us. Just be careful what you use for the key field. Hopefully I explained the issue I had well enough above or didn't miss any parts of it.