opkfy.blogg.se

Which gives a lot of benefits as most users "live" in Outlook.

We learned how to build applications for Outlook. Deep dive into both API's gave us the opportunity to display the correct properties of the tasks with eventually the only difference between the two systems: the icon at front. Accomplishments that we're proud ofĬombining multiple sources of data is never easy, but we accomplished a seamlessly integration of SharePoint -and Planner tasks. Therefore we went for the standard SharePoint Online API endpoints. Microsoft Graph now includes a SharePoint API endpoint but does not allow you to call the search API.

Challenges we ran intoĪt the moment Planner is still quite new, so not all API endpoints give use the right amount of information we needed to build the module. It makes use of the Microsoft Graph to work with the Planner tasks API and SharePoint Online. This Outlook module is built with React and Node.js. This gives the user more time on actual completing its tasks, instead of searching for them. The user will have the ability to filter, group, update and complete them. This Outlook module gives you an overview of all your SharePoint and Planner tasks. This is what we want to tackle with our Outlook module. This makes it difficult for end-users to get an overview of all their tasks and / or complete them. In most organizations, the three main tools are Outlook, SharePoint (Project), and Planner as the new kid on the block. These days you have a lot of applications where you can go for task management.