Improved Integration with Custom Attributes in Outbound Messages

Thanks, there we have it!

​@dsj what outbound messages are supported? I mean does this apply also on e-invoice xml export? 

Hi ​@kvbe 

There’s no proper indication on which outbound messages are supported with this. According to the documentation, to enable custom attribute support, structure-based projection action structures must be annotated with the configentity property. 

I did a simple search on 25R2 code base and found below contains the syntax. E-invoice is not there yet as per my guess, but worth checking with IFS.
 

Cheers!

Damith

​@dsj what outbound messages are supported? I mean does this apply also on e-invoice xml export? 

 

 

Hi ​@kvbe 

 

There’s no proper indication on which outbound messages are supported with this. According to the documentation, to enable custom attribute support, structure-based projection action structures must be annotated with the configentity property. 

 

I did a simple search on 25R2 code base and found below contains the syntax. E-invoice is not there yet as per my guess, but worth checking with IFS.
 

 

Cheers!

Damith

Hi ​@dsj,

Do you know by chance if the annotation of the the configentity property must be completed from the backend and if it applies to inbound messages as well?

I was working on a functional test of adding custom attributes on an inbound file (released in 24R1), but the new attributes do not appear in the API doc.

According to my customer who has tested it, it doesn't work perfectly. In the example of Dispatch Advice, only the header can export custom fields. Any CF added to the Dispatch lines, will not be shown in outbound messages.

Anyone, any comment on above?

Hi ​@Frbese ,

You mention your customer had success with CF on the header for DESADV - can you tell me, where they placed the CF? Which entity? And how they sent it?

And in regards to dispatch lines and handling units - if you place them in HandlingUnitHistory, they show up on Outbound Message Viewer. However, in the utility package they collect custom attributes from ShipmentHandlUnitWithHistory and DispatchAdviceLine which doesn’t correspond to any LU or TAB - so, I assume that’s an error. The view shpmnt_access_hu_with_history is based on handling_unit_history_tab, so I would assume it should be changed to HandlingUnitHistory.

My issue is that I can see the CFs on the Outbound Message Viewer, but none of the CFs are places in the DESADV JSON file when using INET_TRANS, and I have no idea why that is.