Bulk Administration Import error: <filename> is not a valid filename

[John Whitford]

Trying to move configuration from v8.0.3 to v9.1.2. I have tried using a header.txt file from the v.8 cluster and from the v.9 cluster with the same message. This error is from the header file. The validation passes the config file (css details in this case) with no errors.

The header file looks like this

Time : Jan 15, 2016 09:10:32 AM EST
IP Address : 10.251.93.20           <the v.9 cluster pub>
CCM : master-9.1.2.11900-12
File : pilot_css

Here's the verification output

Failure Details :

FileName Error Code Error Description

-----------------------------------------------------------------------------------------

pilot_css pilot_css is not a valid filename

******** NO ERROR FOUND ********

Result Summary :

VALIDATE for 1 FILES passed.

VALIDATE for 0 FILES failed.

End Time : 01/18/2016 15:05:23

Documentation never defines what a valid file is. Can anyone help me with file naming conventions for imports?

Thanks,

John

[Jaime Valencia]

There's no documentation to address that, and trying to move info between versions using BAT is most of the time not as simple as just exporting on A and importing on B, as the format might change, you would need to do an export of the same config (phone, line, etc whatever you're trying to migrate) and then manually compare the two, then adjust as necessary (add, remove, rename fields, etc)

[John Whitford]

The css csv file passes the validation. Even the header.txt file seems to pass the validation. But when I try to import the files don't show up.

Here's the css file validation report:

Validate Configuration Items

Begin Time : 01/18/2016 15:50:56

Failure Details :

FileName Error Code Error Description

-----------------------------------------------------------------------------------------

******** NO ERROR FOUND ********

Result Summary :

VALIDATE for 21 Records passed.

VALIDATE for 0 Records failed.

End Time : 01/18/2016 15:50:56

[John Whitford]

I found the issue. The import csv file name must be exactly the same as the exported csv file. 

Too simple.