or the Dynamics 365 CE integration a model.json is exported which is a one-to-one description of the underlying CSV-files. These CSV-files don’t have header information so without the model.json it is not possible to import in Azure.

For Dynamics 365 for Marketing integration also a model.json is exported which contains the metadata of the columns of the underlying CSV-files. The CSV-files that are used however do have header information.

For the processing of these two groups of data, an import is created by the data platform which first reads the model.json and based on the header information interprets the CSV files.

The starting point for this functionality is that the sort order used in the JSON is determinative for the sort order of the columns in the csv files.

Now we see that the model.json has not changed for the Marketing environment (the sort order is still the same) but the sort order of the columns in the csv files do have changed. This causes the import does not work anymore.

Instead of azure synapsis option we would like a new feature to be added as an alternative tool which can be used for importing