Skip to main content
Solved

Inbound integration - table key returns not working

  • May 6, 2022
  • 4 replies
  • 177 views

Forum|alt.badge.img+13

Hi Experts,

This is related to the same question below raised by a community member. 

Inbound integration -Table key returns is not working | IFS Community

There is a requirement to send the keys to the outer system with the inbound response.

→ Inbound request

→ Create response with the key

I have tried to achieve this using the ‘Table key returns’ option in xml map.(As shown in the below screenshot )

 

 

Postman request

Postman response

But the response doesn’t have the Task ID information.

Am I missing something here?

 

Thanks and regards,

Hasara

Best answer by Saranga Amaraweera

Hi Saranga,

Thank you for the response.

Above suggestion was tested but still the TASK ID is not in the response.

Postman Response

{
"@odata.context": "http://hagilk0//DEMOFSMServer6_4/OData/$metadata#fsm.ComplexType",
"value": "<perform_inbound_integration_result><batch_id></batch_id><run_id>156</run_id><run_status>COMPLETED</run_status><run_message>1 records processed.</run_message><run_handler>Standard XML Inbound</run_handler><keys><keys /></keys><CustomResponse></CustomResponse></perform_inbound_integration_result>"
}

 

Thanks and regards,

Hasara

Hi @Hasara Dinu ,

According to the baseline code, you should be providing the table name instead of the key column name (key field) so that it will return the relevant keys on your result for <keys> element.  This should be working with “*” (all) symbol  as well in which returns all the relevant key fields for all the tables.

4 replies

Saranga Amaraweera
Superhero
Forum|alt.badge.img+22

Hi @Hasara Dinu ,

Have you tried adding the accept path field as “//response “ on the inbound settings?


Forum|alt.badge.img+13
  • Author
  • Hero (Employee)
  • May 6, 2022

Hi Saranga,

Thank you for the response.

Above suggestion was tested but still the TASK ID is not in the response.

Postman Response

{
"@odata.context": "http://hagilk0//DEMOFSMServer6_4/OData/$metadata#fsm.ComplexType",
"value": "<perform_inbound_integration_result><batch_id></batch_id><run_id>156</run_id><run_status>COMPLETED</run_status><run_message>1 records processed.</run_message><run_handler>Standard XML Inbound</run_handler><keys><keys /></keys><CustomResponse></CustomResponse></perform_inbound_integration_result>"
}

 

Thanks and regards,

Hasara


Saranga Amaraweera
Superhero
Forum|alt.badge.img+22

Hi @Hasara Dinu ,

Is the task_id being recorded into integration run log ? Can you share the run log result


Saranga Amaraweera
Superhero
Forum|alt.badge.img+22

Hi Saranga,

Thank you for the response.

Above suggestion was tested but still the TASK ID is not in the response.

Postman Response

{
"@odata.context": "http://hagilk0//DEMOFSMServer6_4/OData/$metadata#fsm.ComplexType",
"value": "<perform_inbound_integration_result><batch_id></batch_id><run_id>156</run_id><run_status>COMPLETED</run_status><run_message>1 records processed.</run_message><run_handler>Standard XML Inbound</run_handler><keys><keys /></keys><CustomResponse></CustomResponse></perform_inbound_integration_result>"
}

 

Thanks and regards,

Hasara

Hi @Hasara Dinu ,

According to the baseline code, you should be providing the table name instead of the key column name (key field) so that it will return the relevant keys on your result for <keys> element.  This should be working with “*” (all) symbol  as well in which returns all the relevant key fields for all the tables.