Thanks for the feedback, Mike. I assume you are recommending creating a Web Service (both options) with the NVO. Are there other approaches to doing this? We are still considering these alternatives, but at this point we were hoping to not utilize a separate server for the process.



We figured we begin by converting the current process to an NVO first, but before beginning understand the implications tied to the course of action.

create a small application that takes a command line (or reads data from a file, or from the database) and then creates your NVO and processes the data. it doesn't have to be a web service, you could run it on the same machine that your user is on. there may be security considerations, and you want to be sure you are starting the application as a completely separate process, but in the end you are just running another application.



running on the same box as the user is not really an option for powerserver web clients, for that you would want to run on a server. that can be done as webservice or some sort of process queue. you basically are running a batch job.

I thought that SharedObjects was not supported anymore. I am glad this changed, because there are some bugs that make my life very difficult....

Thanks for the update, Chris. I look forward to the release of PowerServer 2021.

Hello, Yiannis.



Do you have any bug fixes / improvements that may be of interest. I'd like to be aware of any challenges you've come across while implementing functionality with the shared objects.



The one thing I found interested is I cannot pass a datastore as an argument into the shared NVO. I though the DS was an NVO but the error messages states it is a visual object.