Evelynn mentions a beta cookie scanner under Privacy & Consent settings, though access may be limited.
Re-authenticating the app after adding scopes was suggested but did not solve the issue for Pieter. No definitive solution was provided in the thread.
Stefan Jaeger confirmed this is possible using custom code to make API calls to fetch the Deal ID and update the associated line items. Andreea later confirmed this approach worked for them.
Erick suggests using a HubDB workaround or external automation. Pietro implements a multi-select checkbox via API.
Carter McKay confirmed that accessing comments on Tasks and Notes via the API is still not supported and is not currently prioritized on the roadmap.
The user discovered they were using the wrong endpoint. They likely needed the standard Marketing Single Send API (`/marketing/v4/email/single-send`) which requires the `marketing-email` scope, rather than the Transactional Email API which requires a specific paid add-on in addition to the `transactional-email` scope.
Harpreet and Shakil recommend optimizing plugins, images, caching, and CDNs, offering further assistance.
No specific technical solution was provided in the thread, but Ryan Ginsberg offered to discuss potential approaches via direct message, indicating a custom solution likely involving API calls is needed.
Kiara confirms customers do not need early access; App Cards are available once the app is published.
Harun Kumar Siva suggested using the 'Read a Contact' endpoint (`GET /crm/v3/objects/contacts/{email_address}`) with the query parameter `idProperty=email`. This allows fetching a contact using either their primary or additional email address.
Stefan Jaeger suggested checking different phone fields (e.g., phone, mobile_phone, company phone) to locate the correct value.
The question was deemed unclear and needed clarification. Stefan Jaeger asked for more details on what 'join' meant in this context. No specific solution was provided.
No solutions or answers were provided by the community.
No responses or solutions were shared regarding purging the CDN cache.
Roger Brown clarified that developer accounts are intended for public app development, which requires beta enrollment and approval. Furthermore, projects built as private apps (in test/customer accounts) need refactoring to work as public apps deployable via a developer account due to architectural differences.
Harun Kumar Siva clarified that logs don't show body/headers for successful requests. Jacob discovered the issue was that he was searching for an 'additional email', not the contact's primary email, which the search endpoint didn't cover.
Stefan Jaeger suggested the limit is likely 100 per request, aligning with HubSpot's standard API pagination limits.
Matt identified that having both `fields.js` and `fields.json` in a module caused the error. Removing one resolved the issue.
No solutions were suggested in the responses to Chris's query.
The issue was resolved by correctly formatting the `properties` query parameter. Instead of passing a list/array structure, the properties should be passed as a comma-separated string.