Skip to content
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

sample/sharepoint-list-update-created-by #110

Conversation

Glynnryan
Copy link
Contributor

By submitting this pull request, you agree to the contribution guidelines

If you aren't familiar with how to contribute to open-source repositories using GitHub, or if you find the instructions on this page confusing, sign up for one of our Sharing is Caring events. It's completely free, and we'll guide you through the process.

To submit a pull request with multiple authors, make sure that at least one commit is a co-authored commit by adding a Co-authored-by: trailer to the commit's message. E.g.: Co-authored-by: name <name@example.com>

Put an x in all the items that apply ([x], without spaces), make notes next to any that haven't been addressed.

  • Bug fix?
  • New sample?
  • Related issues: fixes #X, partially #Y, mentioned in #Z
  • Needs API permissions?
  • Has other prerequisites? (E.g. requires a list, document library, etc.)

What's in this Pull Request?

This is a new sample for a solution called Update "Created by" in a Microsoft List, which is a Power Automate flow updates the “Created By” field of a Microsoft List item, replacing the account with a specified user based on their email address, using an HTTP request to SharePoint.

Checklist

  • My pull request affects only ONE sample.
  • I have updated the README file.
  • My README has at least one static high-resolution screenshot (i.e. not a GIF)
  • My README contains complete setup instructions, including pre-requisites and permissions required

This Power Automate flow updates the “Created By” field of a Microsoft List item, replacing the account with a specified user based on their email address, using an HTTP request to SharePoint.
Rename directory to match existing directories naming convention
@Katerina-Chernevskaya
Copy link
Contributor

Hi @Glynnryan ,

Thank you for your submission! We value your time and contribution.
To move forward with the review and merging of your pull request, we kindly request that you update your PR in accordance with the Contribution Guidelines. Please ensure that the source code is prepared following these instructions.

Thank you!

Regards,
Katerina Ch.

@Katerina-Chernevskaya Katerina-Chernevskaya added the Needs Attention Something needs to be fixed with the PR before merging label Oct 9, 2024
@Glynnryan
Copy link
Contributor Author

Hi @Katerina-Chernevskaya,
Apologies for the incorrect format. I'm swamped with work at the moment and will look into this next week.

Update sample files per PR instructions using pac
@Glynnryan
Copy link
Contributor Author

Hi @Katerina-Chernevskaya, I found a quick gap to update the PR.
I've submitted the sample using these instructions.

I also forgot to add a description for the changes in commit 79fe3be. Apologies... This was to update the tracking image src.

I hope all is now in order.

@Katerina-Chernevskaya Katerina-Chernevskaya removed the Needs Attention Something needs to be fixed with the PR before merging label Oct 15, 2024
Copy link
Contributor

@Katerina-Chernevskaya Katerina-Chernevskaya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Glynnryan ,
Thank you for updating the solution and for your contribution! I've made some changes in the Read Me file - reorder the path, moved reference files into assets, and added the sample.json file.
I'm going to merge your sample.
Thank you for sharing! :)

Regards,
Katerina Ch.

@Katerina-Chernevskaya Katerina-Chernevskaya merged commit b651688 into pnp:main Oct 15, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants