cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
gymcode
Post Partisan
Post Partisan

Date Calculation Incorrect During Patch() Formulas in Published Mode

I have a Patch() function that create 1 parent 'Reservation' record, and multiple child 'Reservation Details' records, and it skips weekends and a collection of holiday dates.

When I am executed Patch() function in Editing mode, both 'Reservation and 'Reservation Details' records were created on the correct days (weekdays).

However, when the app is published, 'Reservation Details' records created there was incorrect (1 day behind).

Scenario

- FromDate_Datepicker : Mon (05 Feb 2024)
- ToDate_Datepicker = Sun (11 Feb 2024)

 05 Feb06 Feb07 Feb08 Feb 09 Feb10 Feb11 Feb
 MonTueWedThuFriSatSun
Editing ModeCreatedCreatedCreatedCreatedCreatedSkippedSkipped
Published ModeSkippedCreatedCreatedCreatedCreatedCreatedSkipped
Published Mode is 1 day behind*Sun*Mon*Tue*Wed*Thu*Fri*Sat


Based on the results above, Published Mode is 1 day behind Editing Mode.

Question: May I know how can I resolve this, and is a code change to fix this possible?

Thank you.
_____________________________________________________________________________________

Below is my full Patch() function:

 

//Creates 1x parent 'Reservation' record
If(
    BookingType_Self_Cb.Checked,
    ClearCollect(
        ReservationRecord,
        Patch(
            Reservations,
            Defaults(Reservations),
            {
                'Start Date': FromDate_Dp.Value,
                'End Date': ToDate_Dp.Value,
                'Reserved For': 'Reserved For (Reservations)'.Employee,
                Facility: Building_Ddl.Selected,
                Area: Area_Ddl.Selected,
                'Employee Name': Self_Section_EmployeeName_Ddl.Selected,
                'Reserved Desk': Self_Section_Seat_Ddl.Selected,
                'Booked By': Self_Section_EmployeeName_Ddl.Selected
            }
        )
    )
);
// Store created parent 'Reservation' record in a variable 'newReservationRecord'
Set(
    newReservationRecord,
    First(ReservationRecord)
);

//Create 'Reservation Details' record for each date and associated it with 'Reservation' record created by 'Reservation Details'.'Reservation'
//Only create records if date matches weekdayt dates in WeekdayDates collection
Patch(
    'Reservation Details',
    ForAll(
        Sequence(
            DateDiff(
                FromDate_Dp.Value,
                ToDate_Dp.Value,
                TimeUnit.Days
            ) + 1
        ),
        With(
            {
                _Date: DateAdd(
                    FromDate_Dp.Value,
                    Value - 1,
                    TimeUnit.Days
                )
            },
            If(
                _Date in WeekdayDates,
                {
                    Date: _Date,
                    Reservation: newReservationRecord,
                    Name: newReservationRecord.'Reservation ID' & "_" & _Date,
                    'Reserved Desk': newReservationRecord.'Reserved Desk'
                }
            )
        )
    )
);

 

 
- 'Reservations'.'Start Date' is correct
- 'Reservations'.'End Date' is correct
- 'Reservation Details'.'Date' is wrong

24 REPLIES 24

// Creates 1x parent 'Reservation' record
If(
    BookingType_Self_Cb.Checked,
    ClearCollect(
        ReservationRecord,
        Patch(
            Reservations,
            Defaults(Reservations),
            {
                'Start Date': FromDate_Dp.Value,
                'End Date': ToDate_Dp.Value,
                'Reserved For': 'Reserved For (Reservations)'.Employee,
                Facility: Building_Ddl.Selected,
                Area: Area_Ddl.Selected,
                'Employee Name': Self_Section_EmployeeName_Ddl.Selected,
                'Reserved Desk': Self_Section_Seat_Ddl.Selected,
                'Booked By': Self_Section_EmployeeName_Ddl.Selected
            }
        )
    )
);

