cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ramirefm
Regular Visitor

Counting differences between two sql tables

Hello, I am trying to return the number of differences that there are between two tables that I have in a sql database. They are both nearly identical besides the actual values. So the column and row names are exactly the same as well as the amount of columns and rows. I've tried to directly compare columns however it gives me an error: 

CountIf(Patients, Patients.FirstName <> PatientEdits.FirstName);

Ideally I want to be able to count all differences between one row from both tables.

1 ACCEPTED SOLUTION

Accepted Solutions

@ramirefm 

I think I got it working but I am totally unsure if this is a "good" approach.

 

I tried it like this. First I created 2 initial collections. Based on those initial Collections I created two new working collections with one addition column where I just concatenated all columns

ClearCollect(colListA,{FirstName:"Lutz",LastName:"Beyer"},{FirstName:"Max",LastName:"Mustermann"},{FirstName:"Power",LastName:"Ranger"});
ClearCollect(colListB,{FirstName:"Lutz",LastName:"Beyer"},{FirstName:"Max",LastName:"MusterFrau"},{FirstName:"Power",LastName:"Ranger"});

ClearCollect(colListACombinded,AddColumns(colListA,"Combined",FirstName&LastName));
ClearCollect(colListBCombinded,AddColumns(colListB,"Combined",FirstName&LastName));

 

I then compared the working collections like this

Clear(Counter);
Clear(rowErrors);
ForAll(
    colListACombinded,
    Collect(
        Counter,
        Last(Counter).Value + 1
    );
    If(
        Last(
            FirstN(
                colListBCombinded,
                Last(Counter).Value
            )
        ).Combined = ThisRecord.Combined,
        Collect(
            rowErrors,
            {
                row: Last(Counter).Value,
                HasError: false
            }
        ),
        Collect(
            rowErrors,
            {
                row: Last(Counter).Value,
                HasError: true
            }
        )
    )
);

As in PowerApps we can't get an item based on a index we have to use this "ugly" Last(FirstN..." part.

 

Within the ForAll I add records to the collection rowErrors. If the Combined columns don't match HasError will be true otherwise false.

 

You can add three Galleries on your screen and one Button. Paste the Complete code in the OnSelect of the button. Point your Galleries to colListA, colLisB and rowErrors

 

PowerRanger_0-1644276577927.png

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.




​Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item.

If the content was useful in other ways, please consider giving it Thumbs Up.

View solution in original post

10 REPLIES 10

@ramirefm @So you want to compare row 1 of table 1 and row 1 of table 2…. Row 2 of table 1 and row 2 of table 2 ….and so on. Or do the tables have a column which must be used to find the rows belonging to each other?




​Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item.

If the content was useful in other ways, please consider giving it Thumbs Up.

Yes, you've got the right idea, I want to compare row 1 of table 1 and row 1 of table 2 and so on. I don't need anything with the columns as the rows should already be aligned with each other.

@ramirefm 

I think I got it working but I am totally unsure if this is a "good" approach.

 

I tried it like this. First I created 2 initial collections. Based on those initial Collections I created two new working collections with one addition column where I just concatenated all columns

ClearCollect(colListA,{FirstName:"Lutz",LastName:"Beyer"},{FirstName:"Max",LastName:"Mustermann"},{FirstName:"Power",LastName:"Ranger"});
ClearCollect(colListB,{FirstName:"Lutz",LastName:"Beyer"},{FirstName:"Max",LastName:"MusterFrau"},{FirstName:"Power",LastName:"Ranger"});

ClearCollect(colListACombinded,AddColumns(colListA,"Combined",FirstName&LastName));
ClearCollect(colListBCombinded,AddColumns(colListB,"Combined",FirstName&LastName));

 

I then compared the working collections like this

Clear(Counter);
Clear(rowErrors);
ForAll(
    colListACombinded,
    Collect(
        Counter,
        Last(Counter).Value + 1
    );
    If(
        Last(
            FirstN(
                colListBCombinded,
                Last(Counter).Value
            )
        ).Combined = ThisRecord.Combined,
        Collect(
            rowErrors,
            {
                row: Last(Counter).Value,
                HasError: false
            }
        ),
        Collect(
            rowErrors,
            {
                row: Last(Counter).Value,
                HasError: true
            }
        )
    )
);

As in PowerApps we can't get an item based on a index we have to use this "ugly" Last(FirstN..." part.

 

Within the ForAll I add records to the collection rowErrors. If the Combined columns don't match HasError will be true otherwise false.

 

You can add three Galleries on your screen and one Button. Paste the Complete code in the OnSelect of the button. Point your Galleries to colListA, colLisB and rowErrors

 

PowerRanger_0-1644276577927.png

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.




​Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item.

If the content was useful in other ways, please consider giving it Thumbs Up.

@ramirefm 

To get the amount of Errors place another label on the screen and set its Test property to

"Errors:" & CountIf(rowErrors,HasError = true)

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.




​Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item.

If the content was useful in other ways, please consider giving it Thumbs Up.

@ramirefm 

To get the Errors on column level you could try this:

