Import File Mapping Disappears When Production Data Copied Down to Another Environment

Matthew E Chitty

When we copy the data from one environment to another, the displaying of the file mapping is gone. If I look in the IMPORTFILETEMPLATE table, the file mapping still exists in the DETAILCOLUMNMAP field and the import file mapping template can be used without re-mapping anything. But, it is not displayed in the import file mapping data form in the CRM. If the file mapping needs to be changed at all, then the import file mapping must be totally re-mapped.

Why doesn't the file mapping display in the import file mapping data form at all? Trying to come up with a way to be able to move the file mapping, seamlessly, between environments. Currently, the only way that we have found to do this is '…to grab the DETAILCOLUMNMAP column first, then load the template through the front end (along with the import file used to do the file mapping), don't map anything, then in sql update the IMPORTFILETEMPLATE with the column map.' Trying to find an easier way to do this…if there is one.

Thanks,

Matt

Stacey Segal

@Matthew E Chitty
Hi Matthew

Not sure if you'd want to try this, but you could rebuild them in the BVDL, and then the file mapping would be created, and you could import/export them via configuration from one environment to another. If you'd like to give it a shot or talk more about it, you can reach out to our support team (or email me directly, and I'll connect you.)

Stacey

Matthew E Chitty

@Stacey Segal
Hello Stacey,

Currently we have about 300 imports in our CRM. I have converted several of them already so that it is being done through BVDL. We might (or might not) convert a lot, if not all, of our imports to using BVDL. It will take quite a while to convert all of them which is not feasible at this time. We are looking for a current way to backup all of our imports in the CRM.

Thank you for the advice, but at this time, it is not feasible to convert all of our imports to using BVDL, so we need something that will work for the time being,

Thanks,

Matt

David Wanless

Dear @Matthew E Chitty,

I believe this happens because the file is not present in the import folder for the non-production environment. We've got around it by copying the file into the import folder, e.g., by uploading it with a different import process. The mapping then reappears.

Ciao,

David.

Matthew E Chitty

Hello @David Wanless,

My next question would be how are you importing the files from one environment to another? Currently, our import folders are locked down so that files cannot be moved in or out of them.

Thanks,

Matt

David Wanless

Dear @Matthew E Chitty,

We just use any normal Import process to upload them (one by one).

Ciao,

David.