Practice: test three Salesforce account scenarios, then isolate one row

In a sandbox, prepare a suite that reads account name and type from a CRT data table and verifies the created account. Use disposable demo records, not production data.

Create ./data/accounts.csv using the sample rows below. Match its column names to the suite’s configured data-table bindings; importing a CSV alone does not make the script consume those columns. Replace <table-id> with the ID returned by creation.

# Sample ./data/accounts.csv (adapt columns to your suite):# ACCOUNT_NAME,ACCOUNT_TYPE# CRT_Demo_Prospect,Prospect# CRT_Demo_Customer,Customer - Direct# CRT_Demo_Partner,Channel Partner / Reseller$ agentia testing data-table create --project <project-id> \  --name Account_Matrix --file ./data/accounts.csv$ agentia testing data-table export <table-id> --project <project-id> \  --datasets 1-3 --output ./data/accounts-preview.xlsx$ agentia testing job run <job-id> --project <project-id> --datatable <table-id>:1-3$ agentia testing job run <job-id> --project <project-id> --datatable <table-id>:2

Check your results

• Review the upload preview and exported spreadsheet: row 1 is Prospect, row 2 is Customer - Direct, and row 3 is Channel Partner / Reseller. Dataset numbering starts at 1, excluding the header.
• The first command selects all three datasets. Inspect each dataset’s result rather than treating a batch as a single test.
• The second run isolates only row 2 for debugging. Verify the account values and clean up the disposable records using your team’s sandbox procedure.