Clear(Counter);
Clear(columnError);
ForAll(
    colListACombinded,
    Collect(
        Counter,
        Last(Counter).Value + 1
    );
    If(
        Last(
            FirstN(
                colListBCombinded,
                Last(Counter).Value
            )
        ).FirstName = ThisRecord.FirstName,
        Collect(
            columnError,
            {
                row: Last(Counter).Value,
                HasError: false,
                Field:"FirstName"
            }
        ),
        Collect(
            columnError,
            {
                row: Last(Counter).Value,
                HasError: true,
                Field:"FirstName"
            }
        )
    );
    If(
        Last(
            FirstN(
                colListBCombinded,
                Last(Counter).Value
            )
        ).LastName = ThisRecord.LastName,
        Collect(
            columnError,
            {
                row: Last(Counter).Value,
                HasError: false,
                Field:"LastName"
            }
        ),
        Collect(
            columnError,
            {
                row: Last(Counter).Value,
                HasError: true,
                Field:"LastName"
            }
        )
    )
);

Add another Gallery on your screen and sets its items property to columnError

 

PowerRanger_0-1644278335059.png

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.




​Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item.

If the content was useful in other ways, please consider giving it Thumbs Up.

@ramirefm 

This would be my final approach for column comparison:

Clear(Counter);
Clear(columnError);
ForAll(
    colListACombinded,
    Collect(
        Counter,
        Last(Counter).Value + 1
    );
    With(
        Last(
            FirstN(
                colListBCombinded,
                Last(Counter).Value
            )
        ) As relatedRecord,
        If(
            relatedRecord.FirstName = ThisRecord.FirstName,
            Collect(
                columnError,
                {
                    row: Last(Counter).Value,
                    HasError: false,
                    Field: "FirstName"
                }
            ),
            Collect(
                columnError,
                {
                    row: Last(Counter).Value,
                    HasError: true,
                    Field: "FirstName"
                }
            )
        );
        If(
            relatedRecord.LastName = ThisRecord.LastName,
            Collect(
                columnError,
                {
                    row: Last(Counter).Value,
                    HasError: false,
                    Field: "LastName"
                }
            ),
            Collect(
                columnError,
                {
                    row: Last(Counter).Value,
                    HasError: true,
                    Field: "LastName"
                }
            )
        )
    )
);

 

So for each column you want to compare you have to add another:

If(
            relatedRecord.<column name> = ThisRecord.<column name>,
            Collect(
                columnError,
                {
                    row: Last(Counter).Value,
                    HasError: false,
                    Field: "<column name>"
                }
            ),
            Collect(
                columnError,
                {
                    row: Last(Counter).Value,
                    HasError: true,
                    Field: "<column name>"
                }
            )
        )

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.




​Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item.

If the content was useful in other ways, please consider giving it Thumbs Up.

@PowerRanger 

So I believe earlier we were having a discussion about the ForAll and the power of it.  When used like the ForLoop that you have in the formula, it is quite a "so-so" formula.

When used in the way it was intended, it becomes quite powerful and your formula on your Gallery can become simply this:

With({_listA: Table({FirstName:"Lutz",LastName:"Beyer"},{FirstName:"Max",LastName:"Mustermann"},{FirstName:"Power",LastName:"Ranger"}),
      _listB: Table({FirstName:"Lutz",LastName:"Beyer"},{FirstName:"Max",LastName:"MusterFrau"},{FirstName:"Power",LastName:"Ranger"})},

      
      Filter(
        ForAll(Sequence(CountRows(_listA)),
            With({_listItemA: Last(FirstN(_listA, Value)), _listItemB: Last(FirstN(_listB, Value))},
              {Comp: (_listItemA.FirstName = _listItemB.FirstName) &&
                     (_listItemA.LastName = _listItemB.LastName),
               itemA: _listItemA,
               itemB: _listItemB
              }
            )
        ),
        !Comp
      )
)

A label in the Gallery to show the first and last name of list a, and a label to show the different record first and last name in List B.

RandyHayes_0-1644279728112.png

 

No collections needed and no behavioral actions needed. It will just show the records that are in error.

To get counts, if used from a gallery, then CountRows(galleryName.AllItems) will give you the count. 

 

Just thought I would throw this out there as we had discussed earlier, and this is a good example about how to use the ForAll correctly.  Makes a big difference!

 

Hopefully this will be helpful for you.

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

@RandyHayes I knew you will comment this because of our discussion before 🙂 and that’s the only reason why I said “totally unsure if this is a "good" approach.”

 

Still trying to get my head around on how to use ForAll correct…. At least I believe I understood the power of With now 🙂




​Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item.

If the content was useful in other ways, please consider giving it Thumbs Up.

@PowerRanger 

Lol...too funny!  I wasn't trying to intrude, just saw the formula and, said - there's a good example of a ForAll backward...🤣

I used a With in that formula just to encapsulate the data, but it could easily be a datasource, a Gallery, or any other table producing item.

 

I will say as a side, there is one ability that is lacking in PowerApps...the ability to compare a record.  It would be ultra-nice to be able to do a recordA = recordB to determine if they are the same.  Now, I fully understand why it does not exist...but it would be nice! 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

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 in the Forums 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 of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (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. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     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 Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     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 Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

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