DocStar (23.1.132) JSON Web Service DataLink Creation

ECM
, ,
1

Hello,

I have exhausted much of my resources in attempts to create a new ‘custom’ JSON web service datalink in DocStar without success. At this point I am trying to get any Epicor API call to work, even one which requires no params and just returns data, Eg. Erp.BO.CustomerSvc. I am new to all of this so I don’t quite understand how these work. From my research it appears as though the DataLink Connection configures the…connection…and importantly holds authentication information and the DataLink lower on the page is the call itself. I don’t know what is required/optional in these calls to get them to work properly and am unable to find documentation which explicitly states what’s needed. Below I have included what I currently have configured for my Customers example.

I have reached out to DocStar support and unfortunately, they only had a single, very old, document which didn’t provide any help. Additionally, I have looked through EpicWeb and EpicLearning with no great information here either. I have also gone through some of the resources here on EpiUsers which has been quite beneficial but many of the discussions have been overly complicated for what I am trying to achieve or are a bit dated.

Again, just looking to get anything to work so that I can dissect it and really understand the how so that I can move on to creating more complex calls.

Does anyone here have any good documentation on JSON Web Service DataLinks that they can provide or maybe a simple example (which would be amazing)?

DataLink Connection:

image
image859×562 30.5 KB

DataLink Connection Call Definitions:

image
image833×743 18.6 KB

DataLinks:

image
image1306×765 52.4 KB

DataLinks Call Definitions:

image
image1190×969 18.4 KB

Error when clicking Test Live (The only error that displays after making any changes): “Misused header name. Make sure request headers are used with HttpRequestMessage, response headers with HttpResponseMessage, and content headers with HttpContent objects.”

As usual any help here is greatly appreciated. Thank you all in advance!

Brandon Kveene

2

A few things to note.

You need the URL before your token request in the header Call Definition. Also, depending on what version of ECM you’re on, you don’t need the encoded AuthParameter in any of the calls. Worth trying without, once you get things working.

As for your individual Call Definition below, v2 calls require API authentication while v1 types do not. Using v1 and Basic as the AuthScheme should help.

Finally, the API call you’re referencing in the URL portion doesn’t seem to have the correct parameters to use. The best way to get the correct URL is to develop the call in Epicor REST and then apply it in ECM.

2 Likes
3

Thank you for the feedback Victor! I was advised to use the V2 API but can still apply the suggested changes. I did work in Epicor Swagger prior to moving into DocStar but this had gone through too many iterations so I may have muddled things up a bit. Thank you for identifying this.

2 Likes
4

You might want to try takeing a step back and using postman to see how the request is generated. once you have that working you can export it out and should be able to paste it in.

1 Like
5

Brandon,
Were you ever able to get this to work? I’m trying to do something very similar, creating a DataLink lookup against a Kinetic BAQ using the BAQ API. I keep getting stuck at an Authentication error. If you were able to make this work, I would love to know what you did. Thanks.

1 Like
6

You should be able to create an API Key in Epicor and use that for accessing REST API from ECM. This would only be required for v2 API calls. The API Key value would likely only be needed in the Datalink Connections call and not each individual call, but I may be mistaken on that…

1 Like