Custom API LBOs CurrentCulture Issue

Extensibility
,
1

Hi Team,

We are creating a custom API in Critical Manufacturing Version 9. From the Custom API we are getting material name as input and loading material → Production Order and returning Production order in response.

To load the material and its production order, when we use the MaterialOrchestration class

cmf.navigo.businessorchestration.materialmanagement.materialmanagementorchestration.getmaterialbasicinformation(input)

Problem:

When we call this api from Postman tool it is working fine. But when we generate LBOs and reference the dll to another .Net project, then call the custom API it is not working.

We are getting error “Unexpected Problem occured” issue. When we tried to attach to host service and debug we can see the CurrentCulture is null in the message header. We are not sure if this is the actual issue.

2

Hi Simon,

Confirm if your input and output classes extend the MES BaseInput** and BaseOutput* ***classes.

If this is ok, then please check if your service, orchestration, input and output classes have the name conventions as specified at https://developer.criticalmanufacturing.com/business/createservices/, namely:

  • The Input and Output classes extend MES BaseInput** and BaseOutput* ***respectively;
  • The custom Input and Output classes have the name of the service;
  • The Input and Output classes have the DataContract and DataMember attributes.

Also, ensure that your LBOs are updated (see https://developer.criticalmanufacturing.com/business/lightbusinessobjects/).

Regards,

João Moreira