Hello Everyone,
I am having trouble with ForAll statement.
I am building a time entries application.
When the employee edits the timesheet, if the record already exists, the system should update the record as per the changes made by the employee; if the record did not exist, the system should add the record. This is the code i am using:
ForAll(
galleryTimeEdit.AllItems,
If(IsBlank('Timesheet ID'),
Patch(
[@'Timesheet_Entries_T'],
Defaults([@'Timesheet_Entries_T']),
{
'Employee Name': User().FullName,
Email: User().Email,
WeekEnding: DateTimeValue(DateToLbl_1.Text),
'Level 1 Approval Status': "Pending",
Monday: Value(MonIn_1.Text),
Tuesday: Value(TueIn_1.Text),
Wednesday: Value(WedIn_1.Text),
Thursday: Value(ThuIn_1.Text),
Friday: Value(FriIn_1.Text),
Saturday: Value(SatIn_1.Text),
Sunday: Value(SunIn_1.Text),
'Project Name': ProjectCB.Selected.'Project Name',
}
),
Patch(
[@'Timesheet_Entries_T'],
{'Timesheet ID':'Timesheet ID'},
{
'Employee Name': User().FullName,
Email: User().Email,
WeekEnding: DateTimeValue(DateToLbl_1.Text),
'Level 1 Approval Status': "Pending",
Monday: Value(MonIn_1.Text),
Tuesday: Value(TueIn_1.Text),
Wednesday: Value(WedIn_1.Text),
Thursday: Value(ThuIn_1.Text),
Friday: Value(FriIn_1.Text),
Saturday: Value(SatIn_1.Text),
Sunday: Value(SunIn_1.Text),
'Project Name': ProjectCB.Selected.'Project Name',
}
)));
The result i am gettting is duplication of records. Looks like the code is just patching as new records than updating with existing record.
Can you please help?
Does galleryTimeEdit have a field (label) showing or hidden for Timesheet ID? When using a gallery as a reference you must include the fields you need in the gallery - they cannot just be part of the data source sitting behind the gallery.
Another thing you could try is disambiguation using 'As', for example
ForAll(
galleryTimeEdit.AllItems As _myPatch,
If(IsBlank('Timesheet ID'),
Patch(
[@'Timesheet_Entries_T'],
Defaults([@'Timesheet_Entries_T']),
{
'Employee Name': User().FullName,
Email: User().Email,
WeekEnding: DateTimeValue(_myPatch.DateToLbl_1.Text),
'Level 1 Approval Status': "Pending",
Monday: Value(_myPatch.MonIn_1.Text),
... and so on
I see where the issue may be occurring in your PowerApps formula.
The ForAll function in PowerApps is intended to be used to evaluate a formula for all records of a table.
It is not the same as the 'For' loop in traditional coding.
In this scenario, the ForAll function should not be used as a loop to Patch data to your data source but should be used when you want to perform operations on all items in a collection or a table and you want to return a table as result.
The reason you're probably seeing duplicates is that the Patch function is executed for every record in the 'galleryTimeEdit.AllItems'. This means that for every record, it's either creating a new entry (when 'Timesheet ID' is blank) or updating an existing entry (when 'Timesheet ID' exists). However, the condition to update an existing record is not accurately captured in your current formula.
Specifically, If(IsBlank('Timesheet ID') doesn't really make any sense and I don't think you are accurately capturing this condition. Besides this, that whole condition should be moved into a two argument version of patch, and perform the If only on the primary key, to avoid repetition of the entire thing. Patch inside ForAll is also a bad idea, Patch should be outside the ForAll.
Here is an improved version of your formula:
Patch(
[@'Timesheet_Entries_T'],
ForAll(
galleryTimeEdit.AllItems,
{
'Timesheet ID': If(IsBlank(ThisRecord.'Timesheet ID'), Blank(), ThisRecord.'Timesheet ID'),
'Employee Name': User().FullName,
Email: User().Email,
WeekEnding: DateTimeValue(DateToLbl_1.Text),
'Level 1 Approval Status': "Pending",
Monday: Value(MonIn_1.Text),
Tuesday: Value(TueIn_1.Text),
Wednesday: Value(WedIn_1.Text),
Thursday: Value(ThuIn_1.Text),
Friday: Value(FriIn_1.Text),
Saturday: Value(SatIn_1.Text),
Sunday: Value(SunIn_1.Text),
'Project Name': ProjectCB.Selected.'Project Name'
}
)
)
Replace 'Timesheet ID' above with the actual name of the column that is your primary key of that Timesheet Entries table of your data source.
Make sure the setting "Formula-level error management" is turned on in your Power Apps (for fairly recent Power Apps this should be on by default) or else it may not know when to create the new values using Blank() for signaling to patch to create a new one instead of modify an existing one, as patching blank value is not allowed with that setting off.
Actually, in the above, If(IsBlank(ThisRecord.'Timesheet ID'), Blank(), ThisRecord.'Timesheet ID') doesn't make that much sense, as that condition should never be true, no blank primary key should be possible for record of your gallery.
So just replace this line with just ThisRecord.'Timesheet ID'. ThisRecord is the current record from the ForAll, is what ThisRecord means. Then even if "Formula-level error management" is turned off it may not matter then.
See if it helps @Sham07
Hello, I tried your solution but the same error:
Timesheet ID is a primary column in Timesheet entries table. I am not able to pull into the gallery. So created an auto generated number in the timesheet entries table " AutoTest".
This is my code now:
ForAll(
galleryTimeEdit.AllItems As _myPatch,
If(IsBlank(_myPatch.AutoTest),
Patch(
[@'Timesheet_Entries_T'],
Defaults([@'Timesheet_Entries_T']),
{
'Employee Name': User().FullName,
Email: User().Email,
WeekEnding: DateTimeValue(DateToLbl_1.Text),
Monday: Value(_myPatch.MonIn_1.Text),
Tuesday: Value(_myPatch.TueIn_1.Text),
Wednesday: Value(_myPatch.WedIn_1.Text),
Thursday: Value(_myPatch.ThuIn_1.Text),
Friday: Value(_myPatch.FriIn_1.Text),
Saturday: Value(_myPatch.SatIn_1.Text),
Sunday: Value(_myPatch.SunIn_1.Text),
'Project Name': _myPatch.ProjectCB_1.Selected.'Project Name',
}
),
Patch(
[@'Timesheet_Entries_T'],
{AutoTest:_myPatch.AutoTest},
{
'Employee Name': User().FullName,
Email: User().Email,
WeekEnding: DateTimeValue(DateToLbl_1.Text),
Monday: Value(_myPatch.MonIn_1.Text),
Tuesday: Value(_myPatch.TueIn_1.Text),
Wednesday: Value(_myPatch.WedIn_1.Text),
Thursday: Value(_myPatch.ThuIn_1.Text),
Friday: Value(_myPatch.FriIn_1.Text),
Saturday: Value(_myPatch.SatIn_1.Text),
Sunday: Value(_myPatch.SunIn_1.Text),
'Project Name': _myPatch.ProjectCB_1.Selected.'Project Name',
}
)));
@Sham07 For optimization purposes Power Apps is not guaranteed to return all rows in a Gallery and loads them in iteratively as you scroll. So Gallery.AllItems may not return all your records.
You can use a Collection however note that whether your function is delegable or not, a single function call e.g. ClearCollect can only return at most the record limit (500 by default, raise-able to max of 2,000).
A non-delegable function on your innermost Filter for example will be inaccurate on a large data set say 10,000 because it will process the first 2,000 only and stop there. However, even a delegable Filter (or any other delegable function of any kind), while more accurate here, while it may process beyond the 2,000th record on the data source side, will still return only the 1st 2,000 processed records, stopping on whichever is the 2,000th filtered one. Keep this in mind.
No escape is possible from the record limit. Design so it returns less than record row limit.
Remember it's record limit per function call.
It's possible to use tricks like batching to go beyond this limit, but it's not recommend, as large collection sizes may be bad for performance, and except in a few select cases, may be a sign of not using Power Apps correctly.
@Sham07 What's your error?
What's being duplicated exactly?
Again, using ForAll outside of Patch increases the likelihood of you getting that error exponentially, and it is also bad for performance and ForAll is not a for development loop.
I am getting duplicate rows.
This is a timesheet entry application. So, at most an employee will be retrieving not more than 25 lines of data for a particular week. So, delegation should not be an issue.
Here is the code now as per your suggestion:
Patch(
[@'Timesheet_Entries_T'],
ForAll(
galleryTimeEdit.AllItems,
{
'Timesheet ID': If(IsBlank(ThisRecord.'Timesheet ID'), Blank(), ThisRecord.'Timesheet ID'),
'Employee Name': User().FullName,
Email: User().Email,
'Position Title': PositionTtle_txt_1.Text,
WeekEnding: DateTimeValue(DateToLbl_1.Text),
'Approval Status': "Submitted for Approval",
'Level 1 Approval Status': "Pending",
Monday: Value(MonIn_1.Text),
Tuesday: Value(TueIn_1.Text),
Wednesday: Value(WedIn_1.Text),
Thursday: Value(ThuIn_1.Text),
Friday: Value(FriIn_1.Text),
Saturday: Value(SatIn_1.Text),
Sunday: Value(SunIn_1.Text),
Notes: NotesIn_1.Text,
'Project Name': ProjectCB_1.Selected.'Project Name',
}
));
'Timesheet ID': If(IsBlank(ThisRecord.'Timesheet ID'), Blank(), ThisRecord.'Timesheet ID'), should be just ThisRecord.'Timesheet ID' because no timesheet id should be blank.
See below. If you get an error with the below, you have a blank timesheet ids on some records in the Gallery - which is odd and you may have to double check why that is. You may need to use ShowColumns on the Gallery or somewhere to show the id in the Gallery side like in this recent similar issue: Row id hidden from data table, how to use it for form
Patch(
[@'Timesheet_Entries_T'],
ForAll(
galleryTimeEdit.AllItems,
{
'Timesheet ID':ThisRecord.'Timesheet ID',
'Employee Name': User().FullName,
Email: User().Email,
'Position Title': PositionTtle_txt_1.Text,
WeekEnding: DateTimeValue(DateToLbl_1.Text),
'Approval Status': "Submitted for Approval",
'Level 1 Approval Status': "Pending",
Monday: Value(MonIn_1.Text),
Tuesday: Value(TueIn_1.Text),
Wednesday: Value(WedIn_1.Text),
Thursday: Value(ThuIn_1.Text),
Friday: Value(FriIn_1.Text),
Saturday: Value(SatIn_1.Text),
Sunday: Value(SunIn_1.Text),
Notes: NotesIn_1.Text,
'Project Name': ProjectCB_1.Selected.'Project Name',
}
)
);
The blank timesheet IDs are when the employee is creating a new line item in the application and is not appended in the table yet.
As far as i am progress is the same: New rows are created rather than updating the records if it is already present in the table.
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