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… Continue reading Power Apps Portal: deactivate account, no workflow please, thank you
Category: dynamics 365
Dynamics 365 CE/model-driven app: the form script unexpected discovery
Something I won't expect to discover. Yet, here I am! It's all started with a very "simple" requirement to populate a read-only form field on change of another form field, Method. The fancy way it set up is when you select the field to change it pops up the window asking you if it was… Continue reading Dynamics 365 CE/model-driven app: the form script unexpected discovery
Power Apps Portal Maintenance: The curious incident of the naughty user.
In the last article here I proposed the design for the custom Maintenance functionality: https://msolenacrm.blog/2020/06/20/power-apps-portal-summon-the-custom-error-page-to-test-a-custom-layout/ After the serious testing we discovered that the solution works, to some extent. For the naughty user ignoring our warnings to leave the portal during maintenance, it is possible to stay on the cached web page, go for a coffee… Continue reading Power Apps Portal Maintenance: The curious incident of the naughty user.
CDS current environment connector: Filtering attributes for the record created
Let's say I want trigger some logic when the particular field has been modified on a record. In this example, I modify a contact Email field and create a Note when it's been modified. I picked up a trigger for Create or Update because you can enter Email for a new record or you can… Continue reading CDS current environment connector: Filtering attributes for the record created
The curious case of the model-driven app prefix_
Since Microsoft first introduced the concept of a solution we all live in fear of creating an entity with the prefix "new_". If you do things properly you create a solution first, define a publisher with the unique prefix then all new entities and custom fields will be created with that prefix. For example, for… Continue reading The curious case of the model-driven app prefix_