While importing a csv the checking process validates all the lines but then hangs on the next screen if it hits a ASCII CHAR not supported - could the validation also check for unhandled ASCII CHARs?
I am now stripping these out from CSV.
Long term we will move to using API imports - are they also limited to ASCII utf08?
Can you tell us more about which API import method you plan to use in the future?
Hope to move 3rd party service suppliers and providers to log incidents in our G2A service using the v2 API in the future.
In the mean time we are generating a csv to upload new tickets in to the service.
Thanks, we will look further into this.
@swampyedwards I'm sorry, this issue remains open currently.