I am comparing patterns of passing/using contractId vs contract Keys when creating associations between contracts. Example a contract representing an “organization”: the org can create a “department”: the department uses a key or a contract ID of the org? (or there could be a party per org). Is t…

Off the top of my head, using the org and department example, seems like best method is to use keys. For example, you create an org contract with the name “BadlySpelledOrgName”, then a department contract. If the department contract references the “BadlySpelledOrgName” via contract ID, and the org…

What about using the contract itself as a reference key? Like this: template A with p : Party where signatory p nonconsuming choice CreateB : ContractId B controller p do create B with a = this template B with a : A where signator…

What does that look like when it gets serialized?

contractId vs key use cases / patterns for establishing parent-child relationships

App Development

a_putkov October 3, 2022, 8:05pm 5

Update for housekeeping purposes. The answer to this question is provided on a separate thread here.

Topic		Replies	Views
Related Contracts App Development daml	1	210	September 22, 2022
Pros and cons of keeping a reference to a contract as a parameter of another contract App Development	4	437	May 7, 2020
ContractIds in contract keys App Development	3	410	March 10, 2022
Use self-type in contract keys App Development daml	3	574	March 9, 2021
Should I store contract Ids on other contracts? App Development daml	5	675	December 7, 2020

contractId vs key use cases / patterns for establishing parent-child relationships

Related topics