|
I have written interfaces for a few Office APIs (email, SMTP, OneDrive).
Not Calendar yet, though (but I did for Google Calendar) as I haven't used
it personally or had requests for it.
You do need application permissions and OAuth 2.0 flow, which really is the
most challenging part, especially since microsoft requires a callback for
the initial OAuth authentication. (this can be skirted with a few tricks,
though).
My GreenTools for Microsoft Apps (G4MS) now uses the Graph APIs for
everything as well, so creating a calendar hook wouldn't be terrible. I
believe you could even use the G4MS base for OAuth 2.0 like I have set up
for my Google API package as well. I could easily create a simple calendar
package if you were interested with some basic functions.
Bradley V. Stone
www.bvstools.com
GreenTools for PayPal <https://www.bvstools.com/g4pp.html>: Easily send
PayPal invoices from your IBM i applications using RPG ILE! Process
refunds, get account balances and more!
On Tue, Apr 21, 2020 at 3:31 PM Bruce Vining <bruce.vining@xxxxxxxxx>
wrote:
I have the need to create and maintain cloud based Outlook calendars fromhttps://docs.microsoft.com/en-us/graph/api/resources/calendar?view=graph-rest-1.0
the i. The various calendar APIs (
)jobs)
seem sufficient but I do have questions on configuration and hope someone
out there has been down this path before.
First some background. Various dates and times are maintained on the i
related to the progress of orders. Some of these dates and times
correspond to meetings that need to be held involving several individuals
(who will vary based on the specific order). All of these individuals do
use Office 365/Outlook calendar and currently operators on the i must
manually maintain these calendar entries whenever the date and/or time of
the meeting changes back in the i. What I want to do is capture the
database changes and basically feed them through a *DTAQ to a job (or
that are using the Graph APIs to eliminate the manual approach currentlyanything
being used. So far so good, all of the *DTAQ entries are getting there
just fine. Now it’s time for the Microsoft Graph configuration work…
In reviewing the Graph documentation it appears that I want to use is
application permissions. Has anyone used such an approach? If so, any
advice/examples/warnings to share? The company here has never set
up for application permissions, I certainly never have, and I’m nothttps://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-configure-app-access-web-apis
authorized to do any “playing around” on the Microsoft side so I need to
get the configuration “right” the first time. There are many sites (
beingmy
one) that talk about setting up application permissions but I’m concerned
that my use of terminology doesn’t exactly fit with Microsoft use of
terminology, and there’s way too many warnings in the various sites for
comfort (given my general feeling that I’m missing “something” due tothese
terminology/conceptual differences).I’m
Any guidance from those who have been here before?
Thanks,
Bruce
PS – I’m confident that using the Graph APIs will be “educational” and
comfortable with that. I just want to make sure I’m not going down a badgetting
path in getting the two systems to talk with each other. That is,
the basic networking configurations in place.list
--
Thanks and Regards,
Bruce
931-505-1915
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.