// Store created parent 'Reservation' record in a variable 'newReservationRecord'
Set(
    newReservationRecord,
    First(ReservationRecord)
);

// Create 'Reservation Details' record for each date and associate it with 'Reservation' record
Patch(
    'Reservation Details',
    ForAll(
        WeekdayDates,
        If(
            Value >= FromDate_Dp.Value && Value <= ToDate_Dp.Value,
            Collect(
                ReservationDetailsCollection,
                {
                    Date: Value,
                    Reservation: newReservationRecord,
                    Name: newReservationRecord.'Reservation ID' & "_" & Text(Value, "[$-en-US]yyyy-mm-dd"),
                    'Reserved Desk': newReservationRecord.'Reserved Desk'
                }
            )
        )
    )
);

 

looks like so, lol

Hi @mmbr1606 , thanks for the formula. I reverted back to classic datepicker control and tried to use tis code, but received a similar error, that it cannot use a non-record value in this context.

gymcode_0-1706276279856.png

// Creates 1x parent 'Reservation' record
If(
    BookingType_Self_Cb.Checked,
    ClearCollect(
        ReservationRecord,
        Patch(
            Reservations,
            Defaults(Reservations),
            {
                'Start Date': FromDate_Dp.Value,
                'End Date': ToDate_Dp.Value,
                'Reserved For': 'Reserved For (Reservations)'.Employee,
                Facility: Building_Ddl.Selected,
                Area: Area_Ddl.Selected,
                'Employee Name': Self_Section_EmployeeName_Ddl.Selected,
                'Reserved Desk': Self_Section_Seat_Ddl.Selected,
                'Booked By': Self_Section_EmployeeName_Ddl.Selected
            }
        )
    )
);
// Store created 'Reservation' record in a variable 'newReservationRecord'
Set(
    newReservationRecord,
    First(ReservationRecord)
);


// Create 'Reservation Details' record for each date and associate it with 'Reservation' record
Patch(
    'Reservation Details',
    ForAll(
        WeekdayDates,
        If(
            Value >= FromDate_Dp.Value && Value <= ToDate_Dp.Value,
            Collect(
                ReservationDetailsCollection,
                {
                    Date: Value,
                    Reservation: newReservationRecord,
                    Name: newReservationRecord.'Reservation ID' & "_" & Text(Value, "[$-en-US]yyyy-mm-dd"),
                    'Reserved Desk': newReservationRecord.'Reserved Desk'
                }
            )
        )
    )
);

 

hey @gymcode 

 

maybe this modification helps solving the issue stated in your last post:

 

// Creates 1x parent 'Reservation' record
If(
    BookingType_Self_Cb.Checked,
    ClearCollect(
        ReservationRecord,
        Patch(
            Reservations,
            Defaults(Reservations),
            {
                'Start Date': FromDate_Dp.Value,
                'End Date': ToDate_Dp.Value,
                'Reserved For': 'Reserved For (Reservations)'.Employee,
                Facility: Building_Ddl.Selected,
                Area: Area_Ddl.Selected,
                'Employee Name': Self_Section_EmployeeName_Ddl.Selected,
                'Reserved Desk': Self_Section_Seat_Ddl.Selected,
                'Booked By': Self_Section_EmployeeName_Ddl.Selected
            }
        )
    )
);

// Store created parent 'Reservation' record in a variable 'newReservationRecord'
Set(
    newReservationRecord,
    First(ReservationRecord)
);

// Create 'Reservation Details' record for each date and associate it with 'Reservation' record
ForAll(
    Filter(
        WeekdayDates,
        Value >= FromDate_Dp.Value && Value <= ToDate_Dp.Value
    ),
    Collect(
        ReservationDetailsCollection,
        {
            Date: Value,
            Reservation: newReservationRecord,
            Name: newReservationRecord.'Reservation ID' & "_" & Text(Value, "[$-en-US]yyyy-mm-dd"),
            'Reserved Desk': newReservationRecord.'Reserved Desk'
        }
    )
)

 

