From version 8.00.0083 onwards the inmydata client installation supports the importing of QAD browses from the QAD database to provide export definitions for inmydata.
These QAD browses are used to create Subjects that can then be used by the inmydata Data Publisher app to extract data from QAD via a Progress AppServer (Classic or PASOE) and push the extracted data into the inmydata platform.
The created Subjects can also be used in the inmydata Excel Add-In to extract data from QAD via a Progress AppServer (Classic or PASOE) directly into Excel.
To import QAD browses into inmydata, follow these steps;
- Install the latest version of the inmydata client available here: https://inmydata.com/updateV8 on a Windows PC or server than has access to the AppServer you wish to extract data from.
- Copy the inmydata procedure library available from this KB to the a directory that is available to AppServer you are going to use. If you are using a V11 AppServer then use the inmydata111.pl procedure library. If you are using a V12 AppServer then use the inmydata12.pl procedure library.
- Edit the PROPATH on your AppServer to include the procedure library you copied in step 2 above.
- Edit the "startup" procedure to be inmydataStartup.p*
- Edit the "connect" procedure to be inmydataConnect.p*
- Edit the "activate" procedure to be inmydataActivate.p*
- Create a directory that is available to the AppServer. This will store any .p files generated by the import of the QAD browses. These are pieces of Progress code uses by the QAD browses to perform some of the more complicated calculations.
- If you are using a Classic AppServer then add the environment variable inmydataBLDir and assign the value of the directory created in step 7 above. Ensure that the directory ends with / on Windows or \ on UNIX based systems. If you are using a PASOE AppServer then follow the instructions in this Progress KB to set the enviroment variable. The name and value of the environment variable should be inmydataBLDir and the value should be the fully qualified directory name ending with / on Windows or \ on UNIX.
- Restart the AppServer.
- Start the inmydata Excel Add-in or the inmydata Data Publisher. Select the "Configure data sources" option from the ribbon/menu to open the "Other data sources" window.
- Create a new system and set the connection details to be the AppServer you configued in the earlier steps. Ensure that the "Prompt user for password" option on the "Advanced" tab on the "Connection Details" screen is selected. For PASOE AppServer's ensure that the "Session Model" is set to "Session Managed" to ensure that the AppServer connect procedure will be called on the same connection.
- From the ribbon in the "Other Data Sources" screen select the "Import/Export" button.
- Select the "Import Browses from QAD as Subjects" option and click "Next"
- Select a folder on the local PC or Server to write the .p's to. These are Progress code used by the QAD browses to perform some of the more complicated calculations. Then click "Next".
- Now select the system created in step 11 above. This should already be selected. Click "Next".
- Select the browses from the list on the left that you want to import. You can filter the list to search and you can select multiple browses together. Use the ">" button to move the selected browses to the "Selected" list from the "Available" list. Once you have made all your selections click "Next".
- Once the browses have been imported any .p's used by them will be been written to the local folder you seletced in step 14 above. Copy these .p's to the machine running the AppServer to the directory you created in step 7 above. This will be the directory you assigned to the inmydataBLDir environment variable.
- Now you should be able to create tasks in the inmydata Data Publisher and queries in the inmydata Excel Add-In based on browses in QAD.
- You can repeat this process to update the any changes made in the QAD browses at any time by following the same steps.
* If you already have startup, connect or activate procedures assigned on the AppServer you wish to use then you will need to integrate the code in the inmydata versions of these procedures. The source for these is attached to this KB entry.