Mastodawn

On our side, this case information is received in Power Platform using a Logic App, which stores info into Dataverse and Sharepoint, and lets us know about the issue in Teams.

Lastly, because of course things can just go wrong sometimes, there should be a clear "Now what?"

Right in the support engine, you can fill out the key things we need to investigate -- AND it will attach all the info we would want to diagnose the issue as a ZIP file.

So, to sum up:
- Give the tools to help the user self-check
- Give relevant help
- When all else fails, make sure you get the info you need

All of this is just built into our #msdyn365 No-Code API Factory solution, Data Braider. And I hope you add something like it to yours.

The tool will run through the scan, and give things you can try to resolve the issue without having to check a wiki or email a support desk.

Once you've selected which configurations are giving you trouble, you can choose which scans you'd like to run.

Users running into problems with the product can open a Support Wizard within Business Central itself.

This wizard will scan for common issues that users may encounter with settings.

I kept trying to come up with a better title than "Please Steal This Idea", but couldn't.

Today I want to talk about a feature in our #msdyn365bc solution Data Braider that I hope customers *never* need, but when they do, I think it's amazing.

In Data Braider, you have a tool to make your own APIs. This means that you have the power. That also means you can absolutely make things not work the way you intended.

Built into the foundations of 2.0 is the Support engine.