DataSet physicalTable Id and logical Table IDs

Question & Answer
,
1

I’m creating the same dataset say for 50 customers in a single quicskight account. I’m creating all datasets via code and boto3 API. Where in the code I define sql query, logical tables, and columns.
When it comes to physical Table IDs and Logical Table Ids, do they need to be unique?

For instance I’m creating GenericDataset 50 times. For each one of those datasets, my physicalTableId will be GenericDataset, where the id is not unique per dataset… is this an issue? Is there any chance on dataset creation of company2, it will pull the physicalTableId of company1 because they are the same?

Thanks.

2

@evanbetterc ,

You can get code sample and steps for creating dataset programmatically using boto library at this content porting demonstration link: Porting Content :: QuickSight DevOps

physicalTableIDs identifier maps fields in dataset between PhysicalTableMap relation-table (Datasource,schema,table) and LogicalTableMap (representation of data-field in QuickSight). physicalTableID need not be unique across dataset definitions however DataSourceArn within physicalTableMap need to be unique if all datasets are pointing to different datasources.

I am not sure what you mean by “Logical Table Id”. Please elaborate. Here is the document explaining dataset creation parameter via API: create-data-set — AWS CLI 1.31.11 Command Reference

Let us know if this is resolved. And if it is, please help the community by marking this answer as a “Solution" (check box under the reply)

Regards,
Anwar Ali

3

thank you, this answered my question. needed to know if physical Table ID is only contained within a singular dataset definition.

4

Logical Table ID are the other Ids I see referenced in a logical table map.