...

RequestsTable:
LOAD 0 as ID AutoGenerate 0;

// START Requests API Call and add the returned results to previous ones
LIB CONNECT TO 'WPP Blackbaud Grantmaking (ad_ahmadijooban)';
RequestsTable:

SQL SELECT 

Separating Load from Visualization

In order to do that, one giant load was created inside the loop and the entire API calls moved into LAD app. The result was saved in one QVD.

The version of load that broke the table into smaller ones with links and joins stayed inside the visualization app.

This way, concatenating all tables into one big table in order to save it in one QVD was possible without any issues, mostly because there were no linking happening yet.

Join vs Keep

Replacing joins with keep didn't work. It only loaded data from the first set of classification tables joint to codings table. And it also didn't line up the data properly:

Image Added