RE: deep insert custom entities 1:n relationship odata api
Hi Max,
It might be caused by fieldname of your child entity(Claim) is not correct:
The field name is case sensitive, e.g:
I have a custom entity Country, and the relationship between Country and Contact is 1:N,
When creating a Country with multiple contacts, if my data is something like below:
{
"new_name": "Clofly Republic",
"new_new_country_contact_Country": [
{
"Firstname": 'Clofly',
"Lastname": 'Mao'
}
]
}
As you can see, fields of Contact entity are "Firstname" and "Lastname", then I encountered same error if I keep the wrong name.
After changing them to firstname and lastname, it works.
Therefore, I suggest you could change dsl_DocumentNumber, dsl_ServiceType to dsl_documentnumber and dsl_servicetype to test again.
Regards,
Clofly