Closed sabin-sharma closed 4 months ago
I really can't reproduce your issue... I created this one, and there are no issues.
<fetch>
<entity name='account'>
<attribute name='name' />
<link-entity name='contact' from='parentcustomerid' to='accountid' alias='contact'>
<attribute name='fullname' />
<filter>
<condition attribute='lastname' operator='not-null' />
<condition attribute='firstname' operator='not-null' />
</filter>
</link-entity>
</entity>
</fetch>
Can you reproduce it now? Any more info for me?
No response. Closing this issue, please reopen if you have any feedback!
Scenario: Add the link entity and use the filter with two condition in the link entity.
Issue: If the condition's attribute exists in both the main entity and the link entity then it works fine. If the attribute is only in the link entity and does not exists in the main entity it throws error.
Error: 'Account' entity doesn't contain attribute with Name = 'new_exclude' and NameMapping = 'Logical'.
Example.
Say 'new_exclude' attribute exists in Contact table but not in Account and we would like to filter record based on the value of this attribute.
FetchXML that generates error.
In order to make above FetchXML work we have to add another filter as shown below.