A customer of mine wants to use Dynamics. As time goes on the user interface is starting to prove to be more complexity than they'd like. We also want to connect some flows so that data is automatically created. For example, I'd like to be able to create released products as a 1 step process or at least have a simpler UI for it.
Our options look like the following:
A) Try to create custom UI elements using dynamics framework which would be focused view and flows we care about.
B) Leverage the power platform from dynamics, this includes Power Apps, Power BI and Power Automate to create a custom front end experience.
C) Roll our own solution in either a SPA , MVC, or MVVM app and then use OData/REST to send data back and forth. If we go this route, ideally I'd like to use something like React that either talks directly to OData service or talks to a .Net core 3 back end. Also entertaining blazor as it's becoming a hot item.
I've never done A, B or C before with Dynamics and I was hoping to get feedback from the community on the different approaches and pitfalls encountered doing them. Thanks for your feedback!
