Hi @premkrishnan612 

I've no idea what you are referring to about the limitation of the number of indices that you can use in a CSV mapping. The only limitation is the maximum dimension an AIMMS identifier, which is 32, and DEX is fine handling these.

I've attached a very simple example of a 5-dimensional identifier being mapped to a CSV file, both with all dimensions in the row header, and with the last dimension mapped to the column headers using the name-binds-to attribute. This would work the same with identifiers with any dimension up to 32.

With DEX you can't have multiple column headers. These pivot-like tables are the realm of the axll library. For exchanging data with other applications, such formats suck imo.

BTW. if you have massive data I would suggest to use Parquet files instead of CSV files. This will lead to increased performance as well as decreased file size, while many applications are able to work with Parquet, and delta-lake based data warehouses like databricks are built on top of the Parquet format.

Thank you for the response !

Just one more follow up question. I tried to test out parquet mapping but AIMMS keeps crashing and closing. I had originally created the parquet files in python with and without encoding but in both cases it starts to run the code and then AIMMS closes. Is there any reason why this is happening ?

If you have an example of the crashing parquet file, then please send a reproducing example to support@aimms.com and we can take a look at it. Might be you're using some Parquet feature we don't support, but we would need the parquet to be able investigate.