A derived transaction portfolio inherits all the transactions of its parent transaction portfolio at the moment it is created.
A transaction in a derived portfolio is therefore a live copy of the same transaction in the parent. The derived transaction inherits all subsequent updates to the parent transaction, whether this is a change to a field or property value, or cancellation of the transaction itself. However, it is possible to break this link if you update the derived transaction, at which point it stops inheriting changes.
In summary:
A derived portfolio inherits all transactions from the parent portfolio at the moment it is created:
You can add new transactions to the parent portfolio and they are automatically synced to the derived portfolio:
You can add new transactions to the derived portfolio but they are NOT synced to the parent portfolio:
You can update an existing transaction in the parent portfolio and the change is synced to the same transaction in the derived portfolio:
You can update an existing transaction in the derived portfolio but the change is NOT synced to the same transaction in the parent portfolio:
Furthermore, the link between the portfolios for this transaction is now broken; further changes to the transaction in the parent portfolio are now NO LONGER synced to the derived portfolio:
