cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
NigelP
Kudo Kingpin
Kudo Kingpin

Combining Fields Into a Record

Hi

 

I am hitting my head against a Brick wall here.

 

I have a list called "Actuals" which has columns :-

  • Project
  • FY
  • FinancialItem (Actuals or Committed)
  • Internal
  • External

So each Project will have two records (Actual and Committed).

 

I want to combine the two records into one :-

 

  • Project
  • FY
  • InternalActual
  • ExternalActual
  • InternalCommitted
  • ExternalCommitted.

This helps me create a Sum :-

 

FY, InternalActual, ExternalActual,InternalCommitted,ExternalCommitted over all of the Projects and

Project, InternalActual, ExternalActual,InternalCommitted,ExternalCommitted over all of the FYs

 

Can anyone help ?

 

Thanks

 

Nigel

1 ACCEPTED SOLUTION

Accepted Solutions

I'll call this Table1:

Project ID FY ItemType CAPEX OPEX
Proj1 FY18/19 Actual $150,000 $10,000
Proj1 FY18/19 Commit $20,000

$30,000

Proj2 FY18/19 Actual $250,000

$20,000

Proj2 FY18/19 Commit $30,000

$40,000

 

[Side note: you can paste in spreadsheets from Excel 🙂 ]

 

I can group together records that are matching in the columns I choose:

 

GroupBy(Table1,"Project Id", "FY", "GroupName")

This means, "Group together records that have distinct combinations of Project Id AND Fiscal Year. Move the grouped records with all the other columns into a new column called 'GroupName.' The grouped records will result in a nested table."

 

 

Here's what the outer table would look like:

Project ID FY GroupName
Proj1 FY18/19
ItemType CAPEX OPEX
Actual $150,000 $10,000
Commit $20,000 $30,000
Proj2 FY18/19
ItemType CAPEX OPEX
Actual $250,000 $20,000
Commit $30,000 $40,000

 

Now you have the data where you want it. You can AddColumns that can reach into each group. You can set up a gallery's Items like this:

 

AddColumns(
    GroupBy(Table1,"Project Id", "FY", "GroupName"),
"InternalActual",LookUp(GroupName,ItemType="Actual",CAPEX),
"ExternalActual",LookUp(GroupName,ItemType="Actual",OPEX),
"InternalCommitted",LookUp(GroupName,ItemType="Committed",CAPEX),
"ExternalCommitted",LookUp(GroupName,ItemType="Committed",OPEX)
)

 

 

Because GroupBy is like Distinct and other non-delegable functions, it may not return what you're looking for if you use it directly on the datasource. For this to work, I would suggest collecting the data you're looking at to a collection. 

 

And if you really want to tidy up, you can remove the nested tables (the grouped records):

DropColumns(
    AddColumns(
        GroupBy(Table1,"Project Id", "FY", "GroupName"),
    "InternalActual",LookUp(GroupName,ItemType="Actual",CAPEX),
    "ExternalActual",LookUp(GroupName,ItemType="Actual",OPEX),
    "InternalCommitted",LookUp(GroupName,ItemType="Committed",CAPEX),
    "ExternalCommitted",LookUp(GroupName,ItemType="Committed",OPEX)
    ),
"GroupName"
)

View solution in original post

14 REPLIES 14
jhall
Skilled Sharer
Skilled Sharer

This particular answer might apply to your scenario:

 https://powerusers.microsoft.com/t5/General-Discussion/Syntax-for-joining-tables/td-p/61387

 That is mainly about views vs. actually joining the data, but it likely applies.  I'll go ahead and try to connect this to your own scenario.

 One thing you might want to be clear about is if you're using a Table or a Collection.  This can get confusing. In fact, some of Microsoft's own documentation doesn't make a clear distinction between Tables and Collections.  I am going to cross into using a Collection for this below but will try to make it as clear as possible.

 Another thing is that some of the Table/Collection functions you might be trying to use do not actually modify the Table/Collection directly.  What this means is that functions like AddColumns() don't actually add columns to the Table.  They return a new Table that includes the old table plus the new columns.  So AddColumns(myTable,...) does not modify myTable.  You would use it more like: UpdateContext({newTable:AddColumns(myTable,...)}).

For the sake of argument, let's assume you have created a pair of tables (tblActuals and tblCommited) similar to this:

 

UpdateContext({tblActuals:Table({Project:"Project1",FY:2018,FinancialItem:"Play Dough",Internal:1000,External:40})});
UpdateContext({tblCommitted:Table({Project:"Project1",FY:2018,FinancialItem:"Play Dough",Internal:50,External:20})})

