Social distancing has definitely took a toll on my blogging – it’s been a while since the last post. Although, I’ve actually learned quite a few things outside of PowerPlatform in the last month, so I could probably start blogging about a few other things now: How to teach math fractions How to build wooden… Read More »
When working with the model-driven applications, we can make a field required, but, normally, that would not make any difference for server-side processing. That field will be required on the form: But I would have no problem at all using “empty” value for that field through the API/SSIS/etc. Or, as in the case below, by… Read More »
I was looking for a point of sale software solution the other day, and it occurred to me that, in theory, I could probably write something up using a Canvas App. Of course I would need to solve a few problems, such as: Which device do I run it on How do I stop users… Read More »
The way I feel about Power Automate Flow is a perfect example of the love-hate relationships. Yes, I can do much more than I used to be able to do in the classic workflows. However, every now and then I run into something that seems simple, but that ends up being an exercise in… Read More »
You probably know that PowerApps Component Framework is now in the public preview for CanvasApps. So, what do we do when there is something new? Of course, we start poking around to see what happens. One thought that kept bothering me is that I tend to use more than I am probably supposed to in… Read More »
Every input control in model-driven apps has a couple of methods that I use quite often when creating web resources to customize form behavior. Those are: setVisible setDisabled Actually, I can’t recall a single projects where I would not need to use one, or, probably, both of those. So, we have PCF now, and… Read More »
You know how we can put more than one control for the same attribute on the model-driven form? So I was thinking… would it work if I added the same attribute twice, but if I used default control for the first occurrence of that attribute on the form, and, then, if I used a custom… Read More »
Ever since Power Apps Component Framework went into the GA, there probably was not a day when a new PCF component would not be released by somebody in the Power Platform community. There is just no way to ignore the fact that PCF has turned into a very popular addition to the Power Platform developer… Read More »
Up until now, none of my PCF controls were meant to be readonly. But, of course, it would only make sense to prevent updates for inactive records and/or when some of those controls are set to be readonly in the form designer: Dynamics Ninja has already described the basics in his earlier post: https://dynamicsninja.blog/2019/11/25/is-your-pcf-control-read-only/ Just… Read More »
I was looking into adding FetchXml parameter to the N:N lookup PCF component earlier today, and something interesting came up. But first things first. I needed a way to define a filter for the list of records my control will be showing in the dropdown list. Imagine the following scenario, for instance: There is a… Read More »