Pawan Singh
Jul 16, 2025
  629
(0 votes)

Importing Form Submission Data into Optimizely Forms Using DdsPermanentStorage

Recently, we needed to import a large number of records from a third-party system into Optimizely Forms. The data was available in CSV format, and our goal was to insert this data as form submissions within the Optimizely platform.

🔍 The Challenge

During our initial analysis, we discovered that Optimizely Forms does not offer a built-in API to directly insert or update form submissions programmatically. While the method PerformDataSubmit() handles submission automatically through the UI (taking care of cookies and submission IDs), it relies on HttpContext, which we don’t have access to in a scheduled job environment—like in our one-time migration scenario.

✅ The Solution: DdsPermanentStorage

After some investigation, we found that the internal class DdsPermanentStorage can be used to directly interact with the Optimizely Forms' data store. This allowed us to insert and update form submissions programmatically without depending on the httpContext.

We utilized this class in a scheduled job and were able to import all records successfully.

🔸 Important: To ensure these submissions show up correctly in the Form Submissions view under Edit Mode, you must include the SYSTEMCOLUMN_Language field during creation.



🕒 Handling Custom Submission DateTime

While everything was working well, we noticed that the submission timestamp (Created date) was automatically generated by the system at the time of insertion. However, our source data contained historical submission timestamps, and it was important for reporting and UI display that we preserve these original dates.

To solve this, we went one step further and overridden the default behavior to allow setting a custom submission date. We achieved this by extending DdsPermanentStorage as below.

using EPiServer.Data.Dynamic;
using EPiServer.Forms.Core.Data;
using EPiServer.Forms.Core.Models;

namespace Alloy.Customization.ExtendedDdsPermanentStorage;

public class ExtendedDdsPermanentStorage : DdsPermanentStorage
{
    public const string SYSTEMCOLUMN_SubmitTime = "SYSTEMCOLUMN_SubmitTime";
    protected override void EnsureFormFieldsExistInPostData (FormIdentity formIden, ref PropertyBag postData, out IDictionary<string, Type> typesBag)
    {
        DateTime.TryParse(Convert.ToString(postData[SYSTEMCOLUMN_SubmitTime]), out DateTime submitedTime);
        base.EnsureFormFieldsExistInPostData(formIden, ref postData, out typesBag);
        if (submitedTime > DateTime.MinValue)
        {
           postData[SYSTEMCOLUMN_SubmitTime] = submitedTime;
        }
    }
}

🧩 Dependency Injection Setup

Since this custom class may need to be reused in other parts of the solution (or injected), don’t forget to register it in the DI container if you're wrapping it inside a service or using Optimizely’s built-in services.

Hope this post helps someone facing the same challenge!

Jul 16, 2025

Comments

Please login to comment.
Latest blogs
From Vision to Velocity: Introducing the Optimizely MVP Technical Roundtable

Digital transformation is a two-sided coin. On one side, you have the high-level strategy, the business cases, the customer journeys, and the...

Patrick Lam | Mar 6, 2026

Commerce 14.45.0 is incompatible with CMS 12.34.2 (but that's an easy fix!)

Incompatible is a strong word, but that is to get your attention. This is one of the small thing that can be overlooked, but if you run into it, it...

Quan Mai | Mar 5, 2026

Announcing Stott Security Version 5.0

March 2026 marks the release of Stott Security v5, a significant update to the popular web security add-on for Optimizely CMS 12+, with more than...

Mark Stott | Mar 5, 2026

Is Opal the Enterprise-Ready Evolution of OpenClaw?

From OpenClaw experiments to enterprise AI agents: exploring the journey from my personal automation to governed execution at scale with Optimizely...

Hristo Bakalov | Mar 5, 2026 |