BUG - SharePoint Forms Not Loading after Publishing since 6/19/2018

[skylitedave]

I have a powerapp form associated with a sharepoint list that will not load after publishing since 6/18/2018.  Seems like it started happening when I started to see the spinner for loading.  I cannot make any changes and must roll back to a version published  5/7/2018.  Loads fine in studio but will not load when a user clicks on sharepoint list link.

Will not load in ANY browser after publishing as of Monday

Opened support Ticket #10568162  since no response yesterday using this board

[dixonthunder]

Session ID: 163fc44a-bb50-4fa4-b4ea-5db1ff09d300
PowerApps 3.18062.24

[CWesener]

Thanks all - our team are in the process of investigating this issue, I'll provide updates as soon as they are available.

Thanks,

Clay.

[sarafankit]

We have identified the issue are in the process of preparing a fix for this. This issue only happens if your custom form has a formula which accesses data in OnStart event. As a temporary workaround, you can move the formula from OnStart to SharePointIntegration.OnView/OnEdit/OnNew events.

We expect the fix to be released by end of day today/early tomorrow morning.

[ericonline]

@sarafankit, @CWesener, 

I'm preparing to rollout a PowerApp to ~700 internal users. When there are issues like the one brought up in this post, what is the protocol for: 

• Debugging on our end
• Reporting to Microsoft

There is no information that I could find in the documentation about debugging. I've heard "Fiddler" and "Chrome Dev Tools" tossed around here and there, but no formal tutorials on how to gather the necessary information from a malfunctioning app. 

Please recommend some tools and methods so we can continue to evangelize PowerApps within our organizations and have  successful rollouts. 

Thanks for all your hard work, 
Eric

[sarafankit]

@ericonline - First of all let me start with Thanking You for using PowerApps and evangelizing it in your organization and the community.

We suggest creating a support ticket if you have an outage affecting production scenarios. Support team has channels to escalate issues to engineering and can wake up people (including me) depending on the scope of outage.

We also suggest posting on the community because multiple users can describe their symptoms which helps us narrow down the issue faster and provide a fix. Even today, we were able to narrow down the issue faster via details provided in the posts.

In terms of debugging, there really are not much options around what you can do due to the nature of the product. A network trace using Fiddler or browser dev tools can sometimes let you see an error message which the UI may have hidden.

The best set of information to provide us is details around changes you made recently and get a Session Id from the session where your see the issue: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/get-sessionid

[ericonline]

Thanks for the response. Just to be sure I have the protocol down:

1. User experiences issue with a PowerApp.
2. User calls OUR internal tech support
3. Tech support deems the issue to be on Microsoft side ( HOW?)
4. Our internal tech support “creates a support ticket w/ Microsoft (Where is the PowerApps support contact info?).
5. Our internal tech support posts the issue to the community forum (Is there a specific format for suspected bug posts? Screenshot, connectivity details, version numbers, etc?)
6. Microsoft responds to our support request with either a “fixed”, “not a Microsoft issue” or “ETA x hours” message (I imagine).
7. Our internal tech support notifies user accordingly, advising of work arounds in the meantime (Is there a list of workarounds somewhere? E.g. “If mobile app is down, use browser link on mobile device.”, “If Sharepoint data connector is down, print form, complete manually, upload later.”)
8. Our internal tech support updates post on forum with findings as necessary.

Quite a bit of oneness on our internal tech support for bugs and issues that are out of our control. Also without some form of debugging the potential for “back-and-forth” between our internal tech support and Microsoft is high. Meanwhile users are dead in the water.

[skylitedave]

• Can you provide the proper link to enter a support ticket when we suspect a bug in PowerApps? 
• How can we indicate the severity - ie there some kind of ranking that we should use to indicate say a production outage affecting many users that cannot work?  
• We want to be able to let the PowerApps team know which bugs are really impacting a business versus something we uncovered that is an issue but not blocking a business process. Let us know the proper way to do that.  I would suggest a blog post on this with a link on the PowerApps home page if possible describing all of this.  Help us help you 🙂

[Ying]

@ericonline, @skylitedave Thank you for your feedback, and your suggestion is good for having a blog post describing the support process in detail for PowerApps. We will take that as an action item to deliver - providing more details describing the process end-to-end.

If you need to file a support ticket to get Microsoft help for an PowerApps issue when you are stuck, or unable to resolve via Community forums help, this is the link to file from the PowerApps support portal: http://powerapps.microsoft.com/support/pro/ . The current submission form does not ask the severity, but we do want as much detail description of the issue as possible. As my colleague @sarafankit previously mentioned: the best set of information to provide us is details around changes you made recently and get a Session Id from the session where your see the issue: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/get-sessionid.

Thanks,

Ying

[ericonline]

@Ying, I appreciate the guidance and professional response, thank you. I will work this into our internal workflow and look forward to the support post. 

Take care, 
Eric