ExhibitRefer to the exhibit.

In the provided data model, both the CurrentOffice and Transaction tables contain the fields SalesID and Office. This leads to the creation of a synthetic key in Qlik Sense because of the two common fields between the two tables. A synthetic key is created automatically by Qlik Sense when two or more tables have two or more fields in common. While synthetic keys can be useful in some scenarios, they often lead to unwanted and unexpected results, so it’s generally advisable to resolve them.

In this case, the goal is to have both the current office of the salesperson and the office where the transaction occurred visible in the data model. Here’s how each option compares:

Option A: Comment out the Office in the Transaction table:This would remove the Office field from the Transaction table, which would prevent you from seeing which office the salesperson was in when the transaction occurred. This option does not meet the requirement.

Option B: Inner Join the Transaction table to the CurrentOffice table:Performing an inner join would merge the two tables based on the common SalesID and Office fields. However, this might result in a loss of data if there are sales records in the Transaction table that don’t have a corresponding record in the CurrentOffice table or vice versa. This approach might also lead to unexpected results in your analysis.

Option C: Alias Office to CurrentOffice In the CurrentOffice table:By renaming the Office field in the CurrentOffice table to CurrentOffice, you prevent the synthetic key from being created. This allows you to differentiate between the salesperson’s current office and the office where the transaction occurred. This approach maintains the integrity of your data and allows for clear analysis.

Option D: Force concatenation between the tables:Forcing concatenation would combine the rows of both tables into a single table. This would not solve the issue of distinguishing between the current office and the office at the time of the transaction, and it could lead to incorrect data associations.

Given these considerations, the best approach to resolve the synthetic key while fulfilling the requirement of having both the current office and the office at the time of the transaction visible is toAlias Office to CurrentOffice in the CurrentOffice table. This ensures that the data model will accurately represent both pieces of information without causing synthetic key issues.