Just a few days ago, when I was writing a post about Power BI Paginated Reports, “Dataverse” connection type was still called “Common Data Service(Preview)” there. As of today, in the updated version of the Power BI Report Builder, it’s called “Dataverse”: There is no reference to the preview anymore, but, apparently, it’s still a… Read More »
In the previous post, I looked at some of the features of Power BI paginated reports. What was still unclear is how security works. Turned out it works pretty much as one would expect. Users having no access to the data won’t see that data in the report. Unless the report has NOT been configured… Read More »
Now that SSRS authoring tools have finally been updated (and there is a great article Nick Doelman published the other day on this topic), it might be the right time to ponder on which technology we should be using moving forward since there are two now: Power BI Paginated Reports SSRS So, how do… Read More »
Have you ever tried adding power apps applications to the office app launcher? I actually had not done it myself up until a few days ago, when one of the users mentioned they were observing some strange behavior there. So I tried, and it was working perfectly fine for me, until, just by pure coincidence,… Read More »
I’ll be absolutely honest – I have no idea what the answer is to the question above. Except that this combination of settings might be a legacy of the older versions of Dynamics CRM? However, if I were to make a suggestion here, I’d say don’t use that combination. Since it may lead to confusing… Read More »
Coincidentally, there seem to be change in how required fields are treated in the model-driven forms. I’m saying “coincidentally”, since I recently wrote a post on a related(though different) topic: https://www.itaintboring.com/dynamics-crm/how-to-not-to-get-stuck-on-the-required-fields-when-creating-a-power-automate-flow/ And, then, a co-worker just mentioned that, it seems, hidden fields are not “required” anymore in the model-driven forms even if they have been… Read More »
You may have seen the announcement: https://powerapps.microsoft.com/en-us/blog/simple-image-control-for-model-driven-apps/ So, I was looking at it tonight and realized that I should probably take it for a spin on my phone. After all, one of the obvious scenarios would be to have a few image fields on the form so we could open that form on the mobile… Read More »
Microsoft Dataverse has a somewhat unique interpretation of what a “required” field is. It’s a bit of “do as I say not as I do”. For example, I can’t create an account in the user interface not having “account name” populated (since it’s a required field): But, of course, behind the scene… whether through Excel… Read More »
Out of a sudden, there is functionality now that we always wanted… and, yes, it went almost unnoticed. We can use main forms within other main forms now. As in the example below, I can edit primary contact information without even leaving the account form. And, then, I can do the same with the owner… Read More »
In one of the earlier posts this month I was seemingly unhappy about the missing “incremental refresh” option: https://www.itaintboring.com/dynamics-crm/power-platform-dataflows-have-i-missed-incremental-refresh-option-somehow/ But, having thought about it a bit more, I don’t think it’s such a big issue. Not when working with the SQL data sources, at least. All we really need is a view that will pre-filter… Read More »