-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Under what circumstances would a user not be able to create a OneNote page using Graph Explorer? #598
Comments
@thewahome @irvinesunday Please investigate the query "create page" sample query under OneNote. It doesn't copy the request url to the address bar |
@thewahome does GE support content-types of |
@irvinesunday If Microsoft Graph supports it then Graph Explorer should support it :-D |
@bettirosengugi this is not related to #626 because it fails before sending. Hence why there is no HTTP traffic capture. What needs to be fixed here is placing the query body in the request body to allow someone to send the post request. |
I have partially fulfilled this. It can now display the content in the request body. However it fails to create the one note page. I have created an issue on the SDK repository related to the failing request |
This issue is fixed in Microsoft Graph JS SDK version 2.1.0. |
Use the issues in this repository to open issues about the Graph Explorer application. Questions about the Microsoft Graph should be directed to StackOverflow. Use the [microsoftgraph] tag on StackOverflow.
Expected behavior
After logging in I am able to use graph explorer to see my notebooks and their sections
When I click on create a section a template is copied in the query line where the user is supposed to fill in the notebook-id and then press "Run query"
Similar behavior is expected for "Create page" nothing happens. Is that expected?
Actual behavior
When I click on "Create page" nothing happens
Steps to reproduce the behavior
I use a MS Account, and I login in in MS Graph Explored
Then I try to create a page.
HTTP traffic capture
N/A
AB#6144
The text was updated successfully, but these errors were encountered: