Apr 1, 2019
(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


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? 

Please login to comment.
Latest blogs
Implementing EmbeddedLocalization in Optimizely CMS 12

My previous post on translation (Translating Optimizely CMS 12 UI components) gives an overview of how to implement the FileXmlLocalizationProvider...

Eric Herlitz | Jan 27, 2023 | Syndicated blog

Breaking changes in EPiServer.CMS.TinyMce 4.0.0

After upgrading to the latest version of EPiServer.CMS.TinyMce, the dropdown with formats disappears. Learn how to get it back!

Tomas Hensrud Gulla | Jan 27, 2023 | Syndicated blog

Translating Optimizely CMS 12 UI components

Optimizely CMS 12 have been out for a while now, but still some elements haven't been properly translated resulting in a GUI defaulting to english....

Eric Herlitz | Jan 26, 2023 | Syndicated blog

Image preview in Optimizely CMS12 all properties view

With these simple steps, you can now see an Image and its Metadata, including size and dimensions, when editing an Image property in Optimizely...

Tomas Hensrud Gulla | Jan 26, 2023 | Syndicated blog