🐛 Source CIN7: fix product_availability primary key for multi-location …

[alex-birch]

What

Fixes the primary key configuration for the product_availability stream in the CIN7 connector to support multi-location inventory tracking.

Problem

The current primary key configuration uses only [ID] (product ID), which prevents the same product from being tracked across multiple locations. This causes data loss during deduplication when a product exists in multiple warehouses/locations.

Solution

Changed primary key from [ID] to [ID, Location] to create a composite key that uniquely identifies each product-location combination.

Why

• CIN7 supports multi-location inventory management
• The Location field is required per CIN7 API documentation
• This enables proper incremental sync with deduplication for multi-location scenarios
• Prevents data loss when products exist across multiple locations

Testing

• Verified Location field is marked as required in CIN7 API docs
• Confirmed both ID and Location are non-nullable fields suitable for primary key

https://help.core.cin7.com/hc/en-us/articles/9034523140879-ProductAvailability

Files Changed

• airbyte-integrations/connectors/source-cin7/manifest.yaml

[vercel]

@alexbirch-xy is attempting to deploy a commit to the Airbyte Growth Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

👋 Welcome to Airbyte!

Thank you for your contribution from alex-birch/airbyte! We're excited to have you in the Airbyte community.

Helpful Resources

• PR Guidelines: Check our guidelines for contributions.
• Developing Connectors Locally: Learn how to set up your environment and develop connectors locally.
• If you enable BYO Connector Credentials within your fork, you can view your test results here:
  

PR Slash Commands

As needed or by request, Airbyte Maintainers can execute the following slash commands on your PR:

• /format-fix - Fixes most formatting issues.
• /bump-version - Bumps connector versions.
• /run-connector-tests - Runs connector tests.
• /run-cat-tests - Runs CAT tests.
• /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).

If you have any questions, feel free to ask in the PR comments or join our Slack community.

Tips for Working with CI

1. "Vercel" CI failures. You can always ignore these. These are our docs builds but they can only be run by approval. A maintainer will approve the workflow upon request, but this failure should not be of concern.
2. Pre-Release Checks. Please pay attention to these, as they contain standard checks on the metadata.yaml file, docs requirements, etc. If you need help resolving a pre-release check, please ask a maintainer.
   • Note: If you are creating a new connector, please be sure to replace the default logo.svg file with a suitable icon.
3. Connector CI Tests. Some failures here may be expected if your tests require credentials. Please review these results to ensure (1) unit tests are passing, if applicable, and (2) integration tests pass to the degree possible and expected.
4. (Optional.) BYO Connector Credentials for tests in your fork. You can optionally set up your fork with BYO credentials for your connector. This can significantly speed up your review, ensuring your changes are fully tested before the maintainers begin their review.

[cgardens]

Thanks for your contribution. Please fix the merge conflicts and then we can get this merged.

[alex-birch]

Thanks! Conflicts resolved and latest master merged, ready for review.

[alex-birch]

Hi there - I've updated the branch again to be inline with the latest master.

@cgardens Is there anything else I need to do to get this merged?

[alex-birch]

Hi there - I've updated the branch again to resolve the conflicts.

@cgardens Is there anything else I need to do to get this merged? I'd really like to get it in so I can start using Airbyte's connector.

[cgardens]

/run-connector-tests

Connector CI Tests Started

These tests will leverage Airbyte's integration test credentials.

Check job output.
✅ Connector CI Tests job completed successfully. See logs for details.

[cgardens]

/run-connector-tests

Connector CI Tests Started

These tests will leverage Airbyte's integration test credentials.

Check job output.
✅ Connector CI Tests job completed successfully. See logs for details.

[cgardens]

Thank you for your contribution!