KennyG
Apr 1, 2019
visibility 3669
star star star star star
(6 votes)

Gotcha’s with reusing Episerver Forms ElementBlocks

First a quick refresher, then the gotchas

Copy/Move Form Elements

So, you may or may not be aware that you can reuse form elements. Say you’ve got a long list of locations that you want to use on more than one form.

You can copy/move an element from one form to another:

With the first form open, switch from the Forms tab to the Blocks tab.

Scroll down and select the “For this form” folder.

This contains all the Form Element Blocks.  From the context menu, choose copy/cut

Go to the other form, switch to the Blocks tab, and select the “For this form” folder.

Here on the folder’s context menu, choose Paste.

You can now drag the copied element to the second form.

Share a single element between several forms

So, instead of making copies that will all need to be updated moving forward, say you wanted a shared element that you can use on multiple forms. Instead of pasting into the other form’s “For this form” folder paste them into a shared location. Something like a “Shared Form Elements” folder. 

 

From this folder you can drag the shared element onto multiple forms. Update the shared element and it affects all linked forms.

Now the Gotcha’s!

If you have the Salesforce connector installed and have the Form Element mapped to a Salesforce table, you lose access to the Extra Field Mappings tab. Here is an example of the original element: 

And here it is after you've moved it to a shared folder:

I think this is because the element must look to its parent form for table mappings and this connection breaks when you move the element out of the “For this form” folder.

A similar situation is the Dependencies tab:

No error message, just a blank screen:

 

 

Any other gotcha's you've run across, or ways to get around the issue? Let me know in the comments.

Apr 01, 2019

Comments

Praful Jangid
Praful Jangid Apr 2, 2019 08:42 AM

Have you checked in logs for any clue? Are you getting any specific error logged? 

Harinarayanan
Harinarayanan May 16, 2024 11:25 AM

Hi Kenny, I'm facing exactly same issue now, Is there any solution / work around to overcome this issue?  

error Please login to comment.
Latest blogs
Personalisation in CMS 13 when you go headless: variations in the CMS, decisions in Experimentation

Back in February I wrote about personalisation in CMS 13 using Audiences . Everything in that post still holds, with one condition I should have ma...

Minesh Shah (Netcel) | Sep 24, 2026

Optimizely Forms: 4.7.0 Too many concurrent connections

Optimizely Forms are eating your emails! How to make it stop!

Tomas Hensrud Gulla | Sep 24, 2026 |

Optimizely CMS 13.2: Cannot find an authentication provider for 'ActiveDirectoryManagedIdentity'

CMS 13.2 upgraded SqlClient to 7, and Managed Identity stopped working in Azure until I added one NuGet package.

Tomas Hensrud Gulla | Sep 23, 2026 |

Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |