Can't upload tenant CSV file

Hi Greg, our logs are showing extra unsupported columns in the file.  This could be erroneous logging, but we'd need an example to determine either way.  Would you be able to send me an example of both your Mac and Windows .CSV files?  If so, please email them directly to me at elias.collins@sophos.com.

Elias, sent you an email with the files.

My system seems to have updated to 1.1.0, but I still can't upload CSV files. I have sent the files previously, but didn't hear of any problems with them.

Hi Joe, I did receive the .CSV file, thank you.  Versioni 1.1.0 was only to address the browser issues.  Version 1.2.0 tentatively scheduled for next week will address the .CSV import in the following ways.

1. Parse the .CSV file and auto wrap quotes around the script syntax suggestions in Column B
2. Update documentation to advise to look for commas in customer names and if so, wrap with quotes
3. Soft fail customer's that have commas in the name, but progress with the rest of the import
4. Log individual customer row failures from the import under the activity logs section 

Hi Joe, I did receive the .CSV file, thank you.  Versioni 1.1.0 was only to address the browser issues.  Version 1.2.0 tentatively scheduled for next week will address the .CSV import in the following ways.

1. Parse the .CSV file and auto wrap quotes around the script syntax suggestions in Column B
2. Update documentation to advise to look for commas in customer names and if so, wrap with quotes
3. Soft fail customer's that have commas in the name, but progress with the rest of the import
4. Log individual customer row failures from the import under the activity logs section 

I have manually fixed the CSV files to deal with the commas, but maybe I can do some more tweaks to make it happier?

Also, seems like getting this fixed on the partner portal so it produces valid CSV files would be a good thing.

I am having the same issue. I have reformatted as recommended, but still no go, not even with 1 row.  Noticed that my plugin is at 1.0.0.  Did 1.2 address this issue? and how do I kick off an update?

Hi Brian, thank you for working with us during this early adopter version.  I am sorry you are having these issues.  Version 1.2 was a release designed to correct this issue and did not require a license file as we were able to apply some better logic handling on the server side to handle commas in the rows as well as better error logging for when we did encounter an issue.

Would you be able to email me the offending file to elias.collins@sophos.com so we may troubleshoot and advise on what we're seeing with issues.

Hi Brian, we have just released version 1.3 which contains some enhancements to the logging for .CSV file import.  This is a breaking change for deployments so will require an upgrade of the license file.

Could I ask you download and install the latest license file either from the license manager within the Kaseya APP of from this link.  Re-attempt the .CSV file upload and let me know the results along with any errors listed under the logging tab?

I just upgraded my system. When I go to the page to upload the csv files, it has spinners under each download section and won't let me choose or drag files.

In past versions, it would eventually timeout and let me do things, but so far I'm not seeing it act like that.

Hi Joe, when you say you upgraded your system, does that mean you upgraded Kaseya, or our license file to the latest mentioned above in this thread?

I meant I upgraded the license. It finally did just timeout and let me choose files. They complain about the comma issue, so I guess I still have to manually fix them? Is anyone working to fix the downloads from Sophos Central so they are valid CSV files?

I just fixed my csv files and tried to upload them. Both gave the "Something went wrong. Please try again later." error.

On the other hand, I do see data in my Tenants section. I've never been quite sure how much data the Kaseya module can get from the API vs. how much it gets from the csv.

Hi Joe, while it seems like a reasonable path to modify the .CSV files themselves, it would be a fair amount of work to get that change on the respective teams backlog.  In the spirit of automation for integration, the product team believes it's efforts would be better placed in eliminating the need for the .CSV file altogether and allowing for full automated deployment via API.

I'll schedule some time with you through email for a remote session to gather some more logs and understand better where the kinks are on the upload.