Currently we use a sql view to surface cross company data to people who do not have Epicor access on their account to all of the other companies (ie, part availability in all companies in the system, rather than only the companies they have access to). We plan to move to SAAS in the next couple of years, where we will lose access to the SQL views, so I am trying to come up with alternatives.
One thought was to do a cross company normal BAQ, but have its data available on a web page that uses a rest call using an ID that had access to all companies to surface the data. Kind of a work around, but I was wondering if anyone had any other thoughts on the best way to do this process? And to make the process future proof.
I also think there is a possibility of a RO replica in SAAS for reporting, but I did not know if you get access to a sql view to be able to read the data.
You can still have your own sql server when Epicor is in the cloud. Then query the Epicor data via a linked server connection from the read only db. That way you could preserve your existing system, if you wanted to. Your idea would work too but how would you authenticate the traffic to the website.
The website uses AD authentication, so we should be good there.
So on the RO database access, do they give you access to create your own SQL views? I had not heard for sure if that was allowed, so I am trying to make sure we are ready for the cutover when it happens, rather than having to scramble at the last minute.
No, its READ ONLY lol.
You can spin up your own sql instance and create views there. The views in your own database can pull data from the read only database via linked server.