Bad Gateway error on Event update in SharePoint with SubmitForm with time portion of just one date changed

[tdegler]

Hey Community!

My Power App connects to SharePoint classic Event list.

This list has 1 choice column added, and Recurrence and All day columns hidden.

Simple canvas app was generated with a lot of customization, but EditForm is almost untouched (I can introduce default EditForm as well to reproduce the same effect).

Now, using app change event date and submit form - no problem.

Change only Time (hour or minutes) in 'Start Time' [EventDate] (without any changes to 'End Time'), and hit SubmitForm and whole 'End Time' datetime disappears from record (in SharePoint version history I can see that 'End Time' was posted as empty but it wasn't touched in Power App).

and Change only Time (hour or minutes) in 'End Time' [EndDate] (without any changes to 'Start Time'), and SubmitForm will fail with "Bad Gateway" Error, and no update is done.

I have tried a lot of different workarounds, and would love to stay with SubmitForm instead of switching to Patch completely.

Any ideas please?

[danielbazetto]

Hi @tdegler 

Do you have screenshots that you could use to provide more clarity in what is the issue? I am still not sure if I understood correctly.

[tdegler]

Hi Daniel,

sure, I'll try my best:

Here is my form, connected to SharePoint event list:

You can generate this form with Power App with no modifications and you will be able to replicate error.

1. edit event

2. on the form change h2 (I am changing to 2 hours later) without changing h1 or anything else

3. submit form.

4. it will take some time, and Power App spits an error:

Hope it helps.

[WarrenBelz]

Hi @tdegler ,

This is nothing to do with the hour fields unless you have modified the Update property of the Data Card containing these. I use start and finish date/times on a number of apps and they work as designed.

Try making two new date/time field and doing the same with them - if you get no errors, you probably have a corruption in one of the two existing fields in the data source.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[tdegler]

1.  As stated in my post - hour fields are "out of the box" (you may translate it to "not modified")

2. I have tried already with "new" data fields.

3. This error is replicable across o365 tenants.

Maybe it is important - both tenants have default SharePoint site language set to Dutch.

Workstations have default language set to us, with french locale.

[WarrenBelz]

Hi @tdegler ,

I suggest you lodge a Support Ticket with Microsoft 

This may be a region-based issue as I cannot replicate it (Australia).

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[tdegler]

Thank you.

Today I was able to replicate that error on another tenant and my collegue reported able to replicate as well on another.

I have experimented as well with different locale settings on workstation and it produces the error 100% times with no change.

@danielbazetto were my explanations clear?

[danielbazetto]

Hi @tdegler ,

I believe that in this Bad Gateway situation it is better to raise a support request with Microsoft as @WarrenBelz also suggested.

So you could provide more sensitive information as network trace, the session id and so on. Perhaps due to my delay on this reply you already raised a support request.

[edguerre]

@tdegler and other users in this thread

I have discussed this internally, and the official statement is that the SPO connector is not supposed to support Calendar lists - this is why it does not show up when you connect to data sources when creating the app.

Because of this, the suggestions are to either:

- Use standard lists to achieve this same goal,

- Adapt your app code in order to, when only one of the fields is filled in, force the app to Patch both values into the calendar. This should resolve the issue as well.

Thanks all for the patience on this one.