Skip to main content

Hi Team,

 

We are trying to call through below XML the out-bound call but it is not working as expected. Instead of using the REST API for message_name C_UPDATE_STATUS, it is using randomly some other message REST API. Can you please help on how this can be handled.

<perform_outbound_integration>
  <parameters>
    <dataconnector>Metrix.Integration.JSONOutboundConnector</dataconnector>
    <extract_entity>C_UPDATE_EQUIPMENT_MODEM</extract_entity>
    <message_name>C_UPDATE_STATUS</message_name>
    <enable_time_constrain>N</enable_time_constrain>
    <input>
      <primary_table_constraints>
        <id>@id</id>
      </primary_table_constraints>
    </input>
  </parameters>
</perform_outbound_integration> 

 

Regards,

AJAY

Hi,

 

Can you please send us the screenshot of your message routing rule to check whether it is configured properly? And also, in the routing rule, you need to set up the correct dataconnector and xml map. If it is triggering another routing rule, please check whether that routing rule has the same xml map and the dataconnector.

 

Thanks,

Hasara


Hi,

Please find below the screenshot of routing. Please advise if something is wrong.

Regards,

AJAY


Hi @ajayifs ,

Could you please let me know the MAP_ID you are using in the Message Routing rule?

 

As per the below part, 

 

It should equal to extract_entity = C_UPDATE_EQUIPMENT_MODEM  (Map ID in Message Routing rule)

message_name = C_UPDATE_STATUS (Message name in Message Routing rule)

 

  <extract_entity>C_UPDATE_EQUIPMENT_MODEM</extract_entity>
  <message_name>C_UPDATE_STATUS</message_name>

 

Thanks,

Hasara


Hi Dinu,

 

Yes map id is C_UPDATE_EQUIPMENT_MODEM. Do we need to keep map id and routing id same?

 

Regards,

AJAY


@ajayifs,

 

No. You don’t need.

Meanwhile please check whether there are any other routing rules that have the same xml map.


Reply