Let me know if my answer helped solving your issue.

If it did please accept as solution and give it a thumbs up so we can help others in the community.



Greetings

Hi @mmbr1606, thank you for the formula. There is no error now, but I realized the Patch() formula is missing, so the 'Reservation Details' records weren't created 😅

gymcode
Post Partisan
Post Partisan

Appreciate your asisstance @mmbr1606. In the meantime, I'll be using the original query, but -1 from the date value.

// Create 'Reservation Details' record for each date and associate it with 'Reservation' record
Patch(
    'Reservation Details',
    ForAll(
        Sequence(
            DateDiff(
                FromDate_Dp.Value,
                ToDate_Dp.Value,
                TimeUnit.Days
            ) + 1
        ),
        With(
            {
                _Date: DateAdd(
                    FromDate_Dp.Value,
                    Value - 1,
                    TimeUnit.Days
                )
            },
            If(
                _Date in WeekdayDates,
                {
                    Date: _Date-1,   <<---- Temporary workaround
                    Reservation: newReservationRecord,
                    Name: newReservationRecord.'Reservation ID' & "_" & _Date,
                    'Reserved Desk': newReservationRecord.'Reserved Desk'
                }
            )
        )
    )
);

 
So at least users who are using the app will have the correct dates. 

in the code above the patch is included

 

here again:

 

// Create 1x parent 'Reservation' record
If(
    BookingType_Self_Cb.Checked,
    ClearCollect(
        ReservationRecord,
        Patch(
            Reservations,
            Defaults(Reservations),
            {
                'Start Date': FromDate_Dp.Value,
                'End Date': ToDate_Dp.Value,
                'Reserved For': 'Reserved For (Reservations)'.Employee,
                Facility: Building_Ddl.Selected,
                Area: Area_Ddl.Selected,
                'Employee Name': Self_Section_EmployeeName_Ddl.Selected,
                'Reserved Desk': Self_Section_Seat_Ddl.Selected,
                'Booked By': Self_Section_EmployeeName_Ddl.Selected
            }
        )
    )
);

// Store created parent 'Reservation' record in a variable 'newReservationRecord'
Set(
    newReservationRecord,
    First(ReservationRecord)
);

// Create 'Reservation Details' record for each date and associate it with 'Reservation' record
ForAll(
    Filter(
        WeekdayDates,
        Value >= FromDate_Dp.Value && Value <= ToDate_Dp.Value
    ),
    Patch(
        'Reservation Details',
        {
            Date: Value,
            Reservation: newReservationRecord,
            Name: newReservationRecord.'Reservation ID' & "_" & Text(Value, "[$-en-US]yyyy-mm-dd"),
            'Reserved Desk': newReservationRecord.'Reserved Desk'
        }
    )
)

 

Let me know if my answer helped solving your issue.

If it did please accept as solution and give it a thumbs up so we can help others in the community.



Greetings

oh you mean at the bottom,

 

see my code above

Hi @mmbr1606 , thanks for the updated formula.

I am able to execute the formula successfully now, but in Published mode, the date time is still showing the same behaviour of being 1 day off 😩

good to hear that but also bad hmmm

 

you are using sharepoint as a datasource? if yes, sometimes it can take a bit longer till SP has the right version of the app.

 

sorry stupid question, but did you save/publish and click the new version when u opend the app in production? in the editing sudio it is working and showing the right values?

 

Let me know if my answer helped solving your issue.

If it did please accept as solution and give it a thumbs up so we can help others in the community.



Greetings

my datasource is within CRM itself. I am in Sandbox environment, yet to deploy to Production. 

In editing studio, yes, it is working and showing correct values.

It is just in published mode, in the page's direct URL, the created record dates are off.

It's also only specific to 'Reservation Detail'.'Date' value. Other date values in 'Reservation' entity is correct, such as 'Reservation'.'Start Date' and 'Reservation'.'End Date'.

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

Users online (720)