Form Component Control (FCC) issue - FCC ignores specified form, loads a different form

(4) Share

Report

Posted on by BK-25081839-0

Hello, I am experiencing an issue with Dynamics 365 (Model-Driven Apps) Forms using Form Component Control (FCC).

When I specify a Form to be loaded by FCC, it ignores the specified form and loads a different form.

For example, let's say I have 10 Forms, Form1, Form2, Form3... Form10.

I configure FCC to load Form1. It loads Form4.

I configure FCC to load Form2. It loads... Form4.

I configure FCC to load Form7. It loads... Form4. Always Form4. No idea why it chose Form4.

Form4 is a nice form, nothing wrong with Form4; it's just that I need FCC to load a different form, but FCC doesn't seem to want to.

Even if I create a copy of Form4, called Form4-copy, and change Form4-copy with a few additional fields, and specify FCC to use Form4-copy, FCC loads... Form4.

I know FCC IS working, because if I configure no Form, FCC correctly displays no form. If it was completely broken, FCC would likely still display Form4.

So FCC is working, it's just ignoring the specified Form and loads a different form.

Has anyone else observed similar behavior with FCC? Anyone figure out why it chose Form4, and how to make it work with other Forms instead?

Categories:

Dynamics 365 general

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

DAnny3211 11,397 on at

Like (0)

Report
hi

A few things can cause the Form Component Control to ignore the selected form and fall back to the same one every time (what you’re seeing with “Form4”). In most cases the platform is picking the first eligible Main form for the current user and app when the requested form isn’t available to that user/app or isn’t a valid type for FCC.

Checklist to fix it

Confirm the form type

FCC can only load Main forms of the target table. It won’t use Quick Create, Quick View, or other form types.

Open the target form in the designer and confirm the Type = Main and the form is Active (not in draft).

Make sure the form is part of the app

In the App designer for your model‑driven app, open the table, add the specific Main form to the app, and Publish all customizations.

If only “Form4” is included in the app, FCC will keep choosing it.

Check security role visibility

On the target form: … > Enable Security Roles. Ensure the roles used by the testing user can see the intended form.

If the user’s roles don’t include the selected form, the platform shows the first visible form (often “Form4”).

Review per‑app form order

In the modern App designer, verify the Form order for the table (per app). Place the intended form above “Form4” or set it as the default for the relevant roles.

If form order points to “Form4” as first available, FCC will frequently land there when the requested form isn’t eligible.

Set the Form explicitly by ID (avoids display‑name ambiguity)

Get the target form’s Form ID (GUID) from Form Properties.

In the FCC properties (advanced), set the Form using that GUID rather than just selecting by display name, then publish. This bypasses name collisions and caching issues.

App/module availability

If the target form belongs to a different app or solution and isn’t available in the current app’s context, FCC can’t load it. Ensure it’s in the same app you’re testing.

Cache and user context

After changes, clear browser cache or use a private window, then test with a different user (or a minimal role) to rule out client caching and role conflicts.

Why it keeps choosing “Form4”
When the selected form isn’t eligible (not in the app, wrong type, not visible to the user’s roles, or not published), the runtime falls back to the first eligible Main form for that table in the current app context—often the one that sits at the top of the app’s form order for the user’s roles, which in your case appears to be Form4.

If this resolves the behavior, please validate the reply on the thread so others can find it more easily.

Thanks and best regards,
Daniele
Note: This response was prepared with support from Copilot to ensure clarity and completeness.

1 people found this reply helpful.

Was this reply helpful? Yes No
BK-25081839-0 16 on at

Like (0)

Report

Thank you, Daniele. That was a most informative set of tests, some of which I hadn't done. Thanks to going through these, you helped resolve the issue.

The desired behavior, by the way, was to have one tab showing Form3 and another tab showing Form4. Both tabs were previously showing Form4.

I went through the steps you suggested, and can confirm:

1. Forms 1-10 are all Main Forms

2. The Forms are part of the App

3. I updated the Forms' security roles. They were not all the same. I made them the same.

4. Changing the Form Order changed the Form that appears. I put Form3 ahead of Form4 in the Form Order, and now only Form3 appears, regardless of chosen Form. That's at least a different behavior, though still not the desired behavior - I need Form3 to appear on one tab, Form4 on another.

5. I reverified the GUID on the FCC settings for both tabs. One had the wrong GUID, that was fixed.

After going through these 5 steps, the issue was resolved! Both tabs are correctly showing the right form - Form3 on one, Form4 on the other.

Thank you, Daniele.

Was this reply helpful? Yes No