3. change the column name of world.name to CountryISOCode
However, I was not able to associate the two tables via the CountryISOCode column by dragging and dropping either of the tables on each other. And also, the column name of CountryISOCode of the world.kml is changed to world.shp/features.CountryISOCode instead.
Could someone please advise or point out what did I do wrongly?
I tried out your suggested solutions but it still did not work for me.
I think the problem lies with the fact that the column name of 'World.Name' of the world.kml file cannot be changed to 'CountryISOCode' without an error message showing, which says 'the field name must be unique. the field already exists in table: salesdata$'
I meant just to load the sales data file. The world map is loaded automatically when you assign the country field as a geo field with ISO2 or ISO3 code. You don´t need to load a separate world.kml file.
PS: Yes, it´s right. The data manager doesn´t allow to rename a field to the same fieldname of an another source. For me this is a missing feature, because exactly by having same field name you can achive the match between data sources.
If you really need to load your own world.kml file you have to go to the data load editor, unlock the autogenerated code and then to rename the field automatically in the script. Unfortunately this will cause that the data load manager cannot be used for the existing loads (only for new loads).