Fabio Alves
- Total activity 84
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 30
- Subscriptions 33
Posts
Recent activity by Fabio Alves-
Improve feature request UI and UX
AnsweredI would like to be able to search the list of feature requests, e.g. for key words in a search bar. Right now, I can't tell if the feature I'm requesting has already been raised and I should upvote...
-
Claude Workspace table: add tags column
AnsweredConnector name: Claude (https://fivetran.com/docs/connectors/applications/claude) Table name: workspace Column to add: tags API documentation link: https://platform.claude.com/docs/en/api/http/beta...
-
Other: Add UUIDs to notifications so we can link creation and resolution notifications
AnsweredCurrently, we have notifications set up for our connectors, which trigger alerts, e.g. when a sync is delayed. For example, we would typically get these 2 notifications sent via email: Subject: [...
-
Other: Sync schedule is maintained after a schema change
When I make changes to a schema definition for an existing connector, e.g. add a new table or rows, I don't necessarily want a sync to be triggered as soon as I hit `save`. Some connectors are set ...
-
Connector Improvement: Oracle Business Intelligence Publisher - sync tables without a primary key
CompletedCurrently, the connector does not allow us to sync data from tables without a primary key defined, as outlined in the documentation. Fivetran marks the source tables as Excluded By System in the ...
-
Connector Improvement: Jira connector, add column DRIVER
In the `version` table we'd like to have the `driver` field added. According to the Jira ERD, this data is coming from the Get version endpoint. This endpoint returns the `driver` object; this is ...
-
Connector Improvement: Relax the schema and table naming rules
We want to use Camel case to name datasets and tables created in BigQuery to match internal style guides. Currently, you have a set of rules for schema names as well as table names which means that...
-
Connector Improvement: Google Cloud Function: Allow loading of repeated records
Not plannedIt would be great if we could make use of the BigQuery functionality to load nested and repeated data. Currently, it looks like it is not possible to create a response object with this kind of data...
-
Connector Improvement: Google Cloud Function: Allow users to explicitly define schema
Not plannedIt would be good to have the ability to explicitly define the schema for the fields in the response object data. As defined in the BigQuery documentation, it would be good to be able to provide a J...
-
Connector Improvement: Google Cloud Function: Allow 'Error' Response Objects
CompletedIt would be great to be able to pass response objects which will cause the dashboard to show the sync status as FAILED as well as some relevant error information. We have a few Cloud Function conne...