Skip to main content
Featured group

FormAssembly

This group is for FormAssembly users to ask questions to other users and share best practices. If you are a current customer and looking for a more interactive FormAssembly networking group, join the FormAssembly VIP Group: https://veerwest.formassembly.com/4739726. FormAssembly is a trusted enterprise data collection platform that empowers security-conscious organizations to drive mission-critical business initiatives and become better stewards of their data. Our platform helps customers of all skill levels build efficient data collection workflows while meeting the high security and compliance standards of regulated industries. Used by thousands of organizations, FormAssembly integrates seamlessly with other commonly used systems to streamline processes and drive business results.

Has anyone found a solution around the per form file upload of 30MB? Our forms are applications with upwards of 35 uploads each and this is a major issue. 

1 answer
  1. Mar 26, 6:09 PM

    As far as I know, to get around it, you’ll need to either split uploads across multiple forms/steps or move file uploads outside FormAssembly (upload to SharePoint/Drive/S3 and pass links into Salesforce).

0/9000

Hi All,      I have a FormAssembly form with two fields, Season Pass 1 – First Name and Season Pass 2 – First Name, and I need a validation or alert in the form to prevent users from entering the same name in both fields. The requirement is that the two names must be different, and if a user enters the same name in both fields, the form should display an error message or alert before submission. I have tried multiple approaches to implement this validation, but it is not working as expected.  @FormAssembly   

1 answer
  1. Jan 21, 3:56 PM

    I actually worked this out with Gemini(!)...I tried it and it works!...  

    To prevent a user from entering the same value in two fields (e.g., tfa_1 and tfa_2), follow these instructions to set up a "No-Code" validation system using a hidden calculation and conditional logic.

    1. The Validation Field (Field X)

    Create a text field that will act as the "logic engine." It is best to keep this field visible during testing and then hide it using CSS (class notext) rather than the "Hidden" checkbox to ensure logic triggers correctly.

    • Variable Setup: * Set tfa_1 as a variable named fieldOne.
      • Set tfa_2 as a variable named fieldTwo.
    • Calculation: Mark this field as a Calculated Field and use this formula: fieldOne == fieldTwo ? "DUPLICATE" : "OK"
    • Validation Rule: Add a Custom/Regular Expression rule to this field.
      • Pattern: /^OK$/
      • Error Message: "Field 1 and Field 2 cannot be the same."

    2. The Error Message Field

    If the built-in validation message doesn't display prominently enough, use a dedicated manual error message.

    • Field Type: Add a Text/HTML block or a Section immediately below the input fields.
    • Content: Enter a warning like: "Error: The values in these two fields must be unique."
    • Conditional Statement: Set a rule to Show this section only if the Validation Field (from Step 1) is equal to DUPLICATE.

    3. The Submit Button Logic

    This step ensures the user cannot bypass the error and submit the form anyway.

    • Conditional Statement: Apply a rule to the Submit Button (or the final section containing it).
    • Logic: Set the button to Hide (or Disable) if the Validation Field is equal to DUPLICATE.
0/9000

Anyone interested in beta testing a new software app, a 3rd party, user-controlled, cloud-to-cloud, easy-to-use software that will backup any of your FormAssembly forms structure (meta-data) for future, one-click restores in case of any sort of data disaster or even as a simple way of documenting the form structure?  

 

It is meant to provide the peace of mind of knowing you wouldn't have to re-create from scratch the form's structure, layout, field definitions, field constraints, etc. Let me know if you are willing to participate, thx.

6 comments
  1. Nov 18, 2025, 11:10 PM

    I didn't make that clear -- we are starting the beta test period on Dec 8 but will be keeping it open for a few weeks to give folks time to test at their leisure. 

0/9000

Hi everyone,

I’m building a FormAssembly form where users can enter multiple levels, each with an amount field inside a repeatable section.

I want to calculate the total amount by summing all of those amounts from each repeated entry.

I followed the usual process:

  • Created a repeatable Fieldset with a currency field named Amount
  • Marked the Amount field as a variable
  • Added a hidden subtotal field inside the repeatable section (Line Total)
  • Added a calculation field outside the repeatable section using @SUM(Line Total)

But the total field still throws an error or doesn’t calculate. 

 

Below is Attachment: 

 

calculate total amount from repeatable Amount field in formassembly

 

 

 

1 answer
  1. Oct 23, 2025, 2:57 AM

    It may be too late for this response, but this article helped me:  

     

    https://www.formassembly.com/blog/tutorial-how-to-use-calculations-and-repeating-sections-in-web-forms/#:~:text=First%2C%20you'll%20need%20to,directly%20in%20the%20form%20builder

     

    The subtotal field should be a variable too. In the Total Amount field you will add the name of this variable (subtotal) in the calculated field section. No formula required, just the name of the subtotal variable. 

0/9000

Hello Experts,

