If you follow us on social media, hopefully you’ve seen that we at Engineered Code shared some exciting news this week. We announced ecLearn, a learning management system (LMS) built on top of Microsoft Dataverse. In this blog post I’m going to give you a bit of a glimpse into the ecLearn journey.
It’s been too long since I’ve posted! With all of the virtual conferences taking place in 2020, I couldn’t find the time to get any blog posts done. But I plan to change that in 2021. First off, I want to share a solution for when you want to use the Condition type of Web Form Steps, but your condition is more complicated than just checking if a regular field equals a specific value.
In this series of blog posts, I’m looking at the ways to enable an asynchronous conversation between Dynamics/Power Apps users and portals users. The two most common techniques I see use Entity/Web Form Metadata – either the Notes or Timeline metadata option. This post covers a comparison between the two.
In this series of blog posts, I’m looking at the ways to enable an asynchronous conversation between Dynamics/Power Apps users and portals users. The two most common techniques I see use Entity/Web Form Metadata – either the Notes or Timeline metadata option. This post covers the newer way – using the Timeline metadata option.
In this series of blog posts, I’m looking at the ways to enable an asynchronous conversation between Dynamics/Power Apps users and portals users. The two most common techniques I see use Entity/Web Form Metadata – either the Notes or Timeline metadata option. This post covers the original way – using notes.
In many cases, allowing for a “conversation” between your Dynamics/Power Apps model-driven app users and your Power Apps Portals users is a requirement for a portal. For example, once a description is entered into a Case, often a back-and-forth is required in order to lead to its successful resolution. In Power Apps Portals, the two primary ways to achieve this functionality is by leveraging either the Notes or the Timeline options of Entity or Web Form Metadata. In this series of posts, I’ll look at these options in more details.
The Web Forms functionality lets you build complex multi-page, multi-entity wizard-style forms on your Power Apps Portals. And while there are a ton of options, it’s not uncommon to run into situations where you can’t do everything you want with configuration, so you might need to resort to a bit of JavaScript (and maybe even Liquid). One of those situations is if you want the source entity for the next step in your Web Form to be a record related to the entity of the current step.
