[Bug] - NoSQL Workbench - CSV Export does not export the current data

Thank you for reporting this issue with NoSQL Workbench for Amazon DynamoDB. While I don't have specific information about this particular bug, I can provide some context about the CSV export functionality in NoSQL Workbench and suggest a potential workaround.

NoSQL Workbench does offer the ability to export query results to CSV files from the Operation builder. This feature is designed to allow users to share sample data with other developers or for testing purposes.

The behavior you're describing, where data from a previous table query is being exported when you've moved to a different table, does indeed sound like a bug. This is not the expected behavior of the tool.

As a temporary workaround, you might try the following steps:

1. After running a query or scan on a table, immediately export the results to CSV before moving to another table.
2. Before running a query on a new table, try closing and reopening the Operation builder to ensure it's not retaining data from previous operations.
3. If possible, work with one table at a time, completing all necessary exports before moving to the next table.

It's important to note that NoSQL Workbench is regularly updated, so make sure you're using the latest version of the tool. If the issue persists, it would be valuable to report this bug directly to AWS support or through the AWS forums to ensure it gets addressed in a future update.

Remember, NoSQL Workbench is a client-side application, so its behavior can sometimes vary based on your local environment. If the problem continues, you might also try uninstalling and reinstalling the application as a troubleshooting step.
Sources
Import and export CloudFormation templates and CSV sample data with NoSQL Workbench for Amazon DynamoDB | AWS Database Blog
NoSQL Workbench for Amazon DynamoDB now enables you to import and automatically populate sample data to help build and visualize your data models