In order to use multiple datasets in System Five on Cloud. The shortcuts on each user's desktop will point to a separate dataset, the same way we create one for Live and Training in an on-premises environment.

The difference is that in an on-premises environment, we would link to the dataset and System Five will update the registry.
In our cloud environment, we don't write to the Windows registry. Instead, we must use an INI file that contains similar information to what we would write to the registry.

You will have to actually log into each user's account to do these steps.

First, we need to create a new INI file for each dataset and place a copy of it in each user's profile.
eg. D:\Users\swind\System5\ To do this I made a copy of the Data.ini and edited the copy for each dataset.
In this example, I named them Data_A.iniData_B.ini and Data_C.ini to keep it simple.
This INI File also has to contain the company name and the path to the data folders.
This is the example of Data_A.ini with the lines we want changing in bold.

CompanyName=Company A

I modified this in the copies of the INI Files I brought back to my desktop so that i would only need to edit them once.

Now we need to manually create icons for each data set on each person's desktop, and point the shortcuts to where each user's dataset.ini file are located. As you can see in the picture below, the Target and Start in would look something like this:

Target = W:\System5\bin\systemfive_SaaS.exe /inifile=D:\Users\swind\System5\Data_A.ini

Start in = W:\System5\bin

As you can see the Target path is the same for all shortcuts, but the /inifile= argument must point to the path of the user's cloud folder, and the ini file for Data_A. Data_B or Data_C.

note: You must be logged into the user's cloud session to see the user's folder, and be able to create the shortcuts and INI files.



Getting access violations trying to link multiple datasets from System Five on Cloud with the Remote POS device Manager on the workstation.
This would happen if the user was using SystemFive.exe in their shortcuts instead of SystemFive_SaaS.exe.

In some cases, SystemFive.exe was used as a workaround to give access to multiple datasets, just like we do on a normal network or workstation environment.

The problem with that is that SystemFive.exe is not RMR aware. The shortcuts need to point to the SAAS Version of the System Five executable for RMR to function.

See this wiki for additional trouble shooting information