-
Notifications
You must be signed in to change notification settings - Fork 54
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
How to get Notes from Service Requests? #63
Comments
Hi Anand, I would recommend that you check out the Service Request examples from the Partner Center SDK sample project. If that does not help then it would be a good idea to open a support ticket through Partner Center regarding this question. |
Hi @IsaiahWilliams thank you for your reply. I got Notes if am using ID: When i use the below code to retrieve all service request notes, i am getting null value for all notes. Source: https://docs.microsoft.com/en-us/partner-center/develop/get-service-request-details-by-id Thanks in advance |
Hi Anand, The behavior you described is excepted. You will notice that various components of the Partner Center API/SDK behave in this manner. This was done to ensure that the data being returned from the API is done so in an optimal manner. If you would like to get the notes for each service request then my recommendation would be
What I have seen most partner do is use the partnerOperations.ServiceRequest.Get() function to obtain a list of service requests. Then they use that data to populate a website where the user can click on an issue to drill into it. |
Hi @AnandKumar2610, please let us know if you are still having issues. I am going to close this issue for now, but please feel free to reopen it. |
Hi @IsaiahWilliams thanks for your reply. |
My Code:
ResourceCollection<ServiceRequest> serviceRequests = partnerOperations.ServiceRequests.Get();
I got only NULL values for Notes!
Source: https://docs.microsoft.com/en-us/partner-center/develop/get-all-service-requests-for-a-customer
Thanks in advance
-Anand
The text was updated successfully, but these errors were encountered: