Developer forum

Hi Adrian,

yes, it does. The documentation about the setup is here.
There are some features for the Live integration discounts and shipping fees that can be handled differently (some features exist only for the BC/NAV) in the Live integration:
https://doc.dynamicweb.com/Default.aspx?ID=12911#21289
https://doc.dynamicweb.com/Default.aspx?ID=12911#21291
BR, Dmitrij

Hi Dmitrij,

Thank you very much for the info.

Adrian

Hi Dmitrij,
I may need some guidance here.
I am trying to first set up the Live integration.
I have defined the Authentication in Endpoint management and I now need to create an endpoint that would be used for Live Integration.
If I click the "Connects to standard Dynamicweb ERP service" I get this warning underneath the URL textinput:
"Url is not valid Dynamicweb service url. For Business Central the url must ends with: /Codeunit/DWWebService. For Finance&Operations the url must ends with: /services/dwservice".
Even if I add "/services/dwservice" at the end of my URL, I still get that same warning and I cannot save the endpoint. I may be able to override this problem by ajusting it directly in the database but I am not sure if this is the right path to do it.
My DW version is 9.17.5 (which is indeed rather old).
Alo, I cannot find any detailed documentation about the F&O integration (as I could for BC). Do you happen to have any starter points that could help me configure it faster?
For now, I only need to import products, send Orders, live prices and live cart. 

Thank you,

Adrian
 

Hi Adrian,
the information about the F&O setup is in the links from my previous reply. I am using the DW9 9.21 and have this url for the F&O cloud connection: https://dwax10b57ca4df9d70d428devaos.cloudax.dynamics.com/soap/services/dwservice
I am using the S2S authentication for the connection:

Can you try to prepend the soap/services/dwservice to your host name?
BR, Dmitrij

Hi Dmitrij,
Thank you. Adding soap/services/dwservice to the host name allowed me to save the endpoint and check the "Connects to standard Dynamicweb ERP service" .
However, testing the request did not return anything. I will probably have to check some logs and see what happened.
One other thing I noticed is that my URL looks a bit different than yours.
Mine is this format: https://<environment name>.sandbox.operations.eu.dynamics.com/
While yours looks different: https://<environment name>.cloudax.dynamics.com/
Is this difference relevant or it's just related to the cloud location?

Thank you,
Adrian

Hi Adrian,

https://<environment-name>.sandbox.operations.eu.dynamics.com/ — this is the standard Tier-2 (cloud-hosted) environment URL format. Your sandbox.operations.eu.dynamics.com URL indicates a proper Tier-2 cloud-hosted sandbox tied to an LCS project, which is what customer implementations use.
 

https://<environment-name>.cloudax.dynamics.com/ — this is the demo/dev environment provisioned via LCS, especially older ones or free trial/demo environments (e.g., the classic "customer demo" or partner demo environments), which historically used the cloudax.dynamics.com domain instead of operations.<geo>.dynamics.com. This is a Tier 1 (cloud-hosted) environment deployed via LCS's "Cloud-hosted environments" feature, not a Tier 2 sandbox.

So: it's not "just cloud location" — it reflects the environment tier/type.
BR, Dmitrij

Hi Dmitrij,
Thank you very much for the clear explanation.

Adrian