One or multiple galleries that is the question...

[Cyril06]

Hi with my bad english an exemple will be faster and limpid so:

From this sharepoint list: (french date format too )

Title	Color	Modified
PC01	Red	20/01/2020
PC01	Blue	22/01/2020
PC02	Green	26/01/2020
PC03	Yellow	25/01/2020
PC03	Red	28/01/2020
PC04	Green	12/01/2020
PC04	Blue	24/01/2020
PC04	Red	28/01/2020

I want a screen showing this result

Title	Color	Modified
PC01	Blue	22/01/2020
PC02	Green	26/01/2020
PC03	Red	28/01/2020
PC04	Red	28/01/2020

The last modified entry of each PC

I did it with 4 galleries on the same screen showing the Last() and navigating into 4 DetailForms and 4EditForms it's not sexy (one for each PC01, PC02...)

Is that possible to doit wih only One Gallery, One DetailForm and EditForm ? 

[RandyHayes]

@Cyril06 

Can you reference what works fine?  The suggestion by @rsaikrishna or the solution I provided?

[Cyril06]

I have to do it from start to be sure I put the right names and all.

Can you tell me the difference between your solution and Rsaikrishna's solution ?

Is there one more acurate for one type of list or not ?

[Cyril06]

@RandyHayes  Sorry !!!! The Rsaikrishna's solution works fine but I'd like to make your working too because I want to progress in the powerapps I don't like to write something I do not understand.

(Even with the Forum I'm a mess !!!!)

[RandyHayes]

@Cyril06 

Yes, Rsaikrishna's solution involves a lot of hard-code names and collections and then having to maintain and refresh and update those collections as needed - and since in the OnVisible, having to duplicate the formula in other places you need or to return to the screen so the collection will refresh.

The one I provided you is dynamic, will update automatically based on your SharePoint list, requires no refresh or update, is dynamic to ANY Titles you have in your data source (not just PC01,2,3, and 4), requires no collections or duplication in other places.

But it is really all dependent on what you need.  If you need one over the other, then you can choose which works best.

[RandyHayes]

@Cyril06 

Can you explain to me what is not working?  What is the error you see or message you get or condition?  Please post the formula that you have that I provided (modified as you needed) and a screenshot of the situation.

[Cyril06]

@RandyHayes I'm working on it. I tried with my project so I want to clean it up before try again and in the spirit I prefer your dynamic solution becaus I will have many categories comming after.

So I make a new one and I'll tell you ASAP

But before many thanks to both of you @rsaikrishna  and @RandyHayes for your time and help

@RandyHayes I think I will choose the Randy's solution but with yours I learned some interesting things

[RandyHayes]

@Cyril06 

It's all part of the learning process.  @rsaikrishna shows some pretty cool concepts around collection manipulations.  This is fine in some cases.  My personal preference is to keep things simple and dynamic and easily maintainable.

That said, your need was actually pretty straight forward - and as you saw from the example I gave, works perfectly.

If it does not work in your scenario, then I am going to make an educated guess that your "Color" column is not a Text column but instead a Choice column.

The other factor is that when you introduced SharePoint to this, we need to modify the resultant column called "Modified" as your SharePoint list already has a column called "Modified".

In these cases you would use the following formula.

DropColumns(
    AddColumns(
        AddColumns(
            GroupBy(
                yourDataSource,
               "Title", "records"
            ),
            "recent", First(SortByColumns(records, "Modified", Descending))
        ),
        "Color", recent.Color.Value,  //Note: .Value here if this is a Choice column.  Don't change if not
        "modifiedDate", recent.Modified  //Note: this avoids impact with the SharePoint Modified column Name
    ),
    "records", "recemt"
)

To explain this, the very first thing that is done in this formula is the all of your records in your SharePoint list are Grouped by the "Title" column.  When you group by, you end up with a table that has (in this case) a column called "Title" which will be the unique values of Title.  The second parameter is what you want to call the resultant records of that grouping.  So, if you had 3 rows that had the title of "PC04", then you would have a table with a Title column with a value of "PC04".  That row will have another column (in the above case, called "records") that will contain the 20 rows that had that Title.

Now, with the grouping done, then next thing we do is Add a column to the results of the GroupBy.  I called that "recent" (for lack of a better name).  In the column, I am taking the first record of the sorted list of the records in the group in a descending order.  That will mean that the first record in that sort will be the most recent one...which is the one you want information from.

At this point (in the context of "PC04") we have a row in the results with a Title of "PC04" and a column called "records" with 3 rows in it and now we also have a column called "recent" that has the most recent record of those 3 rows.

Now, with the above, we add two more columns to the results.  One is the Color and it will contain the Color value of the 1 record that is most recent.  Then we add a "modifiedDate" column and it will contain the Modified date of the most recent record.

With all of that done, We have a row with a title of "PC04",  a column called "records" with 3 rows in it that were from the "PC04" title grouping, a "recent" column that will have 1 record from the "records" list that is most recent, a Color column that has the value of the most recent color, and a modifiedDate column that has the date of the most recent.

Finally, we enclose all of this in a DropColumns to remove the "records", and "recent" columns as we really do not need them any longer outside of the formula.

I hope that helps you understand it a little more.

[Cyril06]

@RandyHayes 😂🤣 you are too fast I was writing to you :

Ok my bad I didn't understand that I had to change the fields .... SORRY  !!!!!!!

So great it works fine no not great it's marvelous but now......

[rsaikrishna]

@Cyril06 

@RandyHayes solution is great. Thank you Randy for great explanation. 

Regards

Krishna Rachakonda

[Cyril06]

@RandyHayes I was writing the steps that you perfectly described thank you again ! but i'm too slow with my translation 😥 and sorry by the way for my spelling errors.

I'd like to see an other thing the entry of the Site column how should I put it into your process ?