The real-life scenario: a portal user (agency) indicates that they don’t manage a particular property anymore. The action is performed via self-service portal. From a user experience perspective, the property has to “disappear” from the list of active properties immediately after “no manage” action is performed.
If we choose to use Deactivate as an action we’ve got two documented choices…
Continue Reading Olena Grischenko’s Article on their blog
Power Apps Portal: deactivate account, no workflow please, thank you
The real-life scenario: a portal user (agency) indicates that they don’t manage a particular property anymore. The action is performed via self-service portal. From a user experience perspective, the property has to “disappear” from the list of active properties immediately after “no manage” action is performed.
Blog Syndicated with Olena Grischenko’s Permission
More About This Author
Array
PowerAutomate2021.09.06Power Apps Portal: “Table permission changes for forms and lists on new portals” So what?
PowerAutomate2021.08.17Dataflows for PowerApps: loading data from CSV file without copying it to OneDrive in advance. 💖😎👍
PowerAutomate2021.08.09Child Flow: the ‘runAfter’ condition is not satisfied.
PowerAutomate2021.08.08Power App Portal Web API – fighting lookups
