Check for commas in CLencryptedVesselIds, CLcomment, and CEencryptedVesselIds during upload

[davidcurrie2001]

During data upload can we check for commas in the CLencryptedVesselIds, CLcomment, and CEencryptedVesselIds fields and return a validation error if any are found?

[davidcurrie2001]

As a test I tried uploading CL data with CLencryptedVesselIds separated by commas. If I didn't quote the value then the validation failed, but if I quoted the field (i.e. "abc,def,ghi") then the upload succeeded. However when I downloaded the data that column only contained "abc

[HenrikK-N]

It is a priority to have a check for use of commas in the text fields especially CLencryptedVesselIds and CEencryptedVesselIds.

[HenrikK-N]

Check that it is mentioned in the description of the free text fields not to use commas.

[HenrikK-N]

A developer have checked that commas cannot be used as a separator in the CLencryptedVesselIds and CEencryptedVesselIds if the file is separated with commas, even though the CLencryptedVesselIds and CEencryptedVesselIds are in quotes. But if the file is separated by semicolons that the commas can be uploaded into the CLencryptedVesselIds and CEencryptedVesselIds, therefore we will remove the possibility to use semicolon as a file delimiter.

[HenrikK-N]

There should not be any commas in the CLencryptedVesselIds and CEencryptedVesselIds, but we keep the issue open for after the new uploads 1st April. The CLcomment will be double checked again.

[HSCole]

Hi, rather than open a new issue I thought I'd add this here as it is related. As well as checking for commas I would also suggest checking for spaces and forward slashes (/) in the CLencryptedVesselIds and CEencryptedVesselIds as I've seen examples of both.