Can Model driven apps do this... (vs. Canvas apps)

(1) Share

Report

Posted on by BP-19081954-0

I've mainly developed Canvas apps, but I'm gathering that model driven apps can be quicker and easier to set up without having to structure the user interface & experience in as much detail.

Can someone help me with some functional questions on Model driven apps to help me resolve whether I need to move that direction?

1) I am used to using controls to determine code. eg. if a field on a form = auditing, display a button which allows an audit request to be sent.

Can Model driven apps do something similar, or would that require PCF controls?

2) I have enjoyed tweaking the code in a form to allow something akin to autofill (prepopulating the field with information depending on the text that has already been typed).

Can Model driven apps do anything similar?

3) on some forms, I have had some fields depend on the value of another field eg. enter the next sequential autonumber if the status is set to "certifying."

Is there any similar functionality in model driven apps?

4) am I right thinking that buttons can be placed on model driven apps to trigger power automate flows eg. to send out a letter.

5) is there any way in a model driven app to structure email notifications dependent on the change of a record eg. when the status of a project changes & is saved, or is power automate the only way to do this?

Thanks so much for replies!

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (0)

Vejai SH 560 on at

Like (0)

Report
Copy link

Link copied!

Hi @BP-19081954-0

1.Show/Hide Button Based on Field Value (e.g., “Auditing”)

Can Model-driven apps conditionally display a button based on a field value?
Yes, but not with out-of-the-box drag and drop like canvas app, Command Bar customization with Javascript + Ribbon Workbench/ Power FX

2.Autofill Based on Input
Can Model-driven apps “autofill” a field based on typed input (like autocomplete or smart fill)?
Auto-populate another field based on value: Use Javascript or you can develop custom PCF control

3.Conditional Auto-number or Field Dependency (e.g., if Status = Certifying)

Yes, in multiple ways

Javascript-for more form based logics

Power Automate and Plugins - for complex autonumbering logic or sequential rules.

4.Buttons to Trigger Power Automate Flows
Yes,
You can add custom command bar button(using Power FX or Ribbon Workbench)
That button can trigger Power automate cloud flow using HTTP Trigger

5.Email Notifications on Record Changes (e.g., project status)
Yes,
Power Automate Cloud Flow: Most common and modern way to trigger on record update to send email
Plugins- For advance, real-time

Let me know if you have more question.

Thanks,
Vejai SH

Was this reply helpful? Yes No
ankit_singhal 618 Moderator on at

Like (0)

Report
Copy link

Link copied!

Yes you can do all in model driven. Power automates will be work same like canvas. you can trigger power automate on change of any column or record creation. Also, you can add buttons in the ribbon bar and applied all the show and hide using Power Fx or JavaScript.

Note: Please mark verified, if it is useful for you

Was this reply helpful? Yes No
BP-19081954-0 61 on at

Like (0)

Report
Copy link

Link copied!

Thanks so much for replies @ankit_singhal & @Vejai SH I really appreciate the input.

I've been thinking things through & wondered if you could add some insight.

From you answers, I gather that I would need to learn Javascript in order to implement the same kind of customizations in Model Driven Apps that I am used to using in Canvas Apps.

Comparing Model Driven apps with Canvas apps, when you know Javascript, are the kind of customizations I am talking about easier to implement in Canvas apps? If I have to resort to PCF controls or Javascript for each piece of functionality, is it going to be more work all round going the Model Driven route?

I appreciate any insight you can give!

Was this reply helpful? Yes No
Suggested answer

CU17062004-0 18 on at

Like (0)

Report
Copy link

Link copied!
You're thinking exactly in the right direction — model-driven apps definitely simplify a lot of things if your data is already structured well in Dataverse and you don't need full control over the UI. Let’s walk through your questions one by one — super practical questions for someone coming from a Canvas app background!

1. Conditional UI – Showing/Hiding Buttons Based on Field Values

Model-driven apps don’t have the same flexibility as Canvas apps when it comes to control-level visibility logic.

What you can do:

Use JavaScript on forms to show/hide buttons or make fields read-only.

Use Command Bar customization to conditionally show buttons.

If you want more advanced visual controls (like a dynamic custom component), then yes, PCF controls would be the way to go.

2. Autofill Based on Typed Text (Like a Search Helper)
This is partially possible, but it's not as flexible as a Canvas app.
You can:

Use business rules or JavaScript to populate other fields based on values typed.

Use lookups with search filtering logic (e.g., filter related accounts by typed company name).

What you can’t easily do:

Implement dynamic predictive text or “autocomplete” without custom dev work (e.g., using PCF or JavaScript).

3. Field Dependencies / Conditional Values (e.g. Auto-numbering)

Yes, this is very achievable in model-driven apps.

You can:

Use business rules to set values based on field changes (like if status = "certifying", then generate value).

Use JavaScript to generate sequential numbers or manipulate form logic.

Use Power Automate for background logic too.

You’ll just need to wire the logic to run on change of a field and/or on form save.

4. Buttons That Trigger Power Automate Flows

Absolutely yes.

Use Power Fx buttons or custom command buttons on a model-driven app form or view that:

Trigger a Power Automate Flow.

Pass the current record as context to that flow (e.g., Project ID, Status, etc).

You’ll configure this in the Command Designer in modern Power Apps.

5. Email Notifications Based on Record Changes

Power Automate is your go-to here.

Best practice:

Create a flow that triggers on update of a Dataverse record (e.g., when project status changes).

Check the old vs. new value to detect status changes.

Send email accordingly.

You can also use Dataverse classic workflows, but Power Automate is much more flexible and modern.

Let me know if this helped you to address your questions and concerns .

Was this reply helpful? Yes No