Any time you set up a new Extractor connection, we generate a unique ID number for it. The number helps identify that specific extractor connection as the source of the transaction data imported by it into Avalara. That number is the data source ID.
You've probably already seen it and not even realized what you were looking at.
- It's on the tile for an extractor connection on the Integrations page. The tile for the connection of the examples that follow would have data source ID 4102 on it.
- In location codes on transactions imported by an extractor, it's the last segment of a location code. For example, 4102 is the data source ID in the following location code: Amazon_DATASOURCE_WA_4102.
- In document codes on transactions imported by an extractor, it's the last segment of a document code. For example, 4102 is the data source ID in the following document code: 1234567890~&4102.
In transactions imported before March 29, 2021, it's the second segment of a document code. For example, 4102 is the data source ID in the following document code: A.4102.1234567890.
If you delete an extractor connection and then set it up again, the connection has a new data source ID.
Before you delete the first extractor connection, you should also use a data source ID to find and resolve errors with transactions imported by that connection.
After you set it up again, the data source ID helps you know which transactions are coming from the new connection.