BJ clarifies that child theme functionality works, allowing users to create a new theme that extends from Elevate by modifying the theme.json file.
Alex Woodbridge provides code to output dates in milliseconds for valid HubSpot datetime properties
Shar Ghavami suggests using a Python ETL script with pagination and setting up automated triggers to handle large exports.
Justin suggests doing a sample creation test via the API after the app is installed to determine the portal's capabilities.
Nicholas expresses interest in trying the theme after an upcoming deadline, indicating excitement about the latest updates.
Nicholas suggests troubleshooting steps: check if the expected image URL has a redirect. Try exporting the HubDB data, deleting all rows, and re-importing. Alternatively, create a new table, import the data, and point the dynamic page to the new table to isolate the issue.
Michael resolves the issue by adjusting the variable scope within the loop iteration.
BJ explains that Elevate is not currently shown in the Design Manager due to its project-based setup but provides a link to the documentation for building and deploying themes using projects.
BJ confirms Elevate uses a project-based architecture, which is likely why it cannot be seen or cloned in the Design Manager.
Lukas recommends using the CRM Search API endpoint (`/crm/v3/objects/contacts/search`) instead of the basic GET endpoint. The Search API allows filtering based on property values, including the `lastmodifieddate` property.
BJ notes that it appears Elevate is a new HubSpot default theme built using projects and not currently viewable in the Design Manager. He provides a link and mentions that it can be obtained through CLI for customization.
Leandro Michelena resolves the issue by including 'hs_object_id' in the request body.
No direct answer. Potential solution: Extract the phone field's default country code via JavaScript instead of external geolocation APIs.
No responses provided in the thread regarding viewing API call logs.
Zach Klein explains how to access logs via HubSpot's UI for Public or Private Apps and recommends checking backend system logs.
Zach Klein provides a PATCH example to update property options, highlighting that all options must be included in the request.
Jake Lett confirms boilerplate inclusion and suggests Bootstrap as alternative
Justin Givens advises using the campaign GUID with the /marketing/v3/campaigns/{campaignGuid} endpoint and 'hs_name' property.
Christopher suggests creating a syncing script hosted on AWS and setting up a cron job to run it periodically.
No responses provided in the thread regarding the API question.