ContributionsMost RecentMost LikesSolutionsGetGo API G2ASD - adding a new incident and updating the occurred at datetime I have tried to email the developer support but no response so thought I would try here. I am able to POST a new incident using the G2ASD API v2 but I am unable to create with a custom "occurred_at" date time or update this value with a PUT incident. Has anyone else had any luck or can point me to how to capture this correctly? S Re: csv upload - ASCII char causing import to hang any update on this issue? Re: csv upload - ASCII char causing import to hang 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. S csv upload - ASCII char causing import to hang Hi 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? Re: csv import timezone incorrect Thanks, Ash Have added a manual BST to UTC adjustment to create the CSV sheet for importing. csv import timezone incorrect When importing incidents to G2A using a csv the timezone seems to be an hour out. My account is set to London (GMT +0) The service is set to London (GMT +0) The csv file is generated in Google Sheets and the orig doc has the timezone as London. The value in the csv is correct but I cannot see an adjustment for DST (BST). Does the csv import expect UTC times?