-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source Hubspot: fix the FieldAnchor closing tag #33257
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@roman-yermilov-gl thanks! Looks like you can use a field anchor within the Hide In UI feature. But why are we doing so? |
If you set up your connections before April 15th, 2023 (on Airbyte Cloud) or before 0.8.0 (OSS) then you'll need to do some additional work to sync custom CRM objects. | ||
|
||
First you need to give the connector some additional permissions: | ||
|
||
<!-- env:cloud --> | ||
- **If you are using OAuth on Airbyte Cloud** go to the Hubspot source settings page in the Airbyte UI and re-authenticate via OAuth to allow Airbyte the permissions to access custom objects. | ||
<!-- /env:cloud --> | ||
- **If you are using OAuth on OSS or Private App auth** go into the Hubspot UI where you created your Private App or OAuth application and add the `crm.objects.custom.read` scope to your app's scopes. See HubSpot's instructions [here](https://developers.hubspot.com/docs/api/working-with-oauth#scopes). | ||
|
||
Then, go to the replication settings of your connection and click **refresh source schema** to pull in those new streams for syncing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I personally would continue to hide this. Definitely makes sense to tell users that their custom objects will be available as well though!
What
Fix the problem from #33042. Documnetation is broken
How
Remove autoclosing
/
from<FieldAnchor />