Then you have two tables w/ a single record that represent the Actuals and Committed values for a particular project/year (e.g. Project1 and 2018 respectively).  There could be hundreds of records in the table, but I just did one for simplicity.  I think that's what you stated that you're working with.  Two tables that represent the same project/year but are divided by whether they are Committed or Actual.

 

I can create a new Collection that contains everything from one of the two tables by doing something similar to this:

 

ClearCollect(colMerged,RenameColumns(tblActuals,"Internal","InternalActual","External","ExternalActual"))

 

 

To understand what happened here, in one command we empty and create a new Collection called colMerged and then we add all of the records from the table tblActuals, however, we change the names of the columns Internal and External first to represent your new names InternalActual and ExternalActual.

 

But we're missing the other new columns that include the Committed values.  We can modify the above command to include them like so:

 

 

 

ClearCollect(colMerged,RenameColumns(AddColumns(tblActuals,"InternalCommitted",0,"ExternalCommitted",0),"Internal","InternalActual","External","ExternalActual"))

This creates our new Collection as above, but also drops in two additional columns that we can use to merge everything in from the other table (i.e. tblCommitted).  Right now the table would contain all of the records from tblActuals, the two new columns needed for the Committed values, but they'd have Zero for their values.

 

 

But let's go ahead and bring it all together by using this:

 

 

ClearCollect(colMerged,RenameColumns(AddColumns(tblActuals,"InternalCommitted",LookUp(tblCommitted,Project=tblActuals[@Project] And FY=tblActuals[@FY],Internal),"ExternalCommitted",LookUp(tblCommitted,Project=tblActuals[@Project] And FY=tblActuals[@FY],External)),"Internal","InternalActual","External","ExternalActual"))

 

 

Now this is a super mouthful and confusing.  Also, doing references to values that are identically named across two tables is EXTRA confusing.  The last thing we're adding here is a Lookup() function that is going to get values from tblCommitted that match the Project and FY of the record we're currently adding from tblActual.  

 

LookUp(tblCommitted,Project=tblActuals[@Project] And FY=tblActuals[@FY]

The part that might be new to you is the [@Project] portion.  Essentially, in English, we're looking up a record from the table tblCommitted where the column Project / FY from that table matches the column Project / FY from the record within tblActuals that we're currently adding to the new collection colMerged.

 

Sooooo easy.  

 

😉

Mr-Dang-MSFT
Power Apps
Power Apps


@NigelP wrote:

Hi

 

I am hitting my head against a Brick wall here.

 

I have a list called "Actuals" which has columns :-

  • Project
  • FY
  • FinancialItem (Actuals or Committed)
  • Internal
  • External

So each Project will have two records (Actual and Committed).


 

Can you clarify this part? I'm not picturing this table. A table of dummy data would help here.

Hi @Mr-Dang-MSFT

 

I want to go from this =>

 

 

Actuals

 

Project ID         FY          ItemType        CAPEX          OPEX

 

Proj1                FY18/19    Actual         $150,000    $10,000

Proj1               FY18/19     Commit      $20,000      $30,000   

 

To =>

 

Project ID       FY      ActualCAPEX      ActualOPEX     CommittedCAPEX    CommittedOPEX

 

Proj1         FY18/19     $150,000         $10,000            $20,000                     $30,000

 

REgards

 

NIgel

My apologies Nigel, I actually wrote you a looong reply (which for some reason was marked to be "reviewed" and has never yet appeared).  Also, we had an enjoyable -25C weather here and a power outage, leading my PowerApps session that I'd build your solution in to close down when my backup battery ran out of juice.

 

So while I'm not going to go to the trouble of re-writing my full page explanation of how to do this (and the Microsoft folks haven't approved my reply), here's a link to a discussion on what you're wanting to do:

 

https://powerusers.microsoft.com/t5/General-Discussion/Syntax-for-joining-tables/td-p/61387

 

 

Mike8
Memorable Member
Memorable Member

Hello NigelP,

Does this work for you?

 

If you need it in a collection..
ClearCollect(NewCollection,ForAll(Filter(Actuals,ItemType="Actual"),{ProjectID:ProjectID,FY:FY,ActualCAPEX:CAPEX,ActualOPEX:OPEX,CommittedCAPEX:LookUp(Actuals,ProjectID=Actuals[@ProjectID]&&ItemType="Commit",CAPEX),CommittedOPEX:LookUp(Actuals,ProjectID=Actuals[@ProjectID]&&ItemType="Commit",OPEX)}))

