Support for embedding Office Add-In webextentions #2180
Labels
No Label
DBF
Dates
Defined Names
Features
Formula
HTML
Images
Infrastructure
Integration
International
ODS
Operations
Performance
PivotTables
Pro
Protection
Read Bug
SSF
SYLK
Style
Write Bug
good first issue
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sheetjs/sheetjs#2180
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Microsoft has provided documentation on how this is done, though by no means approachable without some abstraction.
It seems really promising, one might be able to serialize their JavaScript that they used to generate the data, include it in a dynamically generated add-in, and create a spreadsheet that can recreate all the data manipulation that happened on the site.
I'm starting to see why MS is pushing the web add-ins so hard.
If you can make and share a sample export, we can take a closer look.
Note that many of these newer features are explicitly designed to create lock-in with Microsoft services, and file exports may not have the full details. For example, Microsoft Forms is serialized as a UUID in a worksheet. That's it, a glorified key that the Microsoft servers understand. We can take a closer look at a sample export and see what metadata is stored in the file.
Certainly: GoogleDrive Link
Yes, I would concur that many of the microsoft excel features seem to only obfuscate things (It is very much the case with MS Project which is still a completely closed spec).
However both the file archive and the documentation seem to be very well designed to make this sort of thing easy. From the archive, it just seems to be the folder with the source files and manifest inserted in the workbook directory, and a reference to it added in the
[Content_Types].xml
. The documentation also has a step by step using their library; while the instructions use their C# library, they also provide an equivalent JavaScript one that should operate the same (so one could step through the code), though I think all the library is doing is the file and XML manipulation.