A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

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

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026

Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026

Experimentation at Speed Using Optimizely Opal and Web Experimentation

If you are working in experimentation, you will know that speed matters. The quicker you can go from idea to implementation, the faster you can...

Minesh Shah (Netcel) | Jan 30, 2026