cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
FraserM
Advocate III
Advocate III

Update the Created By (AuthorID) Field of a SharePoint Online List Item with Power Automate

Disclaimer: There are a few steps required to get this done, but the reward at the end is worth the effort.


Get Created By field GUID

To update the Created By column, we need to first find it’s Field GUID.  Because the Created By column is set to read only, we will query our list for all fields but filter them to only show ones set ReadOnlyField = true

  1. Create a new Send HTTP Request to SharePoint action.  Fill in, adjust according to your tenant / match the rest.
    FraserM_0-1602746130673.png
    URI: _api/web/lists/getbytitle('Your%20List%20Name')/fields?$filter=ReadOnlyField eq true

  2. Run your flow and open the run history, we want to get at the Outputs from the action we created in step 1.
    FraserM_1-1602746130681.png
    Copy the body content and paste it into a text editor of your choice.

  3. Search for Created By in your text editor, and just a few lines up from where it appears is your Created By Field GUID.  Note this because we are going to need it later.
    FraserM_2-1602746130685.png
    You can remove the Send HTTP Request action we created in step 1 – no longer required.

Get UserID Number to write to Created By column

Created By is a person column that has an associated AuthorId field.  The AuthorId field contains a numeric value (ie: 11) which is used to populate the Created By person data.  Our end goal (soon)-- to simply update this field to the numeric value of the user we want listed in the Created By column.

First we need to get our replacement numeric value from somewhere. In the following example I look up a sharepoint users numeric value, simply by supplying their email address (in the example this was dynamic content supplied by a person column in my list called 'EmployeeName')

  1. Create a new Send HTTP Request to SharePoint action.  Fill in, adjust according to your tenant / match the rest.  Let’s get some user data we can pull details from.
    FraserM_3-1602746130689.png
    Uri: _api/web/siteusers/getByEmail('[USER@EMAIL.ADDRESS]')
    Plug in any dynamic content that will provide you with an email address
    FraserM_4-1602746130692.png

     

  2. Now that we have this collection of user data, instead of messing around with formulas to isolate the Users ID #, it’s JSON… let’s parse it.  Create a new Parse JSON action and plug in Body from the dynamic content provided by the Send HTTP Request of the step above.
    FraserM_5-1602746130696.pngFraserM_6-1602746130697.png
    This guide is long enough, if you don’t know how to use a Parse JSON action / generate from sample – it’s super easy to find a how-to on the net.  Go check that out and come back.  Forgive me.

    The Parse JSON action will now create a schwack of dynamic content that can be selectable in future actions.  One dynamic content entry called 'Id', is the numeric value associated to the email address we provided above and exactly what we are going to plug into the AuthorId field!  But, first we must...

Unlock the Created By column

Now that we have taken care of all the prerequisites, let’s get on with unlocking the column for manual updating.  The column is locked by SharePoint automatically after a record gets updated - if you don't unlock it before attempting to update it's contents, the column doesn't get changed.

 

Create a new Send HTTP Request to SharePoint action.  Fill in, adjust according to your tenant/list/Created By fields GUID, match the rest.
FraserM_7-1602746130702.png
Uri: _api/web/lists/getbytitle('Your%20List%20Name')/fields(guid'Your-GUID-goes-here-yasss')
Body:
{ '__metadata': { 'type': 'SP.Field' }, 'ReadOnlyField': false }

Update the Created By field

Now that the Created By column is unlocked, we can update its fields.

 

Create a new Send HTTP Request to SharePoint action.  Fill in, adjust accordingly to your tenant/list, match the rest.
FraserM_8-1602746130707.png
Uri: _api/web/lists/getbytitle('Your%20List%20Name')/items('[ID]')
The ID you should be able to plug in from dynamic content from other actions (ie: Get Items, When a New Item is Created, etc)

Body: { '__metadata': { 'type': 'SP.Data.Your_x0020_List_x0020_NameListItem' }, 'AuthorId': [Id] }
For the [Id] shown, we plug in some dynamic content from our Parse JSON Action.  Note: !pay attention here to cAse.  Use the dynamic content Id (uppercase i lowercase d) -- and not id (all lowercase) when you choose.
FraserM_9-1602746130711.png

 

Re-lock the Created By column

Now we can set the Created By column back to read-only.

 

Create a new Send HTTP Request to SharePoint action.  Fill in, adjust according to your tenant/list/Created By fields GUID, match the rest.
FraserM_10-1602746130716.png
Uri: _api/web/lists/getbytitle('Your%20List%20Name')/fields(guid'Your-GUID-goes-here-yasss')
Body: { '__metadata': { 'type': 'SP.Field' }, 'ReadOnlyField': true }

 

I spent the better part of a day sifting through bits and pieces from various forums -- most of them producing more questions than solutions.  Hopefully, you find this helpful (and save yourself some time).

