cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Use SharePoint Rest API to update Project Details in PWA

I'm trying to update a field in the Project Details of a project by a flow. Should I be using SharePoint REST API or HTTP web action?  I'm currently attempting with the SP API action, and have the following entries on the action:

spaction.png

This renders a 'forbidden' value for an error.   What is the best way to dynamically set fields at the Project level for PWA?

1 ACCEPTED SOLUTION

Accepted Solutions
Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @illmatic,

 

As far as I am aware the ProjectData endpoint is for reporting purposes. Try the ProjectServer endpoint instead.

 

Below is an example of the request with the project description (one of the default fields in the project details).

 

I believe that with custom fields you have to approach it a bit differently, so you might want to adjust this example:

https://docs.microsoft.com/en-us/office/client-developer/project/bulk-update-custom-fields-and-creat...

 

 

updateprojectdescription.png

 

Btw, don't forget to checkout, update, checkin and publish your project 😄

projectonline_steps.png

 



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


View solution in original post

16 REPLIES 16
Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @illmatic,

 

As far as I am aware the ProjectData endpoint is for reporting purposes. Try the ProjectServer endpoint instead.

 

Below is an example of the request with the project description (one of the default fields in the project details).

 

I believe that with custom fields you have to approach it a bit differently, so you might want to adjust this example:

https://docs.microsoft.com/en-us/office/client-developer/project/bulk-update-custom-fields-and-creat...

 

 

updateprojectdescription.png

 

Btw, don't forget to checkout, update, checkin and publish your project 😄

projectonline_steps.png

 



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


Thanks! @Expiscornovus 

I tried this approach but received the following 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.


Assuming this has to do with the Body parameter?  

Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @illmatic,

 

I don't think it is because of the body parameter. I have checked my Project Online environment and I am not seeing any ProjectManagerName field on the Project details page. So, I am assuming you created it as a custom field. Is it is single line of text custom field?

 

When you are using a custom field the approach would be slightly different, this would be the draft/updatecustomfields method. In my previous example I was using a standard field (description).

 

Below is an example of how you could update a custom field of single line of text.

You have to use the internalname of the ProjectManagerName custom field for the key. Paul Mather has written a good blog about how to find that internalname:

https://pwmather.wordpress.com/2018/05/21/using-rest-in-javascript-to-update-projectonline-project-c...

 

{"customFieldDictionary":[{"Key":"@{variables('InternalName')}",
"Value":"John Doe", "ValueType":"Edm.String"}]}

 

customfield_projectdetails.png



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


@Expiscornovus 

 

Thanks but it is not a custom field that I created nor is it present in the Enterprise Custom Fields that are created by the system by default.  It is part of the Project entity.  It isn't visible in the Project Details page at all.  I was able to locate it using SPInsider plugin.  

 

And sorry, this is my mistake... I kind of changed requirement based on when I first started creating the post.

UPDATE:  I am realizing that this initial field 'ProjectManagerName' was a field I could see in the ProjectData feed, but I do not see it listed in ProjectServer.   Is there an equivalent field for this?  Where would this information be derived from?   As again, it's not a custom field.  Essentially, my understanding [and I may be wrong] is that listing a Project Manager may drive PWA permissions/SP groups.  I would like to set a Project Manager so that person is automatically given Owner rights when their site is created by PWA.     

I have attempted to update a field that is listed on the Project Details page.  Both 'Description' and 'Owner' still yield the same error with Patch method.  I have modified the Action to use a Post method and this action just times out.  I'm unsure of the cause.

Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @illmatic,

 

Lets start with that Description test, just want to make sure that you can at least update default project details fields.

 

Can you post a screenshot of the configuration of the send an http request action or the whole flow setup?

 

And second question about that test. You are checking the project out in your flow before you are send the PATCH request? 



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


Yep!  I tried Description and I either get a BadRequest or it hangs forever.   I can verify that yes I am checking out the project prior to running the action.  Here is an overview of all steps related to the Project Online connectors in the flow:

