cancel
Showing results for 
Search instead for 
Did you mean: 

Interface determination based on a custom field on payload

0 Kudos

All,

We added a custom field (a flag) to a standard enterprise service TransportationOrderRequest_Out hoping to use it for routing in PI, i.e. determine a unique interface / mapping if this flag has a certain value. However it turns out there is a constraint that only standard fields can be used for routing / interface determination. Is this true and if so could someone advise if there is a work around?

Best Regards,

KC

Accepted Solutions (0)

Answers (1)

Answers (1)

Harish
Active Contributor
0 Kudos

Hi KC,

you can use the custom field for routing, but how you added the custom field in standard structure? You need to use the enhanced data type to add the custom field in PI and then use in ECC (if it is related to proxy).

refer the below link for standard content enhancement

regards,

Harish

0 Kudos

Hi Harish,

Please see the screenshot showing a custom field (ITIN) added to a standard interface. I'm no PI expert, could you please confirm if these type of fields can be used for determining interface?

Best Regards,

KC

Harish
Active Contributor
0 Kudos

Hi KC,

Yes this field can be used to determine interface.

regards,

Harish

0 Kudos

Thanks Harish, could you please give some technical details as to how it can be implemented. This will help our PI team. The information I received from them is 'routing logic cannot be defined for a runtime parameter', 'proxy trigger should be from the local namespace rather than standard namespace' (they are suggesting that all standard objects should be copied into customer namespace)

Best Regards,

KC

manoj_khavatkopp
Active Contributor
0 Kudos

Krishan,

So if i understand properly you need to keep condition on the enhanced field for the standard structure.

Enhanced filed with standard data type :

Condition:

Proxy trigger should be from the local namespace rather than standard namespace' (they are suggesting that all standard objects should be copied into customer namespace)

Usually when we want to enhance the standard content then we create a dependency on the standard content SWCV , and then make the required Enhancement in our custom namespace.Making Enhancement in standard namespace is not a good idea, this affects all the dependent interfaces.

Br,

Manoj

0 Kudos

Manoj,

Is your XML namespace standard or custom? Our interface is in standard namespace and we do not want to move the standard objects to a custom namespace. We do not want to trigger the proxy in custom namespace.

Best Regards,

KC

manoj_khavatkopp
Active Contributor
0 Kudos

This is just a custom test namespace not a standard one.

former_member182412
Active Contributor
0 Kudos

Hi Krishna,

Check the similar discussion.

Enhanced Fields Not visible in Condition Editor... | SCN

Regards,

Praveen.

0 Kudos

Praveen,

The namespace on your screenshot looks like a custom one, could you please confirm? Our interface is in the standard namespace and we don't want to change it. In this case if we choose custom software component in receiver determination will it work if the interface triggered is in the standard namespace?

Best Regards,

KC