DLL Functions for REST APIs

Stephan Woessmann

Has anyone been able to use DLL Functions for REST APIs? For example for the Entity Types' Updatable, Insertable, and Deletable Actions, the Actions, or the Functions.

The 'OData REST API Development' (https://docs.infor.com/ln/latest/en-us/lnesolh/default.html?helpcontent=lnodatrestapiug/cover.html ) documentation does not provide any details, and I have not found any further help on this.

The error messages when trying to save an Action have not lead me to a working Action yet.

Just for an example, I have the following tx DLL function:

function extern long txcom.dll0000.get.company.country(
domain tcncmp i.company,
boolean i.force.read,
boolean i.dal.set.error.message,
ref domain tcccty o.country)

I set the ReturnType of the Action to Edm.String, and the Parameters are (1) company (EdmInt16), (2) force (Edm.Boolean), and (3) error (Edm.Boolean). When trying to save, the following error is given.

ERROR:
Function 'txcom.dll0000.get.company.country' in DLL 'otxcomdll0000' has 4 parameter(s), but a total of 2 parameter(s) is/are expected for Action 'ActionFunctionTest': 1 input parameter(s) + 1 output parameter for the return value

Did I not maintain 4 parameters: 3 input + 1 output?

Stephan Woessmann

While I was figuring out how to do it, Infor created KB3620994 (https://customerportal.infor.com/csmcore?id=kb_article_view&sysparm_article=KB3620994) with an attached document that explains how to do it, which can be used as a guideline while the team works on the documentation.

My earlier mistake was assuming that it would be similar to how BDEs allow calling functions and passing arguments, but that is not the case. Unless it is a single input, the input/output function arguments are JSON (long) objects. The return value of the function must always be a long (0/DALHOOKERROR).