Could you please help me with the issues below?

1. A user reported that the Submit button is grayed out even though all the mandatory fields have been filled. This is currently preventing them from submitting the enquiry.

2. For one of the users, an error message appears saying “Thank you for submitting” when they try to submit the form with all the required details.

I would really appreciate it if anyone could help with a quick solution, as this issue is blocking users from submitting their enquiries.

Thank you!

#Salesforce Developer #Trailhead #Nonprofit
4 answers
  1. Oct 15, 2025, 11:37 AM

    @Ashwini Garwandha

     thank you. I have checked, and there is no rule added under it. 

     One of the users is seeing this error message when trying to submit the enquiry.  

    thank you. I have checked, and there is no rule added under it. One of the users is seeing this error message when trying to submit the enquiry.

     

    image.png

     

    image.png

0/9000
In FormAssembly, we have a Birthdate field on the form. How can we calculate the user’s age, display an error message if the age is less than 15, and prevent the form from being submitted?@FormAssembly @NPSP Admin #Nonprofit #Trailhead #AppExchange
2 answers
  1. Sep 11, 2025, 9:37 PM

    you can also just ask the question - are you younger than 15? Then add a conditional response that states, you are not eligible, etc and end the form.

0/9000

In form assembly if a step in the Salesforce connector fails, notification should be sent to group of users.  how can i do this..?

1 answer
0/9000

I have a FormAssembly form where a user is inputting in a date. I'd like to be able to manipulate that date in a couple of ways, but I'm unsure if I'm able to do so in FormAssembly. I'd like to be able to:

 

  • Construct a new date out of the entered date (based on the entered date, set it to the first of the next month for example) 
  • Add/subtract days from that date

 

I'm not seeing a clear way to do this with the formulas available. This date is also in a repeatable section so I don't think that I can use form calculations either. Has anyone had luck with this? @Nonprofit Success Pack  @Nonprofit Hub

10 answers
0/9000

I'm interested in getting started using secure parameters to prefill. I am used to using either a Classic or Lightning Email Template to send out a personalized link to the form to the recipient. 

 

I am kind of thinking that if I wanted the same approach, I would need to create a Visualforce email template instead (in the Classic Email Templates section in Setup) so that I can use the sample code that is described in this help article:

https://help.formassembly.com/help/508885-prefill-lookups-using-secure-parameters#dynamic-secure-parameters

 

 

That's the part where I am sort of stuck because I'm not sure what the best approach is. I have a very basic understanding of this. I believe I would need to write an Apex Class as a "

controller", right? And then I would need to write a "custom component

" to be able to include it in such an email template. 

 

Is that how I would be able to inject into the email template a URL that has the secure signature for a particular recipient?

2 answers
  1. Apr 25, 2025, 4:18 PM

    I don't know much about the secure parameters process, but I wanted to share how I was able to set up a dynamic way to build links for a form with the "unsafe query" parameter on any given record in case it helps in what you're trying to do.  

     

    I created 2 custom metadata objects (one for the form and one for fields on the form).

    FormAssembly Form just has a field for "form url" and "program" (so I can track which team it's relevant for). And as you can see FormAssembly Field has a field for the Field Alias, the FormAssembly Form

    record it's on, and the Unsafe Query Parameter built in the SF connector. 

     

    Using those has allowed me to create a formula field on our

    Site Visit object that can build a dynamic url for each record that we can attach to our calendar events for the field team to use when they need to complete a form for their inspection for a given client's opportunity.

0/9000

Has anyone successfully been able to obscure url parameters when using prefill?  For example if I want to pass the email field via the url to a FormAssembly form to use to prefill other fields on the form what would be the best way to do this.  

2 answers
  1. Jun 4, 2025, 5:52 PM

    Agreed, you do not want to pre-fill based on email alone -- then I could try email addresses of people I think are in your database and pull out the rest of their information that you are prefilling.  As @Josue Ramirez Bonilla noted I recently wrote a blog post where I strongly

    discourage using the Salesforce ID since they can be iterated over in a similar manner. 

     

    In short whatever you put in the URL needs to be something a bad actor cannot guess and/or try A LOT of?  So Email addresses they can guess a bunch. Ids they can test a large number in sequence. It

    might

    be okay to use email AND SFID depending on the level or risk you are willing to accept (this would likely hold off most bad actors in practice, but has theoretical weaknesses so if you data is high value I wouldn't use it). 

     

    You have a few options depending on your details:

    1. Generate a UUID for each person you are contacting, and have that trigger the prefill. This is the idea I discuss some in the blog post, and it includes some references to code that can help.
    2. Since you're on FormAssembly you can use their secure parameters pattern: https://help.formassembly.com/help/508885-prefill-lookups-using-secure-parameters
    3. Use SSO authentication from another system the users would be logged into anyway to limit who can reach the forms and what FormAssembly knows about them.
0/9000