sp-action2.pngsp-action1.png

The only thing I can think of is maybe there needs to be an action after Create the project site to check-in & publish, then re-checkout the project, run the action, and then check it back in?   I have tried small modifications to the syntax... For instance using double quotations instead of single in the body parameter, and adding a / before _api and/or removing it.  Nothing produces the desired outcome.

Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @illmatic,

 

That is definitely a difference with my test. I am changing the description on an existing project.

 

If possible, test it without the create project action and use an existing project id instead.

 

Also make sure that your project is not checked out from a previous test:

https://docs.microsoft.com/en-us/project/check-in-enterprise-projects-in-project-server

 

Btw, on a side note. I am using this value as the site root url in my tests. I am assuming you are using the same kind of PWA root url?

https://contoso.sharepoint.com/sites/pwa

 



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


I am using a site collection that has PWA enabled, but it is entitled 'projects' instead of PWA.   I don't think this should matter, considering in the flow above the Project is created just fine and it checks out the project itself just fine as well.

Since I have some other actions in this flow, I'll create a new one to see if this updates the fields.

I deleted the actions related to Project Online initially and replaced with the following:

-Checkout Project [of previously created project]

- Send an http request to SP  

 

I used the same info as in the other screenshots.

 

Everything worked fine until I got to the 'Send a request to SP action.'  This resulted in the same error as follows:

 

{
  "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: a5ebd749-5dd1-4867-8cbe-41134ff97c86\r\nserviceRequestId: eec1b79f-3066-0000-9a06-cbf2984ae53d",
  "source": "https://mysite.sharepoint.com/sites/pwatest/_api/ProjectServer/Projects('f5656d50-7c8d-eb11-bf98-00155de91211')/Draft",
  "errors": [
    "-1",
    "Microsoft.SharePoint.Client.InvalidClientQueryException"
  ]
}

 

This seems to me that I need to specify the fields in the body parameter.   

I looked at the Enterprise Fields once more, I think I may have figured out the issue.  One of the columns is marked as required.  This means it probably cannot update the Project until those fields are actually filled in.   I'm going to unmark the required field, and see if I add my initial actions back if this resolves the issue.   

 

Thanks for your help thus far!  Much appreciated!

Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @illmatic,

 

That sounds like you are getting close to the root cause. A required field makes sense. Keep me posted on your progress 🙂



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


Hey @Expiscornovus ,

That was the culprit!  Removing the required field resolved everything, and I was also able to add the 'Create a project' actions back.  Thank you so much for the assist!  

Expiscornovus
Most Valuable Professional
Most Valuable Professional

Hi @illmatic,

 

Great to hear that it is working. That is good news 🙂



Happy to help out! 🙂

Interested in more #PowerAutomate #SharePointOnline or #MicrosoftCopilotStudio content?
Visit my blog, Subscribe to my YouTube channel or Follow me on Twitter


@Expiscornovus @illmatic 

Hello, currently facing the same problem that illmatic was having. Tried to replicate exactly what you both did in order to accomplish this.

 

Goal: Information from SharePoint list gets added to custom enterprise field in Project Online. The project is already created in Project Online, we just need to be able to migrate the information from the SharePoint list to the Project Online custom enterprise fields.


Problem: We are unable to update any custom enterprise field using the SharePoint HTTP connector.

Things Done:
1) Checked that Project Online fields are not required
2) Tried different URIs and IDs 
3) Tried the "Key"::", "Value":"", "Value-Type":"" method

4) Tried: {"Description":"Test"}

Any ideas? Is the only required ID the GUID for the specific project? Or are other IDs needed as well?

Current workflow:

SpaceShip_0-1657225308627.png

SpaceShip_1-1657225463082.png

SpaceShip_2-1657225571756.png

 

Hi, I am using this exact request by I keep getting badGateway error, any ideas why? the projects are created in the same flow

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (2,298)