Protected virtual bool SavePostedData(Guid formId, Guid sessionId, IList postedFields)įoreach (IViewModel postedField in (IEnumerable) postedFields) Return this.SavePostedData(formSubmitContext.FormId, formSubmitContext.SessionId, formSubmitContext.Fields) Protected override bool Execute(string data, FormSubmitContext formSubmitContext)Īssert.ArgumentNotNull((object) formSubmitContext, nameof (formSubmitContext)) Protected override bool TryParse(string value, out string target) Return this._dataProvider ? (this._dataProvider = ()) Protected virtual IFormDataProvider FormDataProvider Internal SaveData(ISubmitActionData submitActionData, IFormDataProvider dataProvider)Īssert.ArgumentNotNull((object) dataProvider, nameof (dataProvider)) ![]() Public SaveData(ISubmitActionData submitActionData) ![]() Let’s look at the code using the good old dotPeek. In our scenario the “Save Data” submit action will suit us best. Today Sitecore has the following submit actions: How do we do that?Įasy peasy people, we will use a custom submit action(Sitecore has excellent documentation about it). But you also want some “personal data” in the form, in this case the user. How about following scenario? You have a Sitecore Form(with some fields and a submit button) and that is great. Today I would like to show you how easy it is to add “hidden” data to a Sitecore Form. Please check out my post Time travel into the future – BLAZOR + SITECORE + HELIXĪnyway let’s continue with the post. I’ve setup a client-side Blazor Sitecore project at github – SitecoreBlazor. In the ASP.NET Core 3.0 release, Microsoft will have a (pre)server-side version of Blazor( called Razor components) using client-side with SignalR. NET) that runs in the browser with WebAssembly. It’s THE game changer which will allow you to do a single-page web app(built on. Read all about it in this great post – What’s new in Sitecore 9.1Īnd I must emphasize the importance of digging into Blazor.
0 Comments
Leave a Reply. |