Chrome Extension update using Microsoft Graph API

Job Description:

I have a relatively simple job for somebody that knows Microsoft Graph API that needs completion, but hope to explain it fully here below, so that you can understand what I need clearly.

I already have a Chrome Extension that runs on our CRM system that generates a menu of links to the relevant Customer (Clients) or Sold Products (Plans) in other systems, where those links contain one of two IDs (a Client ID and/or a Plan ID) available in the URL of the CRM webpage being browsed. I have pasted that Browser Extension here but have replaced the URLs to our systems for privacy reasons. One of those URLs generated is a link to our Sharepoint site.

Our Sharepoint file storage contains Client and Plan folders. Plans belong to Clients, and a Client may have many Plans. A Client Folder is named with the Client Name and the Client ID. A Plan folder is named with a Plan Name and a Plan ID. A bit like this:

- Drive >

- Some Client 12345678 >

- Some Plan 234567890

- Some Plan 345678901

- Some Other Client 98765432 >

- Some Plan 45678912

- Some Plan 5678901

One of the URLs generated by our Browser Extension takes you to a search results page for our Sharepoint, looking for folders with that Client or Plan ID. From there, our users will then click into the relevant folder to navigate further. there should only be one result found.

TASK 1:

I would like to change this Search behaviour so that on page load, the extension will check whether the relevant Client and/or Plan folder exists using the Microsoft Graph API using the GET /me/drive/search(q='CLIENTID'). If it does, then it should store the URL of that folder ready for if the user wants to click on the "Go to Client in Sharepoint" or "Go to Plan in Sharepoint" button.

TASK 2:

I would like to add a function that is able to CREATE the folder if the folder is not already found in TASK 1 above using the Microsoft Graph POST /me/drive/root/children endpoint by swapping the 'Go to Plan in Sharepoint' or 'Go to Client in Sharepoint' button for a 'Create Client in Sharepoint' or 'Create Plan in Sharepoint' button. In order to create the folders necessary, the browser extension will need to parse the Client Name and/or the Plan Name from the web page, in addition to the Client ID and Plan ID it is already parsing from the URL.

Client Name can be parsed by searching for <span class="client-information d-flex align-items-center"><span class="d-inline-block">Client: <strong>CLIENT NAME</strong> (xxxxxxxx-CLIENTID)</span></span>

Plan Name can be parsed by searching for <div class="w-100 text-truncate text-left" ui_test_id="client-actions-secondary-info"> Plan: <strong>PLANNAME</strong> (In force) - PLANID </div>

There may be situations whereby the Client folder is found, but the Plan folder is not, and so it would be important that the system is able to create the Plan folder inside the Client folder, where necessary, but also to create both the Client and Plan folders if neither are found. Please find a picture attached as an example.

I look forward to working with you on this project.

NB: FOR DATA PROTECTION REASONS, I CANNOT SHARE WITH YOUR OUR MICROSOFT CLIENT/TENANT/DIRECTORY AUTHORISATION CREDENTIALS. PLEASE HAVE YOUR OWN MICROSOFT GRAPH API DEVELOPER ACCESS SO THAT YOU CAN TEST YOUR WORK WITH YOUR OWN MICROSOFT CLIENT/TENANT AUTHORISATION CREDENTIALS. PLEASE LEAVE AREAS IN THE CODE WHERE I CAN INSERT MY OWN CLIENT/TENANT AUTHORISATION CREDENTIALS WHEN THE TASK IS COMPLETE.

Taidot: Google Chrome, Laajennukset ja lisäykset, JavaScript, RESTful API

Projektin tunnus: #35889084