Tag Archives: Power Platform

When “required” field validation is not client-side only anymore

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 »

Canvas Apps: What is a “scope” and, what does it have to do with Filter/Lookup functions?

In the previous post, I was looking at which attributes are added to the CDS query by the Filter/Lookup functions. Might not end up with a definitive answer there, but, to summarize, chances are you’ll get the attributes included IF those attributes are utilized in the other formulas. Now, it turned out there is a… Read More »

User licensing in D365 instance

When thinking about user licensing in D365 instances, you may be thinking of D365 applications. However, from the licensing standpoint D365 instance is nothing but an “advanced” CDS instance with a bunch of first-party apps deployed there, so it is still possible to use Power Apps “per app” and “per user” plans in those instances.… Read More »

A CDS security model which supports data sharing, but which is not using business units or access teams

We all know about the owner teams, security roles, access teams, field security profiles, etc. But there is yet another not-so-obvious security feature which controls access to CDS records through the “reparent” behavior on the “parental”/”configurable cascading” 1:N relationship. Why does it matter? See, on the diagram below, even though the security role is configured… Read More »