This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture.
I've had my eye on Plumsail Forms for MS365 for a few years now, and even went through a trial period last year, but I didn't have much time to test it out during that time. I requested a second trial period via email around end of day, and by morning, I had support reply letting me know I was back in. That was a good sign by itself.
Within a few days, it became abundantly clear that I should've given Plumsail my full attention ages ago. There are countless benefits over base SharePoint and Lists forms, even those with JSON formatting, and further benefits over time spent developing custom SPFx React form solutions. Within the past month, I've been able to create a custom order system for a new departmental initiative, partially redesign our current RFQ process, make our vendor database much more useful, and add lookup functionality to an existing equipment management list.
Because it takes so little time and effort to get a form up and running, I plan to use Plumsail Forms anywhere there's even a slight benefit over out-of-the-box options. This is what form building should be on basically every platform. The documentation is extensive, and many of the guides are also available in video form. The developers are extremely active in the community forum, with nearly every thread receiving a direct and informative reply from a member of the team. The 100% transparent and incredibly generous price structure -- one license for the entire SharePoint tenant regardless of user count -- is a breath of fresh air in an industry obsessed with oddly secretive "contact us for pricing" and/or per-user monthly subscription costs.
Note: My high praise notwithstanding, I've been using this software for only about a month, so there may be limitations I'm not yet familiar with. That said, t Review collected by and hosted on G2.com.
For some, the need to use JavaScript to customize forms might be off-putting. As someone with only basic JavaScript knowledge, I was initially skeptical about this myself, but the developers seem to have made it as accessible as possible: there are universal field selectors to access both data and properties, and many of the code examples in the documentation will work with a simple copy, paste, and replacement of a single term. It does help substantially to understand the logic, however.
I have slight concerns about the use of field customizers for cross-site lookups long term because Microsoft briefly indicated they'd be phasing out SPFx field customizers. However, this concern didn't change my purchase decision for two reasons: one, Microsoft quickly retracted the phaseout after developer outcry, and two, Plumsail responded to a forum post about the issue with an immediate willingness to redevelop the lookups feature to use column formatting instead of SPFx. Review collected by and hosted on G2.com.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through a business email account
Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.
