When forms are used as web tickets or other types of important requests forms, it would be helpful to be able to add the company record ID in a field in the form in order to more effecientally and effectively be able to associate that form to the company.
Yes! I have several processes that require us to gather information from customers over several weeks or months. I need that information to get logged back to the service ticket or deal it relates to, and there is no way to do that at the moment.
Hi @ABedoya, I agree, it would be great if the company record ID could be available as a de-duplication and identification field on the forms. This would allow us to have it as a hidden field and use custom codes to generate links that use query strings to pre-populate the field before we send it to a client. Allowing us to tell the form specifically which record to update. In it’s current state the company fields are useless unless you want mass duplicates as it only uses domain cross checking to check for existing companies which is rarely a reliable field.
While certainly not an easy fix and it won’t work for everyone. But for forms we manually send to clients to fill out, a current work around for our team is I’ve created additional fields on the contact level for the fields I want to update on the company level as well as a UID field. I then hide the UID field on the form and use the contact fields in the form in place of the company fields. I pre-populate the UID field with the companies record id using query strings as outlined here. Then use a webhook to identify form submissions and update the company via API.
Definitely want this, My current work around is to create a second record ID field (that is set as unique too), use a workflow to copy the record ID to this field, and use this field instead, it worked great until someone else saw the field and started basing their imports on this field instead of the hubspot record ID, and some issues with deduplication caused the wrong IDs to remain so new objects where created instead of it being merged creating a whole new dedupe issue…
Would be better if I could just make record IDs available in forms.
I have solved this by using Zapier to monitor new incoming form submission, and I created a second “record ID” and using that as a hidden field on the form, and by giving the customers a prefilled link with customer id parameter we can match that against the contact using Zapier. Would be a lot easier to just use the actual record ID field of course.