Is this possible? Does anyone know how this could be done?
Thanks!
I am not aware of a way to do that through SharePoint, but you can add the Coda app to Teams, and share docs and pages that way.
1 Like
Yeah, totally doable. Not easy, but I researched a design for this with another client - there’s daylight for making this work.
1 Like
can you enlighten us?
Sure.
I’ve thought about the Coda → Sharepoint challenge a fair bit and a few things have become obvious.
-
Making copies of anything is bad. Making proxies of anything that reference the “thing” is better. Why? Because subtle changes may have occurred recently and copying [again] has latency. Copies (like PDFs) have a habit of spreading through downloads. Before you know it, five copies of a PO exist and none are the latest.
-
Sharepoint objects can contain the actual content of a document if you make a PDF and upload it. This is problematic with Coda in an automated sense, whereas, it works fine manually. The question - do we want to force users to manually export a PDF from Coda for every purchase order document? Such a manual export breeds additional manual tasks like copying it to a network drive where automation can take over and finish the job.
-
Sharepoint is well capable of representing Coda documents by reference. This is to say - as PO documents are created, we automatically generate a proxy item in Sharepoint that references the original Coda document. I assume following a link from Sharepoint to Coda is an easy lift for the users.
-
A proxy-based representation in Sharepoint has many advantages -
-
More than just a link, the ability to create the Sharepoint object from inside Coda would allow us to add attributes like the status of the PO, who created it, what its for, etc. The metadata exposed along with a link back to the original document could be used in Sharepoint to search for documents that exist in Coda, etc.
-
Proxy objects could be updated as and when the metadata in Coda changes, sustaining a real-time essence of the information for each PO document. You could see in Sharepoint who and when a document was last edited.
-
Proxies could be primed, meaning that we could use the Coda API to generate all Sharepoint PO instances without forcing you to open every Coda PO document and click something to instantiate each one in Sharepoint.
-
Updates to Sharepoint could be contingent on other Coda-based data. For example, unless the status = (x), do not update Sharepoint.
A few more thoughts…
-
It’s possible to generate PDFs from Coda documents with the Admin API.
-
The Admin API also supports multiple formats, including HTML. So, it would be possible to instantiate a Coda document inside a Sharepoint object as an integrated part of the object.
-
It’s unclear at this time if a Pack could streamline the entire process making it a single button (or event-based) process that just happens automatically.
-
The Admin API also provides event auditing - a way to monitor activity in the Coda platform. For example, when a document is created in a certain folder, do something. This could be helpful in designing a reflection of Coda resources in Sharepoint.
1 Like