You can place multiple entity forms on a single Power Pages page, but only if each form is creating or editing different records and does not conflict with the others.
The error you’re seeing:
“An entry with the same key already exists.”
is a classic symptom of form metadata collisions.
This happens when two or more entity forms on the same page try to register the same client-side key, usually because:
-
They are all create forms for the same table
-
They share the same form name, form ID, or HTML field names
-
They use the same entity logical name and Power Pages tries to bind them into the same context
-
They include identical attribute names (e.g., name, ownerid, createdon)
-
They load the same metadata scripts more than once
Power Pages then attempts to build the form context dictionary and hits a duplicate key → resulting in the error.
Why your setup is failing
You have:
{% entityform name: 'NewBoard' %}
{% entityform name: 'Information' %}
{% entityform name:'NewStaff' %}
Even though the forms have different names, they are all:
-
Create forms
-
On the same page
-
Likely using the same table or overlapping fields
-
All loading the same entity form scripts (entityform.js, metadata, validation, etc.)
This causes the duplicate key error.
Is it possible to have multiple create forms on one page?
Yes — but only under specific conditions.
✔️ Supported
-
Multiple forms for different tables
-
One create form + one edit form
-
Multiple forms if each has unique field sets and no metadata collisions
-
Using Web API + custom HTML instead of entity forms
❌ Not supported / problematic
-
Multiple create forms for the same table
-
Multiple forms that include the same attribute names
-
Multiple forms that rely on the same entity metadata
-
Multiple forms that load the same client-side keys
This is why your page breaks.
Recommended solutions
Option 1 — Split the forms into separate pages
This is the simplest and most stable approach.
Use tabs or navigation to make it feel like one page.
Option 2 — Use Web API + custom HTML forms
Instead of entity forms, build your own forms using:
-
HTML
-
JavaScript
-
Power Pages Web API
This avoids metadata collisions entirely.
Option 3 — Use a single entity form with subgrids
If the “Board Members” and “Staff” are related tables, you can:
This is the most “Power Pages native” pattern.
Option 4 — Use iframes to isolate forms
Each iframe loads its own metadata context, so no collisions occur.
Not elegant, but it works.
