We have established hosting of Dynamics NAV RTC over WAN.
The problem is that the customer need an add-on where the reports is not converted to SSRS reports.
What possibilities is there to connect to the classic report throug the RTC client over WAN. It is not the same domain.
Really, what it comes down to, is if you are in the RTC, and you do NOT have any RDLC defined (meaning you deleted the RDLC layout information by designing the report and clicking Tools>Delete Layout which removes the RDLC), you end up with basically the RTC calling the Class Enginer. By this I mean you have to have the Classic Client loaded, the RTC then calls that engine and the Classic actually does the work as if the RTC isn't even being used, gets the report data, renders it, and then automatically closes. So, basically your question is the same as asking how to make the Classic Client run over a WAN, and the answer is you need a VPN connection or open up your SQL Server to everyone so that you can hit it, which i am sure you do NOT want to do. Here is a blog written on what i am speaking about on using Classic Reports with RTC.
My suggestion would be to have the regular Classic Client loaded and use a VPN, or upgrade the reports to the RDLC (RTC) version and just use those so you can use the RTC over WAN.
This was a really good answer. Thanks.
To add to what Nick was saying above, I would suggest his second option, converting to RDLC. The classic report will run ridiculously slow over the WAN. Setting up VPN might work, but users will be highly annoyed with an inefficient report.
One part of it is that since Classic is running in a Client Server model, you are essentially pulling large Recordsets over the wire. In RDLC, you are only serving up the data that is used by the report making it far more efficient.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13