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.
Independent Software Vendors (ISVs) have been an important part of the Microsoft Business Applications space for a long time. ISVs create solutions that build on top of the platforms and products that Microsoft provides off-the-shelf. As the Power Platform has continued to grow and evolve, more opportunities have presented themselves for ISVs. In this post, I’ll look at what ISVs might want to consider when looking at incorporating Power Pages as part of their offering.
Microsoft’s Power Platform is constantly growing and evolving. As much as everyone (especially Microsoft) wishes that all parts of the Power Platform worked seamlessly together, the reality is that many parts of the Power Platform existed long before Microsoft started using the word Power to group these technologies together. However, I believe that advancements in virtual tables, specifically for Power Pages, emphasizes the fact that Dataverse should be at the core of any Power Platform implementation.
The price point for Power Pages has long been a tricky discussion point. The pricing model has changed a few times of the years, and organizations can feel frustrated if they are on the wrong end of who ends up paying less and more when the model changes. In this blog post, I’ll review the history of the pricing for the product, and provide my opinion on whether I think the cost is justified by the value.
One of the subjects I seem to be dealing a lot with recently is invitation codes – so much so that this was the featured topic for this month’s Portals Community Call. During that call I promised to share a small bit of CSS that would hide the “I have an existing account” checkbox on the Redeem Invitation page, so I’ll do that in this post, as well as give a bit of background as to what the checkbox is used for, and why it most cases you probably don’t need it.
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.
I’ve always been an advocate for using CSS to control the visibility of out-of-the-box Power Apps Portals features. Unfortunately, sometimes CSS isn’t enough, and you do have use JavaScript. And even then, sometimes you have to resort to some exotic techniques – one of those times is customizing some aspects of how notes and activities are rendered on Power Apps Portals.
While not officially a series, I’ve done a few posts now on how to use CSS to modify some of the out-of-the-box experiences within PowerApps Portals. This week, I’ll show you show to convert the dropdown used to select the current view for an Entity List into tabs.
In a previous post, I asked you not to forget about CSS when customizing the user experience of some of the out-of-the-box features of the Dynamics 365 Portal product. In this post I’ll provide another example of using this technique to reduce the number of clicks required to remove a SharePoint document.
As most Dynamics 365 Portal developers start as CRM developers, we often try to take the same approach to solve similar problems on both platforms. However, it’s important to remember that a D365 Portal implementation is using different technologies, and sometimes there is a better way. Case in point – consider using CSS instead of JavaScript to control visibility of out-of-the-box features you don’t want.
