Importing Tariffs from CSV with wrong Regional Settings

From Kolmisoft Wiki
Revision as of 11:38, 4 April 2008 by Mindaugas (talk | contribs) (→‎Possible errors)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

In many computers Regional Settings affects how CSV is saved from XLS file.

MOR accepts CSV file where values are separated by comma "," and decimal places by point "."

Very often values are separated by ";" and decimal places by comma ","

In order to import such files, we need to fix them a little.






FIle in Excel looks like this:

Crs1.png




Let's save it to CSV format:

Crs2.png




CSV looks like this and we see incorrect file format for MOR import (';' and ',' instead of ',' and '.'):

Crs3.png




Let's open this file in some editor (MS Word in this example - any other will be good also):

Crs4.png




We see same picture in MS Word also:

Crs5.png




In Find and Replace window enter Find what: ',' and Replace with '.', e.g. we are fixing decimal values from ',' to '.':

Crs6.png




We replaced a lot of values:

Crs7.png




We see some improvement:

Crs8.png




Again in Find and Replace window enter Find what: ';' and Replace with ',', e.g. we are fixing value separation from ';' to ',':

Crs9.png




Even more fixes done:

Crs10.png




We see correct file format:

Crs11.png




Let's save it to another correct file:

Crs12.png




Now you are ready to import this CSV file into MOR tariffs.


Possible errors

International prefix

If all your destinations are BAD - make sure you import them in E.164 format - e.g. WITHOUT international prefix.

Example of bad file:

Crs13.png

Same file but fixed:

Crs14.png


Country instead of Destination

If you have fields like

Afghanistan Mobile

Then in Step 2 this column should be assigned to Destination/OCN Name instead of Country/Direction.

If you will make mistake in this step you will get a lot of BAD DESTINATIONS in Step 4.