Chaincode only accepts the first contract in the export array - Typescript

[ajiths10]

Chaincode only accept the first contract in the export array.

• I've added super to each contract class.

• I exported the contracts like this:

  

• I have 2 channels - mychannel & garagecars

• I deployed the chaincode to both channels using these commands:

  
  ./network.sh deployCC -ccn basic -ccp /home/ajiths/Desktop/chaincode-typescript/ -ccl typescript -ccv 2.0 -c mychannel
  /network.sh deployCC -ccn basic -ccp /home/ajiths/Desktop/chaincode-typescript/ -ccl typescript -ccv 2.0 -c garagecars

 ### The first contract (AssetTransferContract) is accessible on both channels, but the other ones are not.

### Please advice me.

_Version - Latest_

[bestbeforetoday]

The problem might be the way your client application is invoking the smart contract. You need to explicitly request the correct contract within the chaincode package, for example:

const assetTransfer = network.getContract("basic", "AssetTransferContract");
const carGarage = network.getContract("basic", "CarGarageContract");

It seems that one of the contracts — for me, the first in the list — is selected as the default contract. The default contract is the one that will be called if you do not explicitly provide the contract name, for example:

const defaultContract = network.getContract("basic");

Note that the two contracts share the containing chaincode's namespace within the ledger so will have visibility of each other's ledger entries. If you want the ledger state of the two smart contracts to be separate, you should deploy them in separate chaincode packages.

[ajiths10]

The problem might be the way your client application is invoking the smart contract. You need to explicitly request the correct contract within the chaincode package, for example:

const assetTransfer = network.getContract("basic", "AssetTransferContract");
const carGarage = network.getContract("basic", "CarGarageContract");

It seems that one of the contracts — for me, the first in the list — is selected as the default contract. The default contract is the one that will be called if you do not explicitly provide the contract name, for example:

const defaultContract = network.getContract("basic");

Note that the two contracts share the containing chaincode's namespace within the ledger so will have visibility of each other's ledger entries. If you want the ledger state of the two smart contracts to be separate, you should deploy them in separate chaincode packages.

@bestbeforetoday This was the issue. This solved my issue. Thank you.

I have a suggestion as well. It was very hard to find this information in the community. I think we need to include this information in the documentation.

[bestbeforetoday]

@ajiths10 Which bits of information were missing for you? The client application side is documented in the API documentation:

• https://hyperledger.github.io/fabric-gateway/main/api/node/interfaces/Network.html#getContract

It seems that you discovered how to define multiple contracts OK. Again, this is described in the API documentation:

• https://hyperledger.github.io/fabric-chaincode-node/main/api/tutorial-using-contractinterface.html
• https://hyperledger.github.io/fabric-chaincode-node/main/api/tutorial-deep-dive-contract-interface.html

[ajiths10]

@ajiths10 Which bits of information were missing for you? The client application side is documented in the API documentation:

• https://hyperledger.github.io/fabric-gateway/main/api/node/interfaces/Network.html#getContract

It seems that you discovered how to define multiple contracts OK. Again, this is described in the API documentation:

• https://hyperledger.github.io/fabric-chaincode-node/main/api/tutorial-using-contractinterface.html
• https://hyperledger.github.io/fabric-chaincode-node/main/api/tutorial-deep-dive-contract-interface.html

I never thought it was on the client side. Anyway, thanks for the support :+1: . The issue is resolved, so I'm closing this issue.