Skip to content

Fields not listed on first refresh if collection key is forbidden #1978

@danielnelson

Description

@danielnelson

Bug

  1. Setup connector endpoint, click next.
  2. Add collection with a key that will be FORBIDDEN.
  3. Click refresh on field selection.

At this point it shows an error Field selection validation failed. If this issue persists, please contact support. and no fields are listed. Clicking on refresh a second time will show the field listing as desired.

Expected
Listing of fields displayed with a conflict marker on the collection key.

Screenshots

After first refresh:
Image

Browser logs when clicking refresh:
Image

Desktop (please complete the following information):

  • OS: Linux
  • Browser: qutebrowser

Additional context

This is with an in-development materialization for HubSpot, will share a draft of the code soon. With this materialization it may not be possible to write certain keys depending on the the state of existing properties in the destination system. In this case the expected way to address the issue would be to group by on a different field.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions