CallContext for Custom Service using JSON Endpoint in AX 7

(0) Share

Report

Posted on by mjjoachim

Hello,

Is it possible to specify a "CallContext" when calling a custom service at the JSON endpoint in the new Dynamics AX? I'd like to be able to specify the company.

I've tried specifying a "Company" request header and a "CallContext" request header but get a 500 response in both cases.

Thanks in advance.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Suggested answer

Marcel Ferreira on at

Like (0)

Report

Hi mjjoachim,

If you're working with oData, to select an specific company you have to use something like this:
http://[baseURI]/data/FleetCustomers?$filter=dataAreaId eq ‘usrt’&cross-company=true

I believe for a custom service is the same, but I'm not sure.

https://ax.help.dynamics.com/en/wiki/dynamics-ax-7-services-technical-concepts-guide/

Can you test and let us know?

Regards,
Marcel

Was this reply helpful? Yes No
mjjoachim 3 on at

Like (0)

Report

Thank you Marcel, I had not tried that.

Unfortunately, it does not seem to work. I am using the following service address: usnconeboxax1aos.cloud.onebox.dynamics.com/.../Services[ServiceGroup]/[Service]/insert?$filter=dataAreaId eq 'USP2'&cross-company=true. If the user's default company is USP2 the call works. If the user's default company is not USP2, the call fails because of a referential integrity violation. So I think the call is OK, but using the OData syntax does not seem to be changing the company.

Thank you though.

Was this reply helpful? Yes No
Mea_ 60,284 on at

Like (0)

Report

Hi mjjoachim,

As far as I know there is no "company" context and it will return you data from user's default company. The only work around I have heared is to use "cross-company=true" query option and than filter by company in your application.

Was this reply helpful? Yes No
mjjoachim 3 on at

Like (0)

Report

Hi ievgen,

It may be that there is no way to switch the company via the JSON endpoint for custom services. However, it is possible to pass a CallContext object for the same custom service via the SOAP endpoint. So it seems like it would be a pretty big oversight to omit it for the JSON endpoint.

Just to be clear, I'm calling a Dynamics AX custom service, not the OData service.

If I can't figure this out, I will resort to using the SOAP endpoint or manually switching the company within the service. But I don't think that is a good idea if there is a more standard way to do it.

Thanks

Was this reply helpful? Yes No
Verified answer

Mea_ 60,284 on at

Like (0)

Report

Hi mjjoachim,

Yep I probably missed part about JSON and thought that you are talking about OData.

However, I have not heard about call context with JSON as well, here is a similar question on yammer

www.yammer.com/dynamicsaxfeedbackprograms

I don't know if you have access to it or not but solution that is proposed there is to pass company inside of JSON request and do changecompany in your service manually.

Was this reply helpful? Yes No

Community site session details

CallContext for Custom Service using JSON Endpoint in AX 7

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates

Community site session details

CallContext for Custom Service using JSON Endpoint in AX 7

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates