![]() Now what I DID turn my focus to and am still pursuing is an elegant integration of python code into my data crunch and automation workflow. From my limited foray into the area, what I sensed is that the JavaScript API is more for those web developers who came from using JavaScript solutions and are now looking to integrate with Office 365 more tightly not so much VBA coders looking to jump into web solutions for Excel (which would be my interest) I deal a lot with workflow automation and data wrangling/analysis and it was (for me) recreating the wheel for things I had well tested solutions for already. Reason being that it just seemed very redundant for my needs and what I needed to accomplish. I began learning how to translate my VBA modules to this new framework early last year, but sidelined it after a few weeks. As an example, a lot of my work involves querying databases, which I don't think there's a way to do in the API at the moment. I'm certain some simple VBA work could be replaced with the API right now, but much of it could not. And there's also a subreddit on it at r/OfficeJs (disclosure: I'm a mod there.) Both communities are kind of small and dead at the moment. There's a community on StackOverflow to ask questions. People out there are definitely using it and developing addins. But they continue working on the object model and adding new features. The API is still limited compared to VBA and, AFAIK, will never achieve full parity. Reasons like that are (imo) the intent of the API and the main reason to use it. people who traditionally work with web technologies, perhaps people in IT who don't know and aren't interested in learning VBA, etc.) VBA only works on the PC, and to a lesser degree on the mac for example which makes it very limited.īring in a large amount of potential developers into Office to develop their own addins and expand the ecosystem (e.g. In the future, perhaps something like this will be integrated in something like SharePoint. and have them work in all of these environments. You can have solutions in Excel for desktop, Excel for Mac, Excel for the web, iPad, etc. The neat thing about the API is that you'll be able to take advantage of powerful and well-developed javascript frameworks that are already established (Angular, React, etc.) Imo, the intent of the API is:Įnable cross-platform solutions in different versions of Office. I have used it a bit with ScriptLab and javascript / typescript.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |