Error running Real-time DataFeed for DataDocument

Technical Questions
1

Screenshot from 2024-03-18 17-05-41
Screenshot from 2024-03-18 17-05-411918Ă—493 172 KB

This error was generated by this code

<fields fieldSeqId="39" fieldPath="fromParty:contactMechs:contactMech:infoString" fieldNameAlias="fromPartyEmail"/> data documents

and it only throwing exception second time loading (i mean after ./gradlew cleanAll ) after cleanAll 1st ./gradlew load it works perfectly

relationship flow below

 INVOICE -->1 
 
 <entity entity-name="Invoice" package="mantle.account.invoice" short-alias="invoices" cache="never" optimistic-lock="true">
        <field name="invoiceId" type="id" is-pk="true"/>
        <field name="invoiceTypeEnumId" type="id"/>
        (other fileds)
        <field name="fromPartyId" type="id" enable-audit-log="update"/> 
          <relationship type="one" title="From" related="mantle.party.Party" short-alias="fromParty">
            <key-map field-name="fromPartyId"/></relationship>
   </entity>        

PARTY -->2

 <entity entity-name="Party" package="mantle.party" short-alias="parties">
        <field name="partyId" type="id" is-pk="true"/>
         (other fileds)
         <relationship type="many" related="mantle.party.contact.PartyContactMech" short-alias="contactMechs">
              <key-map field-name="partyId"/></relationship>            
</entity>   

PARTYCONTACTMECH -->3

 <entity entity-name="PartyContactMech" package="mantle.party.contact" use="nontransactional" cache="never">
        <field name="partyId" type="id" is-pk="true"/>
        <field name="contactMechId" type="id" is-pk="true"/>
        <field name="contactMechPurposeId" type="id" is-pk="true"/>
         (other fileds)
          <relationship type="one" related="mantle.party.contact.ContactMech" short-alias="contactMech" mutable="true"/>
</entity>   

CONTACTMECH -->4

  <entity entity-name="ContactMech" package="mantle.party.contact" short-alias="contactMechs" use="nontransactional" cache="never">
        <field name="contactMechId" type="id" is-pk="true"/>
        <field name="contactMechTypeEnumId" type="id"/>
        <field name="dataSourceId" type="id"/>
        <field name="infoString" type="text-medium"/>
        <field name="gatewayCimId" type="text-short" enable-audit-log="update"/>
        <field name="trustLevelEnumId" type="id"/>
        <field name="validateMessage" type="text-medium"/>
        <field name="paymentFraudEvidenceId" type="id"><description>Refer to evidence here if trustLevelEnumId is gray listed or black listed</description></field>
        <field name="replacesContactMechId" type="id"><description>For update by copy-on-write this is the ID of the ContactMech it replaces</description></field>

here we get infoString that’s fieldNameAlias=“fromPartyEmail”

1 Like
2

Seems I got similar before.
I remember the temp solution is extending entity to have backward relationship as error message suggested.

1 Like
3

Thank you strand, I used extend entity for creating new relationship directly it works perfectly thanks.

1 Like