i see the same thing in 8.3.03.
Are able to reproduce the same issue in 8.3.03 ?
1 of 1 people found this helpful
This may not be a unexpected behavior at Utility command level. Could be an issue with coping file from non windows server to window server. Later I tried executing the same command couple of times and find it is providing the data in the format given in Latest csv format.
i'm not sure what you mean about copying the file. the blcli command was run, the file was generated on the local file system. it contained the extra characters. that would seem to be a defect.
There is no defect as such. blcli command was run and a csv file was generated an the local file system (unix machine with file format mentioned in Latest csv file) and then it is copied to a window based system and there I have opened the file and found data in a format as shown in Earlier csv file.
I did not checked the content of csv file in the unix box and assumed it is same as I am getting in windows server after copied.
When verified the original csv file generated in the unix machine, I found that data always generated in Latest csv file format(with an additional comma at the end of each line).
Not sure why it changed its format across server while copying(removing an additional comma from each line).
“When verified the original csv file generated in the unix machine, I found that data always generated in Latest csv file format(with an additional comma at the end of each line).”
So on the unix box, where you ran the blcli command, the file that was generated had extra characters? If that’s the case, why do you think that copying the file has anything to do w/ this ?
Bill, Initially I have no access to the appserver where blcli command was run and generated the csv file. So I asked the respective owner to copy the file to a server where I have access, so that we can go ahead and build some script to parse the content of the csv file as part of requirement.
I have tested the script locally and then deployed in dev environment, where the logic of the script failed due to an additional comma in the actual csv file generated in the appserver and I have to change my parsing script logic there.
Later when I got the access to appserver, verified and found that the data always generated with an additional comma.
Earlier you have posted that "i see the same thing in 8.3.03." - what you mean by this ? Are able to reproduce the same issue in 8.3.03 ?
Yes, when I run the export command in 8.3.03, I see the same extra characters.
“verified and found that the data always generated with an additional comma.” -> that means it has nothing to do w/ copying the file.