I am creating flows that will send data from List A to List B. The primary flow creates a new item in list B when one is created in list A. That one is easy and works. The second flow is intended to update list B when an item is updated in list A. So far, I can't get it to work (flow below). One issue it seems is the way I set up the list columns in list B, instead of using the SharePoint ID, Modified, and Modified By columns, I used custom columns of ID-A, Mod-A, and Mod By-A.
The List A ID date is entered in the ID-A column in List B. Although this works great for creating the item. This seems to be a problem for updating the items. The "update" flow using the When an item or a file is modified action fails at the Update Item step. I need a way to tell the flow which item to update.
FYI- If using an excel spreadsheet would work better for "List B," I'm happy to do so. Using a List for B is not necessary, I just thought it would be easier.
Solved! Go to Solution.
SOLUTION - Add and Update Data from One List to Another (A to B)
Goal
User needs a “one-way” transfer of data. When data is added to List A, the flow will add the new item to List B. In addition, when an item on List A is modified (changed), the flow will update the same item in List B. This flow allows Team A members to keep “official” clean data that can’t be modified by Team B members. While Team B members need “view” access to all data, they can’t make changes to List A data, but they can make additions to List B columns that are designated for them.
Solution
Components
A key component of the solution is to use the Compose action to filter out the ID and the Version number from the ID (the “everything ID” which is the triggerOutputs()?[‘body/ID’]).
I use the following expression to get just the ID number:
int(outputs('Flow_gets_the_data')?['body/ID'])
This gets the ID from List A as a number. That number is used to find the right item in List B.
I use the following expression to get just the Version number:
int(outputs('Flow_gets_the_data')?['body/{VersionNumber}'])
This gets the Version from List A as a number. That number is used to determine if this is a new item or if this is a modification.
Flow Description
When a LIST A item is added or modified, the Flow gets the data and using the Compose action, the ID and Version are filtered out as numbers. If the version is equal to 1, it is a new item and the item is added to LIST B and the flow stops. Otherwise, the flow updates LIST B using the ID number filtered using the Compose action. If the word Delete, is found in the Delete column, the flow deletes the item from Flow B and A and a post is sent to the Team channel. Otherwise, an “Item Modified” post is sent to the Team channel.
Sample List
These columns were used in testing.
List A
ID | Modified | Modified By | Title | Data-01 | Data-02 | Data-03 | Comments | Delete |
List B
ID | Modified | Modified By | Title | Data-01 | Data-02 | Data-03 | Comments | Data-B-01 | Data-B-02 | Notes | Mod-A | By-A |
List B uses the Modified and Modified By fields to track when Team B members make modifications to the item. The Mod-A and By-A fields let Team B members know which Team A member originally added the item.
Issues
Delete- Users must remember to use the Delete List field to remove an item. Either “Delete” or “delete” can be entered. However, users must NOT use the LIST delete feature.
Calculations- If you are working with numbers (like calculating a salary), the Calculate List column will NOT show up as an option when adding Dynamic Content. This is really a problem. Just have a “calculate” column if both List A and B. In additional testing I used the following “IF” formula to calculate the salary based on two different salary types (one based on credits of teaching and another based on a fixed salary).
=IF(Credits>1,Credits*[Credit Rate],[Current Salary]+[Salary Increase])
Watch the Microsoft Sharepoint Lists - Complete Beginner Tutorial YouTube videos for some help.
Flow Outline (PIC of table is also below)
# | Step (What is happing) | Action | Notes | |
01 | When a LIST A item is added or modified |
| When an item is created or modified (SharePoint) | List Name = List A |
02 | Flow gets the data |
| Get item (SharePoint) | List Name = List A |
03 | Flow gets the ID for the Item (as a number) |
| Compose (Data Operation) | Formula int(outputs('Flow_gets_the_data')?['body/ID']) |
04 | Flow gets the Version for the Item (as a number) |
| Compose (Data Operation) | Formula int(outputs('Flow_gets_the_data')?['body/{VersionNumber}']) |
05 | If the item is NEW |
| Condition (Control) | Compose Version |
06 | Flow adds data to LIST B | Y | Create item (SharePoint) | |
07 | Flow Terminates Successfully | Y | Terminate (Control) |
|
08 | LIST B is updated with changed data |
| Update Item (SharePoint) | Compose ID |
09 | If Delete is found in DELETE column |
| Condition (Control) | Use: outputs('Flow_gets_the_data')?['body/Delete’] |
10 | Flow deletes the item from LIST B | Y | Delete item (SharePoint) | Compose ID |
11 | Flow deletes the item from LIST A | Y | Delete item (SharePoint) | |
12 | Item data has been DELETED post is sent to Teams channel | Y | Post a message as the Flow bot to a channel (Teams) |
|
13 | Item data has been UPDATED post is sent to Teams channel | N | Post a message as the Flow bot to a channel (Teams) |
|
Hi @Alex_CCI may be when you are creating a new item in your list B you can store the ID of this Item in your list A and then your Update would also be simple and easy
Can you be more specific, not sure what good storing the ID would do, if there is no way to use it to tell the flow which is the unique field to use to determine what row to update.
SOLUTION - Add and Update Data from One List to Another (A to B)
Goal
User needs a “one-way” transfer of data. When data is added to List A, the flow will add the new item to List B. In addition, when an item on List A is modified (changed), the flow will update the same item in List B. This flow allows Team A members to keep “official” clean data that can’t be modified by Team B members. While Team B members need “view” access to all data, they can’t make changes to List A data, but they can make additions to List B columns that are designated for them.
Solution
Components
A key component of the solution is to use the Compose action to filter out the ID and the Version number from the ID (the “everything ID” which is the triggerOutputs()?[‘body/ID’]).
I use the following expression to get just the ID number:
int(outputs('Flow_gets_the_data')?['body/ID'])
This gets the ID from List A as a number. That number is used to find the right item in List B.
I use the following expression to get just the Version number:
int(outputs('Flow_gets_the_data')?['body/{VersionNumber}'])
This gets the Version from List A as a number. That number is used to determine if this is a new item or if this is a modification.
Flow Description
When a LIST A item is added or modified, the Flow gets the data and using the Compose action, the ID and Version are filtered out as numbers. If the version is equal to 1, it is a new item and the item is added to LIST B and the flow stops. Otherwise, the flow updates LIST B using the ID number filtered using the Compose action. If the word Delete, is found in the Delete column, the flow deletes the item from Flow B and A and a post is sent to the Team channel. Otherwise, an “Item Modified” post is sent to the Team channel.
Sample List
These columns were used in testing.
List A
ID | Modified | Modified By | Title | Data-01 | Data-02 | Data-03 | Comments | Delete |
List B
ID | Modified | Modified By | Title | Data-01 | Data-02 | Data-03 | Comments | Data-B-01 | Data-B-02 | Notes | Mod-A | By-A |
List B uses the Modified and Modified By fields to track when Team B members make modifications to the item. The Mod-A and By-A fields let Team B members know which Team A member originally added the item.
Issues
Delete- Users must remember to use the Delete List field to remove an item. Either “Delete” or “delete” can be entered. However, users must NOT use the LIST delete feature.
Calculations- If you are working with numbers (like calculating a salary), the Calculate List column will NOT show up as an option when adding Dynamic Content. This is really a problem. Just have a “calculate” column if both List A and B. In additional testing I used the following “IF” formula to calculate the salary based on two different salary types (one based on credits of teaching and another based on a fixed salary).
=IF(Credits>1,Credits*[Credit Rate],[Current Salary]+[Salary Increase])
Watch the Microsoft Sharepoint Lists - Complete Beginner Tutorial YouTube videos for some help.
Flow Outline (PIC of table is also below)
# | Step (What is happing) | Action | Notes | |
01 | When a LIST A item is added or modified |
| When an item is created or modified (SharePoint) | List Name = List A |
02 | Flow gets the data |
| Get item (SharePoint) | List Name = List A |
03 | Flow gets the ID for the Item (as a number) |
| Compose (Data Operation) | Formula int(outputs('Flow_gets_the_data')?['body/ID']) |
04 | Flow gets the Version for the Item (as a number) |
| Compose (Data Operation) | Formula int(outputs('Flow_gets_the_data')?['body/{VersionNumber}']) |
05 | If the item is NEW |
| Condition (Control) | Compose Version |
06 | Flow adds data to LIST B | Y | Create item (SharePoint) | |
07 | Flow Terminates Successfully | Y | Terminate (Control) |
|
08 | LIST B is updated with changed data |
| Update Item (SharePoint) | Compose ID |
09 | If Delete is found in DELETE column |
| Condition (Control) | Use: outputs('Flow_gets_the_data')?['body/Delete’] |
10 | Flow deletes the item from LIST B | Y | Delete item (SharePoint) | Compose ID |
11 | Flow deletes the item from LIST A | Y | Delete item (SharePoint) | |
12 | Item data has been DELETED post is sent to Teams channel | Y | Post a message as the Flow bot to a channel (Teams) |
|
13 | Item data has been UPDATED post is sent to Teams channel | N | Post a message as the Flow bot to a channel (Teams) |
|
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!
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
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.
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