Hello
I use V4CalendarPostItem to make an event on calendar but it should be register as UTC time.
As https://docs.microsoft.com/en-us/connectors/office365/#create-event-(v4),
start time and end time parameters are date-no-tz type. If I use data-no-tz(ie. '2017-08-29T04:00:00'),
the calendar event should be registered as UTC time zone. ( register time is correct but time zone is UTC)
I found a workaround to use DateTimeValue with locale to register own local time zone.
I don't understand the behavior of time zone mechanism of V4CalendarPostItem.
Register as UTC time zone but registered time is correct even it is UTC time zone.
Office365Outlook.V4CalendarPostItem(
G_CalendarID,
VarCalTitle,
VarCalStartTime,
VarCalEndTime,
"Tokyo Standard Time",
{
body: RichTextEditorBody.HtmlText,
showAs: GlbVar.ShowAs }
)
Register correctly as Tokyo Standard Time
Office365Outlook.V4CalendarPostItem(
G_CalendarID,
VarCalTitle,
DateTimeValue(VarCalStartTime,"ja-JP"),
DateTimeValue(VarCalEndTime,"ja-JP"),
"Tokyo Standard Time",
{
body: RichTextEditorBody.HtmlText,
showAs: GlbVar.ShowAs }
)
I
Solved! Go to Solution.
Hi @Anonymous ,
I think I have missed something with your Formula, you used Office365Outlook.V4CalendarPostItem(), but I used Office365Outlook.V2CalendarPostItem() function.
If you use Office365Outlook.V4CalendarPostItem() function to achieve your needs, I agree with you, you should modify your formula as below:
UpdateContext(
{
VarCalStartTime: Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnStartHr.Selected.Value),
Value(DrpDwnStartMnt.Selected.Value),
0
),
DateTimeFormat.UTC
),
VarCalEndTime: Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnEndHr.Selected.Value),
Value(DrpDwnEndMnt.Selected.Value),
0
),
DateTimeFormat.UTC
)
}
)
and
Office365Outlook.V4CalendarPostItem(
G_CalendarID,
VarCalTitle,
VarCalStartTime,
VarCalEndTime,
""(UTC+09:00) Osaka, Sapporo, Tokyo"", // Selected the specific time zone from the provided available options
{
body: RichTextEditorBody.HtmlText,
showAs: GlbVar.ShowAs
}
);
If you want to use Office365Outlook.V2CalendarPostItem() function, please try the following formula:
Office365Outlook.V2CalendarPostItem(
G_CalendarID,
VarCalTitle,
Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnStartHr.Selected.Value),
Value(DrpDwnStartMnt.Selected.Value),
0
),
"[$-ja]yyyy-mm-ddTHH:mm:ssZ"
),
Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnEndHr.Selected.Value),
Value(DrpDwnEndMnt.Selected.Value),
0
),
"[$-ja]yyyy-mm-ddTHH:mm:ssZ"
),
{
TimeZone: "(UTC+09:00) Osaka, Sapporo, Tokyo", // Selected the specific time zone from the provided available options
Body: RichTextEditorBody.HtmlText
}
);
Best regards,
Hi @Anonymous ,
Actually, it is an known issue with Office365Outlook.V4CalendarPostItem function. The Start Time and End Time of an event is actually a dateTimeTimeZone type, in default, the Start Time and End Time is in UTC format.
Please check the following article for more details about properties of an event:
https://docs.microsoft.com/en-us/graph/api/resources/event?view=graph-rest-1.0#properties
When you specify a date time value for the Start Time and End Time arguments in the V4CalendarPostItem function, you should specify the date time value in UTC format as below:
"2020-05-25T15:35:00Z" // yyyy-MM-ddTHH:mm:ssZ
I have made a test on my side, the standard formula format as below:
Office365Outlook.V2CalendarPostItem(
CalendarDropdown.Selected.Name,
SubjectBox.Text,
Text(StartDatePicker.SelectedDate + Time(Value(StartHour.Selected.Value), Value(StartMinute.Selected.Value),0), "[$-en-US]yyyy-mm-ddTHH:mm:ssZ"),
Text(EndDatePicker.SelectedDate + Time(Value(EndHour.Selected.Value), Value(EndMinute.Selected.Value),0), "[$-en-US]yyyy-mm-ddTHH:mm:ssZ"),
{
TimeZone:"(UTC+08:00) Kuala Lumpur, Singapore", // The value should be chosen from the available options
Body: BodyBox.Text
}
)
On your side, you should modify your formula as below:
Office365Outlook.V4CalendarPostItem(
G_CalendarID,
VarCalTitle,
Text(VarCalStartTime, "[$-en-US]yyyy-mm-ddTHH:mm:ssZ"), // Modify formula here
Text(VarCalEndTime, "[$-en-US]yyyy-mm-ddTHH:mm:ssZ"), // Modify formula here
"Tokyo Standard Time",
{
body: RichTextEditorBody.HtmlText,
showAs: GlbVar.ShowAs
}
)
Note: Use the Text function to format the date time value as a UTC format date time value string.
Best regards,
Hi、
Thank you for your response.
My actual code here for start and end time. I already define it as UTC format.
UpdateContext(
{
VarCalStartTime: Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnStartHr.Selected.Value),
Value(DrpDwnStartMnt.Selected.Value),
0
),
DateTimeFormat.UTC
),
VarCalEndTime: Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnEndHr.Selected.Value),
Value(DrpDwnEndMnt.Selected.Value),
0
),
DateTimeFormat.UTC
)
}
)
Then I confirmed the start/end variable as UTC format.
Hi,
As you mentioned manual of dateTimeTimeZone,
"start dateTimeTimeZone The date, time, and time zone that the event starts. By default, the start time is in UTC."
I suppose my code is also fine because
VarCalStartTime is defined as UTC format by Text()
Then VarCalStartTime is changed to dateTimeTimezone by DateTimeValue()
Hi @Anonymous ,
Based on the formula that you mentioned, I think there is something wrong with it. If you format the Start Time or End Time using the following formula:
Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnStartHr.Selected.Value),
Value(DrpDwnStartMnt.Selected.Value),
0
),
DateTimeFormat.UTC
)
it would convert your picked up date time value into a UTC time.
But the important thing you need to know is that -- when working date time value in canvas app, it would be converted into UTC format automatically. In other words, if you are in UTC + 7 time zone, and you picked up "05/25/2020 03:00 PM" date time value from your canvas app, when passing this date time value in your V4CalendarPostItem() function as Start Time or End Time, it would be converted into "05/25/2020 08:00 AM" date time automatically, and pass this converted date time value to your Outlook. Then based on the time zone attribute you specified in V4CalendarPostItem() function, the "05/25/2020 08:00 AM" date time value would be converted into corresponding Time Zone value. E.G. if you specify your own local time zone for the "time zone" attribute, the passed date time would be converted into your local time zone.
So you could not format your picked up date time value into UTC format manually using the following formula:
Text(...., DateTimeFormat.UTC)
If you passed above date time string value into your V4CalendarPostItem() function, it would be considered as your picked up date time value from your canvas app, and it would be converted into UTC time value again, then it would cause time zone issue (date time offset) when you create event in your Outlook.
On your side, please format the picked up date time value using the following formula:
Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnStartHr.Selected.Value),
Value(DrpDwnStartMnt.Selected.Value),
0
),
"yyyy-MM-ddTHH:mm:ssZ" // specify the format here
)
If the solution I provided above is helpful in your scenario, please consider go ahead to click "Accept as Solution" to identify this thread has been solved.
Best regards,
Hi
I changed the code as you mentioned. But it still be registered as UTC.
UpdateContext(
{
VarCalStartTime: Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnStartHr.Selected.Value),
Value(DrpDwnStartMnt.Selected.Value),
0
),
"[$-ja]yyyy-mm-ddTHH:mm:ssZ"
),
VarCalEndTime: Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnEndHr.Selected.Value),
Value(DrpDwnEndMnt.Selected.Value),
0
),
"[$-ja]yyyy-mm-ddTHH:mm:ssZ"
)
}
)
and
Office365Outlook.V4CalendarPostItem(
G_CalendarID,
VarCalTitle,
VarCalStartTime,
VarCalEndTime,
"Tokyo Standard Time",
{
body: RichTextEditorBody.HtmlText,
showAs: GlbVar.ShowAs }
)
What's is wrong ???
Hi @Anonymous ,
I think I have missed something with your Formula, you used Office365Outlook.V4CalendarPostItem(), but I used Office365Outlook.V2CalendarPostItem() function.
If you use Office365Outlook.V4CalendarPostItem() function to achieve your needs, I agree with you, you should modify your formula as below:
UpdateContext(
{
VarCalStartTime: Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnStartHr.Selected.Value),
Value(DrpDwnStartMnt.Selected.Value),
0
),
DateTimeFormat.UTC
),
VarCalEndTime: Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnEndHr.Selected.Value),
Value(DrpDwnEndMnt.Selected.Value),
0
),
DateTimeFormat.UTC
)
}
)
and
Office365Outlook.V4CalendarPostItem(
G_CalendarID,
VarCalTitle,
VarCalStartTime,
VarCalEndTime,
""(UTC+09:00) Osaka, Sapporo, Tokyo"", // Selected the specific time zone from the provided available options
{
body: RichTextEditorBody.HtmlText,
showAs: GlbVar.ShowAs
}
);
If you want to use Office365Outlook.V2CalendarPostItem() function, please try the following formula:
Office365Outlook.V2CalendarPostItem(
G_CalendarID,
VarCalTitle,
Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnStartHr.Selected.Value),
Value(DrpDwnStartMnt.Selected.Value),
0
),
"[$-ja]yyyy-mm-ddTHH:mm:ssZ"
),
Text(
DatePickerWorkDay.SelectedDate + Time(
Value(DrpDwnEndHr.Selected.Value),
Value(DrpDwnEndMnt.Selected.Value),
0
),
"[$-ja]yyyy-mm-ddTHH:mm:ssZ"
),
{
TimeZone: "(UTC+09:00) Osaka, Sapporo, Tokyo", // Selected the specific time zone from the provided available options
Body: RichTextEditorBody.HtmlText
}
);
Best regards,
Hi
Yes. I use V4 function.
I understand my code is right.
Thanks a lot.
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