Hi all,
does anybody has experience about connecting Jet to a NAV2013R2 multi-tenancy environment?
I have no chance to connect because the SOAP link in such an environment is different from a standard installation.
I already tried many thing but nothing worked. Now I'm out of ideas. Already opened a ticket, so also the jet support is working on it.
But I thought maybe someone else had the same issue.
I can't be the only one who use the multi-tenant function…
Thx
Alex
Date
Votes
3 comments
-
Jet Reports Historic Posts Hi,
I am running into this same issue now. :cry:
I've tried various configurations of the connection info, but keep getting a 401 - unauthorized error.
IT suggested connecting using NAV 2013 -SQL type connection, but then I don't have the database info since the multi-tenant setup abstracts away from that and I don't have access to NAV 2013 Dev Environment.
Has anyone else gotten a solution for this yet? -
Jet Reports Historic Posts You need to give your tenant an alterntate ID as FQDN like myserver.mydomain.local
Then insert this FQDN in your internal DNS Server. Use the alternate ID as servername in Jet, all other settings are standard.
Clear your clients dns cache, else Jet doesn'T find the server.
In my environment I had to use the type "Dynamics NAV 2013 and older" not the one called "..and higher" in the database setup.
Good luck! -
Jet Reports Historic Posts Found this thread via a Google search. Were the access issues resolved eventually alex2605?
Please sign in to leave a comment.