Error Importing a Solution with a Custom Connector in
"Something went wrong" best error message ever, so versatile... fits every situation.
"Something went wrong" best error message ever, so versatile... fits every situation.
Microsoft at it again, killing off something half decent but old for a inadequate 'modern' replacement with a fraction of the capabilities.
Step by step, turning a local Node.js prototype into an Azure Function wrapped with a Custom Connector so it can be called easily from a Power Automate Flow.
Long awaited news about using existing Teams Phone deployment to extend telephone numbers in to Dynamics 365 Contact Center and any 3rd party solution that uses Azure Communications Services.
One of the Power Automate Flows wasn't showing up for a specific person, but it was still fine for everybody else. Here's how I tracked down and resolved the issue.
Having been in the dark for years only hearing vague and questionable information, I took it on myself to figure out how to reliably and accurately map addresses in India to the relevant Telecom Circle, Metro Area, or Districts under the Unified Licence for Virtual Network Operators.
Ghost has been quite easy to get up and running and fairly flexible overall. I decided that I didn't like what I got out of the box and decided to see what was possible with a little skill and locked door to keep the distractions away.
Get serious with Power Pages by downloading and developing sites locally with Visual Studio Code with the added benefit of being able to run pre-processors such as SASS, TypeScript, and more... if that's your thing.