We have a website for reporting on analogue field services.
There are external and internal users and each of these is mapped to client entities.
In the current state website, account management is baked into the website for actions:
* register a new AspNetUser (dont want access for the general internet to register on the site)
* associate a user with a client entity
* associate a client with reports
The associate flows would be to parse parameters from a message and execute parameterised stored procedures.
I believe a more modern approach would be to use a Flow/Logic app/Power App and keep the website really simple focused on end user consumption.
Has anyone done this already?
Daniel


Report
All responses (
Answers (