Saving Progress in Multi-step Forms and anonymous users

[egtb]

I have a long application that I'm considering creating a multi-step form for. What I'm wondering is, if an anonymous user starts the form, gets halfway through, and then closes out of the tab/browser, is their progress saved? I've seen that session details are saved for forms, but wasn't sure if that applied just for authenticated users. 

[mandela]

I will say it depends on how you implement the multi-step form in Power Pages. There are different ways to handle anonymous user data in web forms, such as using session cookies, database records, or local storage. However, each of these methods has some advantages and disadvantages, and you should carefully consider the trade-offs and best practices for your specific scenario.

[egtb]

Thanks for the reply! My main reason for asking is determining if this is possible to do with the subscription plan I'm thinking of using or if I'll have to upgrade now or later on. Based on this, it sounds like it's possible to allow anonymous users to return to the form with progress saved, there just might be additional pros/cons to think through while implementing?

[Lucas001]

Hi @egtb,

what is the reason you need anonymous users?

A question from me would be if it does not make sense to authenticate them beforehand. The issue I can see is if somebody wants to crash your page the multistep form can be filled out automatically and be spammed. Make sure to integrate a captcha.

1. Local Storage (Client-Side):

   • Pros:
     • Fast and responsive as data is stored on the client's device.
     • No server-side storage or processing required.
   • Cons:
     • Vulnerable to client-side attacks or data tampering.
     • Limited storage capacity on the client's device.
     • Data is lost if the user clears their browser storage.

2. Session Storage (Client-Side):

   • Pros:
     • Similar to local storage but with a shorter lifespan (cleared when the browser session ends).
     • Can be more secure than local storage for temporary data.
   • Cons:
     • Data loss when the user closes the browser or session ends.
     • Vulnerable to client-side attacks.

3. Cookies (Client-Side):

   • Pros:
     • Persistent data across sessions if configured with an expiration date.
     • Can be more secure if used with encryption.
   • Cons:
     • Limited storage capacity.
     • Vulnerable to client-side attacks.
     • Data is sent with every HTTP request, impacting performance.

[Lucas001]

@egtb, had to split the post as it cannot exceed a specific amount of chars and formatting.

Some more possibilities:

1. Server-Side Database (e.g., Azure SQL Database):

   • Pros:
     • Secure and scalable storage.
     • Data persistence even if the user closes the browser.
   • Cons:
     • Requires server-side processing and storage infrastructure.
     • Potential cost implications based on usage.

2. Power Platform (Dataverse or Common Data Service):

   • Pros:
     • Integration with other Power Platform services.
     • Centralized storage with security features.
   • Cons:
     • Requires licensing, potentially leading to cost implications.
     • May have limitations on the number of records or storage capacity.

3. Azure Storage (e.g., Blob Storage):

   • Pros:
     • Scalable and cost-effective storage solution.
     • Integration capabilities with Power Platform.
   • Cons:
     • Requires additional configuration and setup.
     • May have a learning curve for those unfamiliar with Azure services.

4. Combination of Local and Server-Side Storage:

   • Pros:
     • Can leverage the benefits of both client-side and server-side storage.
     • Provides a balance between responsiveness and data persistence.
   • Cons:
     • Requires synchronization logic to ensure data consistency.
     • Adds complexity to the implementation.

When choosing an option, consider factors such as data sensitivity, user experience, scalability, and cost. It's also crucial to comply with privacy regulations and ensure that the chosen storage method aligns with your organization's security policies.