-F

40 REPLIES 40
AlekPavlov
Frequent Visitor

@FraserM Big Thank you for writing this step-by-step guide. It works brilliant!

Gman8321
Frequent Visitor

Nice tutorial.

 

I was able to work through some errors. But now I notice that even though my flow is working, it is not accepting the change. So I ran a flow to make the created by field not read only, went into SharePoint to update, but receive a message to fix some problems. SharePoint is not accepting the changes to the Created By or Modified By columns through Power Automate. I have a Power Automate flow to get the ReadOnlyField set to false, the Created By and Modified By fields show up in the results. In PowerShell the same fields show as ReadOnlyField set to true. So Power Automate identifies the fields as ReadOnlyField set to false, when in fact the fields are ReadOnlyField set to true.  

AlekPavlov
Frequent Visitor

@Gman8321 Is your flow finished successfully? If yes, than than the Created By should be updated. If no, than there is an error in your flow. At my side I was having issue with Parse JSON but after it was fixed all works fine.

Gman8321
Frequent Visitor

The flow completes successfully.  The flow action reads the property ReadOnlyField as false, and the action to update the value works. But the value isn't updated.  

As I had mentioned, I created a flow to return all columns that have ReadOnlyField set to false. That flow returns the CreatedBy column.  When I get the CreatedBy column properties using PowerShell, ReadOnlyField is set to true. So the flow action is not correctly reading the field property. 

kmsdove
Advocate I
Advocate I

Great tips for using send http request for other scenarios then just getting or posting some data.  I did struggle a bit at first because I wasn't using patch in the method.  I did skip parsing the JSON.  A one line body command can be used to grab the id in a compose.  Either works though.  Very helpful solution!

Anonymous
Not applicable

Can you please help me, the flow says it ran successfully, but the author doesn't change.

UnlockCreatedBy, UpdateCreatedBy and Lock CreatedBy all have te same status code = "204"

I think this might be the problem. Can somebody help me?

 

flow.JPGoutput.JPG

 

Atty
Frequent Visitor

Thank you! This sorted me out perfectly.

Were you able to resolve your issue?

SenoirB
Advocate I
Advocate I

Thank you so much! This allowed me to move Completed items to a folder with a flow and reassign the original Created By person to it! 

I am trying to follow this and i am having trouble with the dynamic content for step two with email. I have a email column I want to use but there is only dynamic content from the trigger showing. and none from the sharepoint. It is not pulling in the Sharepoint fields. I am using a manual trigger as I only need to run this once to update the items that were added already by someone else. I need to update them to match the email in my requestor field

Are you manually running this workflow and using a get items to retrieve SharePoint data?  

I have a manual trigger and then a get item. But as you can see I am not doing something right 

 

lubriz93_0-1675796758869.png

 

Yes you wouldn't be able to see the information with a variable input from a manual trigger.  You need the id in the get items ID field.  Is Latitude a variable from the manual trigger?

I used two inputs now. I think I have it I used email and number for the ID and then ID fromt the trigger for the Id in the Get field. I am not sure if this will work 

 

trigger.png

 

What does the Trigger look like for this FLow. I am trying to update the created by field with the input from my "Requestor Email" column so that it updates to show the email instead of my name. I already have items in my list and need to update them all to show the correct created by which is the person who actually submitted the item "Requestor Email" 

Were you able to resolve this? 

A 'PrimitiveValue' node with non-null value was found when trying to read the value of a navigation property; however, a 'StartArray' node, a 'StartObject' node, or a 'PrimitiveValue' node with null value was expected.

 

I  am still getting this issue and cannot resolve it. 

@FraserM mentioned that he is using JSON but implied that there's a way using variables that he wanted to avoid. I tried using variables but I am not sure about removing the JSON code in the send HTTP actions, as I received error messages about that after placing the variables. 

 

Any thoughts/solutions would be appreciated!

Thanks a lot for this guide and it’s looking like exactly what I can do

with. 

However, I am not getting any dynamic contact coming back when grabbing user data? Like the post, I have a column in my list which has the email addresses I wish to

search for. 

many ideas what I may be missing? 

Did you manage to sort this problem? 

I am having same issue 

Hello @rl17 , not sure if this is helpful given the its been two years since you had this issue.

 

The problem is in this expression: Body: { '__metadata': { 'type': 'SP.Data.Your_x0020_List_x0020_NameListItem' }, 'AuthorId': [Id] } ... see Id is in brackets "[]" which are now used to create a multiple of something, so all you need to do is remove the bracket if you're passing a single item.

 

Hope this helps!

Thank you for your work on this! After a lot of testing, I was able to get this to work using your flow examples as the starting point. This saved me from a big headache!

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 (762)