Team Sharing of Custom Objects

Summary

  • Team Sharing can be used to share any kind of data including custom objects

The primary use case for TeamSharing is to allow different AdapTable instances to share AdapTable Objects, e.g. Layouts, Format Columns, etc.

However, it is also possible to share bespoke object structures and values.

Caution

  • AdapTable does not provide dedicated UI components for sharing Custom Objects
  • Each user should create their own UI components optimised for their specific use case

AdapTable is very flexible and unopinionated regarding the structure of the shared data, so anything can be Team Shared if required.

Deep Dive

Understanding Custom Team Sharing

handleCustomSharedEntityImport

() => void
Handles import of Custom Shared Entities
Team Sharing with Custom Objects
Fork
  • This example illustrates how Team Sharing can be used to share custom objects
  • Each user may increment/decrement their local value and choose to either:
    • push their local state value to the remote common state
    • import the remote state value and overwrite their local value

Expand to see how custom Team Sharing is handled

Try It Out
  1. As Alice increment the local value from 0 to 1
  2. Switch to Bob and note that his local value is still 0
  3. Switch back to Alice and now click "Push to Team Sharing"
  4. Switch back to Bob and note that his local value is still 0 but the next tab shows that Alice updated the value to 1
  5. Click 'Import Remote Value' and note that Bob now has a local value of 1 (same as Alice)
  6. Update the Local Value from 1 to 2 and then click "Push to Team Sharing"
  7. Switch back to Alice and note that while the local value 1, it says 2 is available which can be fetched by clicking "Import Remote Value"

Custom Objects Team Sharing

(Recorded with AdapTable v15.0)