Converting Logical to Physical model shows duplicate columns (4248928)

Having issues converting a Logical model to a Physical model, related to logical relationships becoming foreign keys in the physical and duplicating columns in the child table. The Logical model was created with 2 entities, and the parent entity (Client) had a 1-many relationship with the child entity (Account). The relationship would define an FK in the physical. The simple conversion option was used to convert the Logical to Physical. The new diagram shows the Account table having the ClientId (the PK of the parent table) listed twice. The original column that was added, plus the ClientId added as part of the FK that Toad generated. 

It is assumed that Toad generates the column since it is the attribute of the FK. Visually this seems odd, but also, if the DDL is generated, this causes the duplicate column to appear in the DDL. To avoid the issue, the ClientId column can be removed from the Child table in the logical, so when it generates the Physical the column gets added. This would work for this simple case, but leaves attributes missing as part of the logical model (It then looks odd for the Logical model diagram). This does not appear to be a bug, but is there a simple solution that would allow users to add required attributes to both parent and child entities in the logical and have the physical conversion not generate duplicate attributes (at least for simple cases)?