#113 When Backend-API is created, transfer the API-Name with the correct

content type. Made the same fix for the filename as well, just in case.

Author: Chris Wiechmann

CHANGELOG.md

@@ -7,6 +7,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 ## [Unreleased]
 ### Fixed
 - Created BE-API response was parsing the response wrong. This could lead to an issue, if the API contains a createdOn field. (See issue [#112](https://github.com/Axway-API-Management-Plus/apim-cli/issues/112))
+- Unicode API-Name was not shown correctly in the Backend-API overview (See issue [#113](https://github.com/Axway-API-Management-Plus/apim-cli/issues/113))
 
 ## [1.3.0] 2020-11-10
 ### Added

modules/apim-adapter/src/main/java/com/axway/apim/adapter/apis/APIManagerAPIAdapter.java

@@ -788,10 +788,10 @@ private JsonNode importFromSwagger(API api) throws URISyntaxException, AppExcept
 		}
 		try {
 			entity = MultipartEntityBuilder.create()
-					.addTextBody("name", api.getName())
+					.addTextBody("name", api.getName(), ContentType.create("text/plain", StandardCharsets.UTF_8))
 					.addTextBody("type", "swagger")
 					.addBinaryBody("file", api.getApiDefinition().getApiSpecificationContent(), ContentType.create("application/json"), "filename")
-					.addTextBody("fileName", "XYZ").addTextBody("organizationId", api.getOrganization().getId())
+					.addTextBody("fileName", "XYZ").addTextBody("organizationId", api.getOrganization().getId(), ContentType.create("text/plain", StandardCharsets.UTF_8))
 					.addTextBody("integral", "false").addTextBody("uploadType", "html5").build();
 			RestAPICall importSwagger = new POSTRequest(entity, uri);
 			importSwagger.setContentType(null);