Custom BOD : Detect Failed

Hi,

I have created custom BOD and published it. Then custom agreement also created accordingly. 

Event Analytic Rule also configured properly. 

When trigger the BOD from M3 program I can see the message in enterprise collaborator administrator (see below) but state is "Detect failed"

 

When I checked the log it says "Null pointer exception". I have simple MEC map with some hard coded values. 

What could be the reason for this?

Appreciate your thought on this. 

 

Thanks

  • Hi there,

    Can you show us a printscreen of your "detection" tab in your agreement please as well as the .rcv file you can retrieve by clicking on the "show" link ? I guess you have reloaded the cache.
  • In reply to Maxime R.:

    a4db806b-b9fc-4cde-beef-d8cdad6ead21.xml
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <EventData>
        <TenantId>ROCKYBRANDS_DEM</TenantId>
        <Publisher>M3BODProcessor</Publisher>
        <DocumentName>SyncItemMaster</DocumentName>
        <Operation>UPDATE</Operation>
        <TrackingId>8e767101-d5d7-47b3-96f5-c6734c11a150</TrackingId>
        <EventId>b488506b-dbad-4c17-9c05-1969de9b5293</EventId>
        <SentTimestamp>2019-08-07T13:01:24.024Z</SentTimestamp>
        <Sequence>23644543027</Sequence>
        <Document>
            <ElementData>
                <Name>CONO</Name>
                <Value>771</Value>
            </ElementData>
            <ElementData>
                <Name>DIVI</Name>
                <Value></Value>
            </ElementData>
            <ElementData>
                <Name>ITNO</Name>
                <Value>TST10</Value>
            </ElementData>
            <ElementData>
                <Name>application</Name>
                <Value>M3BE_16.0_PRD</Value>
            </ElementData>
            <ElementData>
                <Name>currentProgram</Name>
                <Value>MITMASPI</Value>
            </ElementData>
            <ElementData>
                <Name>environment</Name>
                <Value>M3BE_16.0_PRD</Value>
            </ElementData>
            <ElementData>
                <Name>owner</Name>
                <Value>ANUMAN59</Value>
            </ElementData>
            <ElementData>
                <Name>startProgram</Name>
                <Value>MMS001</Value>
            </ElementData>
            <ElementData>
                <Name>version</Name>
                <Value>16.0</Value>
            </ElementData>
            <ElementData>
                <Name>BODNoun</Name>
                <Value>ItemMaster</Value>
            </ElementData>
            <ElementData>
                <Name>BODVerb</Name>
                <Value>Sync</Value>
            </ElementData>
            <ElementData>
                <Name>findDIVI</Name>
                <Value>ALL</Value>
            </ElementData>
            <ElementData>
                <Name>dataEventId</Name>
                <Value>ItemMaster_771TST10</Value>
            </ElementData>
            <ElementData>
                <Name>correlatedEventName</Name>
                <Value>M3BEBOD</Value>
            </ElementData>
            <ElementData>
                <Name>correlatedEventOperation</Name>
                <Value>UPDATE</Value>
            </ElementData>
            <ElementData>
                <Name>delayTime</Name>
                <Value>60s</Value>
            </ElementData>
            <ElementData>
                <Name>keyValue</Name>
                <Value>MMCONO,771,MMITNO,TST10++++++++++</Value>
            </ElementData>
            <ElementData>
                <Name>originKeyValue</Name>
                <Value>MMCONO,771,MMITNO,TST10++++++++++</Value>
            </ElementData>
            <ElementData>
                <Name>originPublisher</Name>
                <Value>M3</Value>
            </ElementData>
            <ElementData>
                <Name>originDocument</Name>
                <Value>MITMAS</Value>
            </ElementData>
        </Document>
    </EventData>
    

    .rcv file is attached herewith.

    Could you please tell me the step to reloaded the cache. 

    Thanks

  • In reply to RajithaWi:

    Detection tab screen capture. 

  • In reply to RajithaWi:

    You are on the cloud. Not sure about it as MEC administration has been moved to Infor OS. As a new agreement has been created, do you have a "reload" button on your admin page ?

  • In reply to Maxime R.:

    Yes I'm on multi-tenant cloud. So I couldn't find "Reload" button in there.
  • In reply to RajithaWi:

    You can both reload the agreements and the custom detections if you have any if you enter the "Server" --> "Custom Detection" or "Custom mappings". 

     

    Have you tried this options? 

     

  • In reply to masars:

    Thanks for the reply.
    Yeah tried both, didn't work.
  • In reply to RajithaWi:

    Ok,

    Based on your ".rcv" file it seems like you are trying to use a standard event/bod (ItemMaster_Sync_Out) Or am I wrong? Have you verified that you have activated the agreement in the "Server" --> "Agreement status" page? If it is a Custom it will be shown below the "Partner: Custom" heading. When you activate a custom bod with the same name of a standard agreement the standard agreement will be deactivated.
  • In reply to masars:

    Yes you are right. I did both ways.

    1. Create custom BOD by copying the standard ItemMaster BOD.

    • As you said, it was appeared under Partner:Custom section and once activate it standard BOD got de-activated. 

    2. Create custom BOD from the stretch. It gives same issue. 

    • Ex:- syncItemMDM

     

    This detect failed issue got appeared from this week onward. Up to last week all the custom BOD's we have created are working perfectly. 

    Even if we do the changes on last week created custom BOD's still working. 

    I suspect this happen due to system update or something done by Infor since this is multi tenant M3 CE. 

    I have already logged infor xtream ticket and waiting. 

    Thank you

  • In reply to RajithaWi:

    Aha okay, then I understand.

    I Agree with you it sounds suspicious since it worked before... please update us on the progress. :)
  • In reply to masars:

    Move to ION Connect Forum