Expand email distribution list - outlook-addin

I need to expand (recursively) email distribution list in Outlook 365. Is it possible to achieve using REST API?
As far as I understand it can be done using EWS, but I'd like to avoid extra complexity of working with EWS SOAP messages in Javascript code.

Related

How to send a recurring event from Outlook to Google Calendar

I have some Outlook VBA code which executes when I add an event to my Outlook calendar. The code makes use of the google calendar API to send the event information to google. Google them updates my google calendar. I also have code which, when I delete an event from my Outlook calendar, will send a DELETE to google through the calendar API. Google then deletes the event from my google calendar. This code works perfectly.
Now I need to write the VBA code which will send recurring event data to google. Is there a simple way to send this information? Is there an online service that I can send information to and have an RRule string generated? Do I have to build the RRule string manually?
Thank you.
If you deal with Office365 account you may consider using the Graph API directly without involving client applications like Outlook. For the Exchange on-premise you may consider using Exchange Web Services, see Start using web services in Exchange for more information.
If you need to end up with a client-side solution you may consider creating a VSTO based add-in (COM add-in) which can sync everything with your system. See Walkthrough: Create your first VSTO Add-in for Outlook to get started quickly. VBA was not designed for distributing solutions on multiple machines.

How to execute a Query/access sharepoint list in MS Project?

I need to populate my resource list in MS Project from a Sharepoint list. The authentication method for sharepoint is the windows credential/company credentials.
I was thinking by SOAP or a query already saved (this will be better since I have the processing Power query). What is the best way to do this?
This can actually be pretty interesting depending on how much access your SharePoint farm admin folks allow you to have.
SOAP is fine probably. But I've always used REST to access a SP List through SP's API. I've used this site: https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints to great effect when creating and accessing lists from remote applications. Anything that can send an authenticated rest / generate a token with credentials should be able to get the LIST and even edit it.
One thing to remember among the many nuances of SP development is that list names are often different when accessing through SOAP or REST API points. You may need to figure out your own List naming conventions and any special character codes like underscore or spaces and their corresponding SP codes ((http://sharepoint.stackexchange.com/questions/787/finding-the-internal-name-and-display-name-for-a-list-column))
EDIT if you have power query, you can use the built in connect to sharepoint template in most Office Apps that feature PQ. That might be good, since it should allow you to save the credentials you have to get the SP without having to generate a token through SOAP or REST. But REST is my main experience here. I've used PQ in Excel to access SP list.

Freshdesk: Automating 'score' emails

Background: I have little coding experience (not API savvy) and would preferably use an automation tool for this but hope for some guidance in the best way to complete the task. '
We need to send a 'response' (number of emails sent by an agent) score at least twice a day to agents so they can gauge their efficiency. As an alternative we can build up a dashboard to enable easy viewing of this information.
Question: How do I go about sending emails to each agents gmail account with the number of responses completed on Freshdesk that day? Can this be done with a Zapier connection to googlesheets and then forming a googlescript? Would it be easier to set up a live dashboard displaying all agents scores and if so how would you recommend doing this?
Sending emails would be tough given that most email clients (gmail, outlook, ...) have stricter rules on what lands in inbox to avoid spamming.
But you can build a dashboard in Freshdesk to show this information. The sdk has default support for most things you'd need.
Here's a blog post of a sample dashbaord app in Freshdesk: https://medium.com/freshworks-developer-blog/building-a-full-page-app-on-freshdesk-5ce17524277f

Office JS Add-in API Compose appointment get contact

I'm searching in documentation how to get the list of contact of the Office account in the way to display it and let the user pick all phone numbers he need.
I assume is not possible during outlook appointment compose. But i would to be sure (Maybe i miss an important point in doc)
Thanks !
Currently the feature to get all contacts, you requested, is not a part of the product. We track Outlook add-in feature requests on our user-voice page. Please add your request there. Feature requests on user-voice are considered when we go through our planning process.
Meanwhile, you can achieve this by using REST API's.

Item ID’s given by Office JS object are different for Outlook App and web

We developed Outlook addin using the framework provided by Office JS.
We observed following differences in Item IDs in web and outlook app.
Please see the following ID's. "Separator is different". How we will identify the uniqueness of emails.
e.g.,
Web :AQMkAGI5MTEANDkzYi1mYTJlLTQwNDUtOGI1Ni00ODJmODc0N2M3NjIARgAAA5vnUELrbT5Mp3SvmLMR6MEHAP7qKD1uxMdCtoUAa/H6RZsAAAIBDAAAAP7qKD1uxMdCtoUAa/H6RZsAAAIXmAAAAA==
App :AQMkAGI5MTEANDkzYi1mYTJlLTQwNDUtOGI1Ni00ODJmODc0N2M3NjIARgAAA5vnUELrbT5Mp3SvmLMR6MEHAP7qKD1uxMdCtoUAa-H6RZsAAAIBDAAAAP7qKD1uxMdCtoUAa-H6RZsAAAIXmAAAAA==
Different Outlook clients will return the itemId in the protocol they leverage. REST and EWS itemIds are escaped differently which is causing the difference between the itemId for the same item. To convert an EWS itemId to REST you can leverage the convertToRestId JS API.