A table that is being excluded is also being used as a starting table. This creates a conflicting configuration.

Why this is a problem

Excluded tables are completely ignored during subsetting, but starting tables are the entry points for data selection. A table cannot be both ignored and used as a starting point.

How to fix

Choose one of these approaches:

Option 1: Remove from starting tables

Keep the table excluded and find a different starting point:

{
  "startingTables": [
    // Remove the conflicting table from this array
  ],
  "excludedTables": [
    {
      "schema": "dbo",
      "name": "ConflictingTable"
    }
  ]
}

Option 2: Remove from excluded tables

Use the table as a starting point and allow it to be processed:

{
  "startingTables": [
    {
      "table": {
        "schema": "dbo",
        "name": "ConflictingTable"
      },
      "filterClause": "Status = 'Active'"
    }
  ]
  // Remove from excludedTables array
}

Common scenarios

Audit tables: Often excluded but sometimes needed as starting points for compliance data

Log tables: Usually excluded but may be required for specific time-based subsets

Archive tables: Typically excluded but might be starting points for historical data analysis