Here we’ve compiled the most common questions from support emails and customer calls. If your question isn’t listed here, please contact us: hello@propform.io.
In 9 out of 10 cases, this is due to the API permissions of the onOffice user — the ‘Private’ checkbox ticked on the address, missing group assignment in the Groups module, restricted record permissions on templates, etc.
Most common causes:
> The field list is updated once a day in the morning and when the form overview is opened. If you have just created a new field in onOffice, reload the form overview in propform.
More on this: Connect to onOffice.
Most common causes:
This typically occurs if the recipient’s email address exists in onOffice only as a secondary or tertiary address. In this case, propform automatically creates a new address record with this email address so that the email reaches the correct person — see the description in the chapter Email Notification.
Via download fields — configurable by document attribute, file pattern, PDF preview on-the-fly or fixed URL. Multiple files are automatically bundled into a ZIP file. Full instructions: Download fields.
Most common causes:
propform automatically converts iPhone HEIC images to JPEG before they are uploaded to onOffice — you don’t need to do anything.
In the field settings of the file upload field, you’ll find the option “Merge multiple files into …” — select ZIP or PDF. Handy, for example, for multiple photos from the planning office.
> For PDF bundling: Only images and PDF files work. Other file types would cause the PDF build to fail.
Most common causes:
address[ID]=... (capital I, capital D), Property: estate[Id]=... (capital I, lowercase d)Four possible causes: (1) Record has been deleted, (2) API user lacks read permissions, (3) Sharing/record permissions are too restrictive, (4) Record is marked as “Private”. Full diagnosis at Address record UUID not found.
CSRF token expires after 24 hours. Solution: Reload the form and repeat the entries. More information at Form has expired.
Use the relevant UUID macro:
https://propform.io/form/dein-slug?address[ID]=_Uuidaddress&estate[Id]=_Uuidestate
_Uuidaddress and _Uuidestate are automatically replaced by onOffice with the UUIDs of the linked records when the email is sent.
If an expiry date is required in the form settings, the form URL must contain ?exp=YYYY-MM-DD HH:MM:SS — and the date must be in the future. You can set the expiry date statically or have it calculated dynamically using an onOffice formula (e.g. “14 days from submission”). More under Account → Expiry date.
We host Google Fonts locally for data protection reasons (no connection to Google when the form is accessed). If your preferred font is missing, please drop us a quick line at hello@propform.io — we’ll add it for you.
Use the iFrame embedding option in the form settings. Tips for seamless integration:
Most common cause: iFrame width/height are incorrect or your website’s parent container is too narrow. More under Form is displayed incorrectly.
Most common cause: Incorrect macros (address macros are in CamelCase, property macros are in lower case) or address fields are being addressed directly instead of via the pre-macro _Kaeufer / _Eigent. More at Values are not transferred to the PDF.
By default, automatically via a hidden honeypot field plus CSRF token verification. More at Spam protection & bot defence.
Currently only via a manually translated copy at a separate URL — automatic multilingual support is on the roadmap. More at Multilingual forms.
Tracking scripts should ideally be placed directly within the form (Form settings → Tracking), not just on the embedding page. More at Tracking in embedded forms.
Using two interacting forms (Overview + Edit) plus recursive address loop macros (_buyerbrek_1_ / _ownerbrek_1_). Full instructions with code examples at Linking multiple records or a short FAQ at Linking multiple buyers / owners.
Via Filters per form — propform only queries records that are in the onOffice filter. Protection against UUID manipulation. More at Filters per form.
Overview of all available protection mechanisms (honeypot, IP whitelist, form password, form key via URL, expiry date, UUID requirement) under Form protection & access control.
Using the form setting “Property and/or address required for form calls” — prevents URL tampering and the accidental creation of empty records. Important for download and edit forms. More under Form Protection → UUID Requirement.
Yes — in the “Conditions and Rules” tab using the “Calculate value” action and pipe syntax: {{multiply:field:X|field:Y|/100}}. Full instructions with examples under Conditions & Rules → Calculations between fields.
Via the Conditions and Rules Editor in the form settings — GUI-based, without field IDs from DevTools. More at Conditions & Rules.
Yes — numeric fields can be configured as a special ‘Range Slider’ field (Min/Max/Interval + labels). More under Calculated Fields & Special Field Types.
Yes — Auto-Submit forms redirect directly upon being called. Plus: The thank-you page URL can be directed to different destinations via _calculate(IF(...)) depending on the field value. More under Auto-Submit & Conditional Routing.
Via a self-service setup: an overview email with a loop using _bScRek_("status:1") + one-click buttons (_pfButton) to editing and deactivation forms. Full pattern under Edit / deactivate search profiles.
Most common cause: the field was created in onOffice within an alternative search criteria template, but the API only reads the default template. Solution: Transfer the field to the default template. More at Search profiles → Pitfalls.
Depends on your setup — radius is simpler, regional add-on is more granular. Compare under Search profiles → Geographical search.
No — it’s better to duplicate it and clear the old transaction data (signatures, documents, notes) in the new listing. More at Duplicating a property for re-marketing.
Formulas are only calculated when saving. Workaround: bulk update without changes. More at Recalculate formula fields.
Add your OpenAI API key in your account settings → enable it in the form settings. Full instructions including setup, costs and privacy information at AI features.
Very affordable — typically under $1 for 100 voice inputs or auto-fills. You pay OpenAI directly based on usage. Details under AI Features → Costs.
Go to Account settings → Default form styling. More information at Design & Branding.
Drop us a quick message with the font name — for fonts available via Google Fonts, we’ll integrate them free of charge within 1–2 working days.
Yes, all features are available regardless of the billing method. Marketplace only affects authentication and the subscription model.
Please contact us with as many details as possible:
📧 hello@propform.io 📞 0163 / 64 18 132