Hello everyone,
I am currently developing an app to edit fields in a SharePoint list. The list contains a first column called "Parcela" in which each row represents a specific plot number, and the rest of the columns are titled after each month of the year.
(The plot numbering is not always consecutive, there are gaps such as for example 1233, 1234, 1241, 1242, 1245, 1300, etc.)
The app consists of a first screen called "BrowseScreen1", where there is a gallery called "BrowseGallery1". This gallery contains each plot number, and when you click on a button associated with it, it takes you to the "EditScreen1" screen, where the plot number appears as the title and a text field for editing the information for each month of the year.
What I want to do is implement a new icon on the "EditScreen1" screen that, when clicked, takes me to the same "EditScreen1" screen but for the next item in the list, which would be the next plot number.
I have tried many ways but nothing works for me. I have read many similar cases here but I am not able to apply the solutions to my specific case. I am very newb in this.
Can anyone please help me with this issue? Any guidance or suggestions would be greatly appreciated.
Thank you!
Solved! Go to Solution.
Hi @DdVill,
You are using the ; syntax instead of , - this is dependent on the browser settings. This means that within my code all commas should be replaced with a semicolon and all semicolons with a double semicolon:
Set(varSelectedRecord; ThisItem);; Navigate(DetailScreen1; ScreenTransition.None)
Unfortunately due to the plot number being defined as a text field, we are receiving a delegation warning (number field would not have given a delegation warning). Should your list not become bigger than 2000 records, this is not something to worry about and you could just add the code below:
Set(
varSelectedRecord;
//Give me the first record
First(
//Sort by Plot number Ascending (closest value to our current number)
Sort(
//Only show me records with a higher plot number
Filter(
//Change listname
LISTNAME;
Value(Parcela) > Value(varSelectedRecord.Parcela)
);
Value(Parcela);
Ascending
)
)
)
Should the 2000 record limit be an issue, we will have to look at ways to 'prefilter' the data (to get it below 2000 records) and then filter by Parcela on that reduced dataset. You could filter by date (e.g. the date should be later than the selected record) or certain columns should match between the current selected record and the next one. The possible filter condition highly depends on your datamodel, but the aim is to reduce the filtered list to below 2000 records.
In my example below I will prefilter the dataset by only looking at rows that were created after the current selected plot number:
With(
{
//Change LISTNAME
//Change Date > varSelectedRecord.Date to a valid condition in your datamodel
filteredList: Filter(LISTNAME, Date > varSelectedRecord.Date)
};
Set(
varSelectedRecord;
//Give me the first record
First(
//Sort by Plot number Ascending (closest value to our current number)
Sort(
//Only show me records with a higher plot number
Filter(
//do not change filteredList
filteredList;
Value(Parcela) > Value(varSelectedRecord.Parcela)
);
Value(Parcela);
Ascending
)
)
)
)
Note: by default the data row limit will be 500, you can change this to up to 2000 within the app settings.
If this solves your question, would you be so kind as to accept it as a solution.
Thanks!
Hi @DdVill,
Let's take a look at a possible solution, step by step. It looks like you are using the app that is generated from data, which is good, but will need some extra steps to make this work.
(1) Let's change how the Form record is filled
Navigate to the BrowseScreen and select the Gallery control. Go to the OnSelect of this control and you will probably see the formula 'Navigate(DetailScreen1, ScreenTransition.None)'. Let's adjust this first:
Set(varSelectedRecord, ThisItem); Navigate(DetailScreen1, ScreenTransition.None)
Navigate to your DetailScreen & EditScreen and change the item property of the Forms. By default it will have code similar to 'BrowseGallery1.Selected'. Change this to varSelectedRecord
(don't forget to do this for both the detail and edit screen)
(2) Let's add the logic to the new icon on your edit screen
Here I expect the plot numbering column to be a number field. With the variables in place, we can now change the displayed item dynamically by overwriting the current value with a new one. This will be done by adding logic to the OnSelect of the icon. Below I will show you the general architecture of the code, please adjust the list / column names according to your specific case:
Set(
varSelectedRecord,
//Give me the first record
First(
//Sort by Plot number Ascending (closest value to our current number)
Sort(
//Only show me records with a higher plot number
Filter(
//Change listname
LISTNAME,
Parcela > varSelectedRecord.Parcela
),
Parcela,
Ascending
)
)
)
When clicking the icon, the Form item should change to the next plot number.
If this solves your question, would you be so kind as to accept it as a solution.
Thanks!
Hello @LaurensM ,
First of all I want to thank you for taking your time to answer my inquiry. You explined it very good and I was able to understand everything and apply it to my case.
Unfortunately, the solution didn't work but I think it is close to work.
In my app, there is no DetailScreen. From BrowseScreen you can only go to EditScreen. I don't know if this is the problem.. so in the first step i wrote
Set(varSelectedRecord; ThisItem)&&Navigate(EditForm1;ScreenTransition.None)
Take note that in my region the character "," is invalid so we use ";" between arguments. Also, we cannot use ";" to use a second action function, I wrote "&" or "&&". I don't know if that is the equivalence but it seems to work.
Then I changed the item property of EditForm1 to varSelectedRecord.
When editing OnSelect property of the icon I get the next warning:
Incidence
Delegation Warning. The "Filter" part of this formula may not work correctly on large data sets.
The data source may not be able to process the formula and return an incomplete data set. The application may not return correct results or may not behave correctly if the data set is incomplete.
Location
Icon3
.OnSelect
How to correct errors
If the dataset exceeds the limit of 500 records, but contains less than 2000, try resetting the limit.
Try simplifying the formula.
Try moving the data to another data source.
Article: Understanding Delegation in a Canvas Application
Blog: Data Row Limits for Delegation
Edit: There are 5 elements on the list of plots which are text because they make reference to a certain areas. Could that also cause some problems? Because when I write Parcela on your code it gives me an error. Invalid argument: expecting Number, Date, Time, DateTime.
Thank you again.
Hi @DdVill,
You are using the ; syntax instead of , - this is dependent on the browser settings. This means that within my code all commas should be replaced with a semicolon and all semicolons with a double semicolon:
Set(varSelectedRecord; ThisItem);; Navigate(DetailScreen1; ScreenTransition.None)
Unfortunately due to the plot number being defined as a text field, we are receiving a delegation warning (number field would not have given a delegation warning). Should your list not become bigger than 2000 records, this is not something to worry about and you could just add the code below:
Set(
varSelectedRecord;
//Give me the first record
First(
//Sort by Plot number Ascending (closest value to our current number)
Sort(
//Only show me records with a higher plot number
Filter(
//Change listname
LISTNAME;
Value(Parcela) > Value(varSelectedRecord.Parcela)
);
Value(Parcela);
Ascending
)
)
)
Should the 2000 record limit be an issue, we will have to look at ways to 'prefilter' the data (to get it below 2000 records) and then filter by Parcela on that reduced dataset. You could filter by date (e.g. the date should be later than the selected record) or certain columns should match between the current selected record and the next one. The possible filter condition highly depends on your datamodel, but the aim is to reduce the filtered list to below 2000 records.
In my example below I will prefilter the dataset by only looking at rows that were created after the current selected plot number:
With(
{
//Change LISTNAME
//Change Date > varSelectedRecord.Date to a valid condition in your datamodel
filteredList: Filter(LISTNAME, Date > varSelectedRecord.Date)
};
Set(
varSelectedRecord;
//Give me the first record
First(
//Sort by Plot number Ascending (closest value to our current number)
Sort(
//Only show me records with a higher plot number
Filter(
//do not change filteredList
filteredList;
Value(Parcela) > Value(varSelectedRecord.Parcela)
);
Value(Parcela);
Ascending
)
)
)
)
Note: by default the data row limit will be 500, you can change this to up to 2000 within the app settings.
If this solves your question, would you be so kind as to accept it as a solution.
Thanks!
It worked! Just after adding Value(Parcela). I had to remove the elements of the list which are not numbers because words cannot be se as numbers (which is obvious lol). Also I changed the limit to 2000.
And it is working now! Thank you so so much, you are a star!
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 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
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