Forum Discussion
QuickBaseAdmi10 MarkShnier__You Howdy - does this approach still work to refresh connected tables on a cadence of more than 1 hr? Have one table which has 6+ small refreshes coming in per hour...yes API would be better long term....wondering if this still works since it sounds like QB is disabling the replicationID?
I was not aware they were to save the replication ID. But it's actually really interesting that the Community Forum likes this answer as using an unsupported technique.
I was not aware they were to save the replication ID. But it's actually really interesting that the Community Forum likes this answer as using an unsupported technique.
I do know a client acquaintance where they were forcing a refresh every five 5 minutes on a large table. They ended up getting into a huge fight with Quickbase as Quickbase said they were abusing the platform, so basically Quickbase told them that they're not allowed to do that.
- GeoffBarrenger2 days agoQrew Captain
Thanks MarkShnier__You - We're in a similar predicament - no reason to refresh a massive table many times. Another table does have very small imports throughout the hour, so we would need to refresh at least 8 items within a 60 minute period (ideally we would move to API but that's not possible at this time internally).
Ok will see what we can do here rather than have users manually click refresh...