Robert points to HubSpot's built-in cookie settings and JS API for advanced customization.
Jeff proposes creating child deals associated with the parent deal or using line item properties for status/dates.
In order to use the HubSpot Form component effectively, you can hook into the form's properties to manipulate fields based on user input and manage state accordingly in React.
Joe explains that the hs_marketable_status property uses boolean values (true/false) instead of strings, aligning with the API's expected format.
Ahmed suggests using HubSpot's Terms checkbox, Quotes acceptance, or HTML blocks for custom signature fields.
Ryan indicates this requires a UI Extension, which is available in Enterprise Hub tiers.
Aldo confirms portal ID and object ID are included by default in CRM card requests.
BJ Szyjakowski recommended using GitHub Actions with the HubSpot CMS Deploy Action to automate multi-account deployments.
Ahmed recommends using the CMS Pages API to fetch articles and sort them locally by visits, as the API doesn't support direct sorting by visits.
Roger clarifies that private apps use access tokens instead of OAuth and do not support Client ID or redirect URL configuration.
Ahmed recommends Zapier for cost-effective integration, noting its scalability limitations but suitability for POC stages.
Ahmed offers to share a process flow chart example for visualizing the workflow steps.
Ahmed confirms it's possible via reverse proxy setup and URL redirects for landing pages.
Ahmed advises using a single checkbox field and converting the string value to a boolean in code.
Federico mentions modifying module.js before uploading, acknowledging the common need for adjustments.
Ahmed suggests ensuring permissions exclude sensitive data, using HubSpot Teams, and setting CRM object permissions to 'Team only' or 'Owned only'.
Anton Bujanowski lists options like global modules, HubDB, or theme variables to manage dynamic images
Nick resolves the issue by implementing a callback function to return output
Ahmed and Ashish provide CSS media queries and class-based targeting to toggle CTA visibility by device.
Maximilian suggests using workflows with custom properties or GraphQL to enforce association constraints.