Calender events of user using OData client connector and Office 365

Document created by aarthi_sridhar Employee on Mar 12, 2018Last modified by sheng_liao462475 on Mar 23, 2018
Version 2Show Document
  • View in full screen mode

Upon seeing two objects (group and users) in the operation of OData client connector, you might wonder how to fetch calendar details of a user.  
Assume we are fetching the data with the below URL syntax: URL: (Base url)/users/{id}/events . When {ID} is one parameter and ‘/events’ is one parameter, these 2 parameters can be passed only if you use query and not get. OData client interprets how they should be passed to server in OData specific way. our GET , DELETE have one default ID param ( for SDK connectors).


OData connector is adding users/{} by default and ID is been passed as a parameter. So OData client connector will be able to add only till {ID}, after which ‘/event’ can be passed as parameter for resource path. For this you might have to select event fields in operation and set as logical expression in filters. Now screenshot shows for SD and ED same way you should do for events. To get the calendar events of that user, for which the URL is: (Base url)/users/{id}/events we have to try Query operation. When multiple parameters are there that is our way of doing with SDK connector. GET, DELETE allow only one param. Container logs or connector debug trace can show full OData request path framed to get connected via OData client connector .

 

Please check if you can use Query operation (instead of GET) in the connector to connect to this path.  Useful link : OData Clientconnector . Below are sample screenshots to browse user object and provide ID of the user for events to be returned as response. 

 

 

 

Attachments

    Outcomes