Crisis Communication solution feedback

[mabolan]

On Monday afternoon, as news of COVID-19 cases spread globally, we pulled together a team to help customers coordinate their own information sharing and team collaboration in response to evolving conditions in times of crisis. Today, less than 48 hours later, we’re releasing the first version of that solution for any customer organization to quickly implement. You can read more about the solution in our blog post or get the full instructions for how you can implement your own Crisis Communication app here.

We're extremely excited to hear how the community leverages this app, so we've created this thread to hear directly from you. Feel free to share your experience customizing the solution and altering it for your own needs. Over the next few weeks, we'll take your responses to make the app even better and post incremental updates. 😁

[Anonymous]

I follow the steps as mentioned in Youtube video and I am getting stuck after importing the DeploySPLists.zip file to Flow. During "Select during import" sharepoint connection I give my organization cloud SharePoint details, it showcases as a Green tick and uploads. It doesnt prompts me for Office 365 or Teams connections anywhere. 

Now when I edit the flow and try to update the SharePoint group path under , it displays following error.

/providers/Microsoft.PowerApps/apis/shared_sharepointonline/connections/shared-sharepointonl-E508A184-5A23-404F-9A01-025936C0C14E'. Failed to fetch

It wont let me Save or Run the flow app. Can anyone help?

[bastosj]

Hi there @Anonymous , @rakesh0987890,

I'd like to help you both in resolving ASAP this issue, which looks similar in both reports.

Could you please confirm whether the licensing issue is currently happening for the Admin App or the Users App?

Kind Regards,

João

[bastosj]

Hello @aarondab,

Have you been able to sort out this issue in the meantime? I'd be keen on supporting you if otherwise.

The Flow with the name CrisisCommunication.Request enrures that all received requests are posted to the configured Teams Channel you provide. 

For this, essentially you need to ensure 3 things:

1. Your Inbox and Admin Email are configured with the same email address
2. Your Teams Id and Channel Id need to be configured with IDs from your Teams tenant.
3. Teams Policies allow Flow to communicate with Teams: 

The error you've reported typically happens when either the Team Id or Channel Id have not been properly set to values from your organization's Teams. 

Please ensure both values are configured as per described here

Let me know if you were able to solve the issue!

Kind Regards,

João

[bastosj]

hello @Anonymous,

Deploying the DeploySPLists.zip Flow should prompt you exclusively for the SharePoint connector and not others, so that's quite normal!

Regarding the update issue, could you please confirm you're updating the "Target Site For Lists" variable (as attached).

Could you please also ensure the user provided for the SharePoint connector has permissiosn to read and create lists within the SharePoint site you've configured?

Many thanks,

João

[Anonymous]

Buen día , disculpa yo tengo el mismo problema no se si tu hayas podido solventar este error de alguna forma?

[bastosj]

Buen dia @Anonymous ,

Puedes describir el problema con más detalle?

Gracias,

João

[DayanaVerdugo]

It's an awesome app but actually I have troubles in the process of build and deploy the app. I had already done step-by-step actions and check all the prerequisites but at the moment of run the flow for import app files to Crisis Comms's SharePoint site, It always shows me this error in the Scope-Logo Library part:

"Action 'Send_an_HTTP_request_to_SharePoint_Logo_Library' failed" 

Thanks for your help!

[Anonymous]

---

@martinkwright wrote:

Thanks to all involved in continuing to further this application. We have successfully applied the update and published it to our entire company. All of my nits and bugs that were causing issues have now been resolved with the exception of still hitting some quota when doing Teams notifications. For now, we are sending emails instead. This works. We get about 300 or so out and it then responds with a "Quota has been exceeded" message and stops sending notifications. We have had a ticket in with MSFT for a week now but don't know where we need to go next so that we can send notifications via teams flow.

Again, Really appreciate all the support from the team, @Mr-Dang-MSFT @mabolan , during this time. 

---

Hi @martinkwright , did you ever have a resolution for this one? We have the same issue (we just started using the feature, which is why we didn't encounter the problem before). Thanks!

Merel

[martinkwright]

Hi @Anonymous . Unfortunately, we abandoned using teams as the notification... It was really nice for up to about 300 people. We opened a ticket with Microsoft on our Microsoft 365 side and they essentially wanted us to re-architect the app. Here is their response, but for now we are going to stick with notification by email which works with our 800+ employees. 

Resolution:

We are hitting the throttle limit for the non-Get requests. The limit for non-Get requests is 300 per connection as specified in the documentation. We can not create additional connections to post 300 more messages.

Please refer the link below

https://docs.microsoft.com/en-us/connectors/teams/

For example: If we are posting 300 individual messages to users, can we have these users grouped in a single channel, so that we can get away with one message and have 299 of the quota left.

[DanielaHo]

Hi, 

We are currently piloting the app hoping to deploy it company-wide. However one issue is causing hesitation:

In order for a user to be able to submit a status, I found that they need membership access to the SPO site that captures the data?!?

This means the user could access and edit the SPO site...

What is the proposed solution to this?

To enable a filter on the list so users can only see their own submissions?

With membership access they could do a lot more than that though...