Binding overview does not show candidates to assign

Client
, , ,
1

Hi,

In my project we have been introduced binding overview within CDM form. To make it more details i attached a picture here:
When i click on new quote to create new contract → assign client ( executed rpc to LIST_CANDIDATES including client, broker, and vehicle) → move to vehicles tab and click on edit to show binding overview to assign vehicle for contract → working fine
I save the contract and open it again → move to vehicles tab to assign again then binding overview does not show any vehicle to assign ( as far as i see there is no rpc LIST_CANDIDATES called when i re-open the contract.
Talked to TPS and models look correct.
Do you have any ideas ?

image
image2461×1135 50.2 KB

After saving and re-open it again

image
image2473×1184 56.2 KB

2

Hey, could you please attach the Models? In which ext version are you working?

So you open the same form for the same document. The only difference is, that it is first a new document (not persisted yet) (-> working) and then an already existing document (persisted and retrieved from DS) (-> not working) ?

3

Hi @felix-blazing-river , i attached my models below:
Vehicle.json (6.5 KB)
Vehicle_form.json (6.7 KB)
Vehicle_overview.json (2.6 KB)

BrokerContract_relationship.json (2.1 KB)
BrokerContract_relationship_Broker____generated.json (1.4 KB)
BrokerContract_relationship_Contract____generated.json (1.5 KB)
ClientContract_relationship.json (2.1 KB)
ClientContract_relationship_Client____generated.json (1.5 KB)

ContractCoverageCategory_relationship.json (2.1 KB)
ContractCoverageCategory_relationship_Contract____generated.json (1.5 KB)
ContractCoverageCategory_relationship_Contract____generated.json (1.5 KB)
ContractCoverageCategory_relationship_CoverageCategory____generated.json (1.5 KB)
VehicleContract_relationship.json (2.0 KB)
VehicleContract_relationship_Contract____generated.json (1.5 KB)
VehicleContract_relationship_Vehicle____generated.json (1.4 KB)
VehiclesCoverageCategory_relationship.json (2.1 KB)
VehiclesCoverageCategory_relationship_CoverageCategory____generated.json (1.5 KB)
VehiclesCoverageCategory_relationship_Vehicle____generated.json (1.5 KB)
Broker.json (1.7 KB)
BrokerageOffer_form.json (3.2 KB)
Broker_overview.json (4.8 KB)
BrokerageOffer_form.json (3.2 KB)
BrokerData.json (8.7 KB)
ALD-Brokerage.json (3.2 KB)
Client.json (4.6 KB)
Client_form.json (21.7 KB)
Client_overview.json (5.6 KB)
ClientData.json (18.3 KB)
CoverageCategory_CDM.json (3.2 KB)
CoverageCategory_form.json (48.9 KB)
DocumentData.json (10.7 KB)
MetaData.json (4.0 KB)
CoverageCategory.json (60.2 KB)
BrokerContract_relationship_Broker_AvailableItemsOverview.json (1.3 KB)
BrokerContract_relationship_Broker_SelectedItemsOverview.json (1.4 KB)
BrokerContract_relationship_Contract_AvailableItemsOverview.json (1.5 KB)
BrokerContract_relationship_Contract_SelectedItemsOverview.json (2.1 KB)
ClientContract_relationship_Client_AvailableItemsOverview.json (1.3 KB)
ClientContract_relationship_Client_SelectedItemsOverview.json (1.4 KB)
ClientContract_relationship_Contract_AvailableItemsOverview.json (1.5 KB)
Contract_overview.json (15.5 KB)
VehiclesCoverageCategory_relationship_Vehicle_SelectedItemsOverview.json (1.6 KB)
VehicleContract_relationship_Vehicle_SelectedItemsOverview.json (1.6 KB)
VehiclesCoverageCategory_relationship_Vehicle_AvailableItemsOverview.json (1.8 KB)
VehiclesCoverageCategory_relationship_Vehicle_SelectedItemsOverview.json (1.6 KB)
DnoContract.json (76.4 KB)
DnoContract_CDM.json (6.4 KB)
DnoContract_form.json (94.9 KB)

4

I tested the models in the PreviewApp with some testdata and there it works as expected. (So the models and standard implementation seem to work correctly)

Is there custom code you execute on form loading? This might produce an error which stops the further processing (including the rpc call)?

5

Hi @chien-calm-dune,

did you find the cause for the issue? If you stil require support regarding this topic, please give us the additional information that @felix-blazing-river requested.

Denise from the Discourse team

6

Hi @denise-narrow-token , yes we found the solution and its fixed in our custom code. And this topic can be closed, sorry for not taking this as done