If you need the data in a gallery it's easier..
Gallery1.Items = Filter(Actuals,ItemType="Actual")
and you add two more labels with the two LookUps above


But it looks like I remembered most of the code.  Assuming you have two tables of data named tblActuals and tblCommitted:

UpdateContext({tblActuals:Table({Project:"Project1",FY:2018,FinancialItem:"Play Dough",Internal:1000,External:40})});
UpdateContext({tblCommitted:Table({Project:"Project1",FY:2018,FinancialItem:"Play Dough",Internal:50,External:20})})

Then you can merge them into a single table tblMerged like so:

UpdateContext({tblMerged:RenameColumns(AddColumns(tblActuals,"InternalCommitted",LookUp(tblCommitted,Project=tblActuals[@Project] And FY=tblActuals[@FY],Internal),"ExternalCommitted",LookUp(tblCommitted,Project=tblActuals[@Project] And FY=tblActuals[@FY],External)),"Internal","InternalActual","External","ExternalActual")})

To break down what this is doing, you kind of work inside out:

  1. We are Adding InternalCommitted and ExternalCommitted columns to tblActuals and filling them w/ Lookup values from tblCommitted where the FY and Project match.
  2. We are renaming the tblActuals column headers from/to Internal/InternalActual and External/ExternalActual.
  3. We are assigning that to a new table named tblMerged (which you can use to assign to the Items value of any DataTable you add to your app.

I had noted in my other reply, that the problem you might be struggling with is that the various table functions do not directly modify the table itself.  For example, running RenameColumns(X...) does not actually rename any of the columns in X.  It simply returns a copy of that table in memory that can then be assigned to something else.  That's what we're doing when we do the assignmend to tblMerged.

Hi @jhall

 

I really appreciate you going beyond the call of duty and having a backup generator so you can carry on working !

 

It was the last stage (tblMerged) that i was having problems with.

 

I will now test and get back to you with the results.

 

Regards

 

Nigel

Thanks for the many responses @jhall @Mike8. My 2 cents: if you have your data stored on SQL, you can create SQL Views where you join the data together.

 

Otherwise, you can Group() the data by distinct Projects. Then you can reference the data inside as you need. Let me know if you do not have SQL and I can go into this.

Hi @Mr-Dang-MSFT

 

I am using SharePoint lists so I would be interested in your kind offer about Groups.

 

Thanks

 

Nigel

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Tuesday Tips: Community Ranks and YOU

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!This Week: Community Ranks--Moving from "Member" to "Community Champion"   Have you ever wondered how your fellow community members ascend the ranks within our community? What sets apart an Advocate from a Helper, or a Solution Sage from a Community Champion? In today’s #TuesdayTip, we’re unveiling the secrets and sharing tips to help YOU elevate your ranking—and why it matters to our vibrant communities. Community ranks serve as a window into a member’s role and activity. They celebrate your accomplishments and reveal whether someone has been actively contributing and assisting others. For instance, a Super User is someone who has been exceptionally helpful and engaged. Some ranks even come with special permissions, especially those related to community management. As you actively participate—whether by creating new topics, providing solutions, or earning kudos—your rank can climb. Each time you achieve a new rank, you’ll receive an email notification. Look out for the icon and rank name displayed next to your username—it’s a badge of honor! Fun fact: Your Community Engagement Team keeps an eye on these ranks, recognizing the most passionate and active community members. So shine brightly with valuable content, and you might just earn well-deserved recognition! Where can you see someone’s rank? When viewing a post, you’ll find a member’s rank to the left of their name.Click on a username to explore their profile, where their rank is prominently displayed. What about the ranks themselves? New members start as New Members, progressing to Regular Visitors, and then Frequent Visitors.Beyond that, we have a categorized system: Kudo Ranks: Earned through kudos (teal icons).Post Ranks: Based on your posts (purple icons).Solution Ranks: Reflecting your solutions (green icons).Combo Ranks: These orange icons combine kudos, solutions, and posts. The top ranks have unique names, making your journey even more exciting! So dive in, collect those kudos, share solutions, and let’s see how high you can rank! 🌟 🚀   Check out the Using the Community boards in each of the communities for more helpful information!  Power Apps, Power Automate, Copilot Studio & Power Pages

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

Top Solution Authors
Top Kudoed Authors
Users online (4,755)