Hi JsonMcTyre, Welcome to DUG. A shame you customer is not already on NAV 2016, because then a PowerBi interface would be out of the box. Well any newer version would have been easier to integrate to. If you are not familiar with NAV's data model, then SQL is maybe not the easiest option. Especially not if the customer makes heavy use of dimensions in NAV, and need them in the BI system too. Or if the BI views need to consolidate across different companies (NAV have a different table per company). It's going to require a lot of joins in your queries. And before you begin to ask to why things look a bit different in NAV, when you look at it from SQL, then remember that in NAV 5, SQL Server is only only one of the database options. The other is NAV's Native database. If you're using SQL, then you can also use the job manager to schedule the execution of your sql scripts. The other option would be to team up with another freelancer, who could create a set of XMLPorts to export the data you need. This could then be scheduled inside NAV using it's NAS (application server). NAV's own (classic) report designer, can also easily be used to create data exports (CSV).
↧