HTTP Request to Project Online - Entry without a type name

(0) Share

Report

Posted on by PhilFancy

124

Hope there is someone to help me,

goal is to use HTTP request to update a project in Project Online.

Followed lots of guides ending up facing this error:

An entry without a type name was found, but no expected type was specified. To allow entries without type information, the expected type must also be specified when the model is specified.
clientRequestId: ccf59fb2-6af8-4399-ab3e-328e9ac40019
serviceRequestId: e8ca8da0-b05c-6000-0d83-688c843fec3e

This is how I tried to update description field of a project.

To keep it simple the flow is started manually. Single action HTTP request.

Has anyone a suggestion which type I might need to add and how to do this?

Thanks in advance!

Categories:

General topics

I have the same question (0)

All responses (7)

Answers (1)

Expiscornovus 33,189 Most Valuable Professional on at

Like (1)

Report
Hi @PhilFancy,

You are trying to update an existing project correct? Normally I would checkout the project first before I make a change. You can use the default checkout project action for that.

I would also suggest to add the X-HTTP-Method MERGE header in your Header section. Can you add that one.

{ "Accept": "application/json;odata=verbose", "Content-Type": "application/json;odata=verbose", "If-Match": "*", "X-HTTP-Method": "MERGE" }

If that additional Header does not fix it try adding the Name field (which I believe is required) also to the Body payload:

{ "Name": "My Project Name", "Description": "Test Description" }

And lastly publish it with the checkin and publish project action as well.

Was this reply helpful? Yes No
PhilFancy 124 on at

Like (0)

Report
Thank you for your reply!

I modified the flow as recommended.
The approaches regarding title as mandatory field, the extended header and checking out the project sounded understandable.
The project was already checked out manually before. I still included the action in the flow so that it is from the same session (and certainly the right user).

Unfortunately, the problem remains the same. There are no custom fields set mandatory in the PWA. But as far as I understand custom fields are not affected by this HTTP request at all.

{ "status": 400, "message": "An entry without a type name was found, but no expected type was specified. To allow entries without type information, the expected type must also be specified when the model is specified.\r\nclientRequestId: 8606cfdf-daac-4066-8710-9a653a910f81\r\nserviceRequestId: 89028ea0-e063-6000-0d83-60b60fe44c48", "source": "https://TENANT.sharepoint.com/sites/INTProjectCenterTest/_api/ProjectServer/Projects('2912f118-4297-ed11-abcf-00155df8957d')/draft/", "errors": [ "-1", "Microsoft.SharePoint.Client.InvalidClientQueryException" ] }

{ "Pragma": "no-cache", "Cache-Control": "no-store, no-cache", "Set-Cookie": "ARRAffinity=c3e56c5cc8f2059e9ca5b31ea6306f0b4d439389925f19007ee442dc2004e749;Path=/;HttpOnly;Secure;Domain=sharepointonline-ne.azconn-ne-003.p.azurewebsites.net,ARRAffinitySameSite=c3e56c5cc8f2059e9ca5b31ea6306f0b4d439389925f19007ee442dc2004e749;Path=/;HttpOnly;SameSite=None;Secure;Domain=sharepointonline-ne.azconn-ne-003.p.azurewebsites.net", "x-ms-request-id": "04038ea0-a0e1-6000-0d83-6726b3c94b76", "Strict-Transport-Security": "max-age=31536000; includeSubDomains", "X-Content-Type-Options": "nosniff", "X-Frame-Options": "DENY", "Timing-Allow-Origin": "*", "x-ms-apihub-cached-response": "true", "x-ms-apihub-obo": "false", "Date": "Fri, 20 Jan 2023 07:10:10 GMT", "Content-Length": "586", "Content-Type": "application/json", "Expires": "-1" }

Hope this messages help to identify the issue.

EDIT:
Removed description and set Title as only value to be changed to make it more simple - issue persists
Selected other project from same PWA - issue persists
Tried most of the out-of-the-box actions for "Project Online" to get information about all projects or the project in question. All ootb actions work fine, only custom http requests fail (like populate custom fields or populate default fields).
EDIT 2:
Found several people facing the same problem updating SharePoint Lists via http request. They solve this issue by adding a __metadata type. Maybe something like this?
{'parameters': { "__metadata":{"type":"SP.List"}, "BaseTemplate": 100, "Title": "Flow Employees", "Description": "Employees Details List" } }

Was this reply helpful? Yes No
Expiscornovus 33,189 Most Valuable Professional on at

Like (1)

Report

Hi @PhilFancy,

Here is a sample I shared and tested a while ago.

https://powerusers.microsoft.com/t5/Building-Flows/Use-SharePoint-Rest-API-to-update-Project-Details-in-PWA/m-p/870577/highlight/true#M122249

Only difference which I can see with your action setup is that I did not use a / slash character after the draft method. Might be worth a shot to remove that character?

Was this reply helpful? Yes No
Verified answer

PhilFancy 124 on at

Like (3)

Report

Thank you! It was not the slash that made the difference - the sample you shared made me see the difference.

Instead of "application/json; odata=verbose" on Accept and Content-Type there must be "application/json; odata=nometadata"!

This is a working HTTP request to Project Online from Power Automate:
Prerequisite is that the project must be checked out.
Thank you for your assistance very much!

Was this reply helpful? Yes No
Expiscornovus 33,189 Most Valuable Professional on at

Like (0)

Report

Hi @PhilFancy,

Great to see you spotted that. I did not notice the difference in headers. Glad the other screenshot helped out 😁

Was this reply helpful? Yes No
Suggested answer

CU11071703-0 2 on at

Like (0)

Report

Hello. Can you post an example of how to check out the project? Thanks.

Was this reply helpful? Yes No
Tomac 3,948 Moderator on at

Like (0)

Report

@CU11071703-0 please post your question as a new thread in the forum rather than posting to a years-old question that's already been answered.

Was this reply helpful? Yes No