EPiServer Commerce: updating currency exchange rates automatically
Simple exchange rates updater automatically.
Why we need update exchange rates automatically
Currency exchange rates are changed everyday or hourly. This is quite important, our commerce site also need to update them to correct product price, shipping cost, ... more often.
How can we do
- Currency exchange rates source: in this sample, I used source from http://fixer.io/ - it's free and simple. You can chose whatever source if you feel trust.
- We have EPiServer schedule job - this is called and run in the background at preset time intervals (for more information, you can go here). So we could write a schedule job to update our task.
Step by step
Step 1: In your project site, create a class, name it as ExchangeRatesUpdateJob.cs.
This class will inherit from ScheduleJobBase.
[ScheduledPlugIn(
DisplayName = "Exchange Rates update job",
Description = "This job update exchange rates.")]
public class ExchangeRatesUpdateJob : ScheduledJobBase
{
public override string Execute()
{
return "Exchange Rate update Job was finished.";
}
}
This class is same as document I mentioned above.
Step 2: using CurrencyManager to update Exchange rates.
[ScheduledPlugIn(
DisplayName = "Exchange Rates update job",
Description = "This job update exchange rates.")]
public class ExchangeRatesUpdateJob : ScheduledJobBase
{
[NonSerialized]
private static readonly ILogger _log = LogManager.GetLogger(typeof(ExchangeRatesUpdateJob));
public override string Execute()
{
string message = string.Empty;
int records = UpdateExchangeRate(out message);
return $"{records.ToString()} currencies were updated. {message}. Exchange Rate update Job was finished.";
}
private static int UpdateExchangeRate(out string message)
{
message = string.Empty;
_log.Information("Starting to update exchange rate job.");
var processedCurrency = 0;
var dto = CurrencyManager.GetCurrencyDto();
var currencyCodeIdMapping = dto.Currency.ToDictionary(c => c.CurrencyCode, c => c.CurrencyId);
try
{
foreach (var code in currencyCodeIdMapping.Keys)
{
int fromCurrencyId;
currencyCodeIdMapping.TryGetValue(code, out fromCurrencyId);
try
{
var uri = $"http://api.fixer.io/latest?base={code}";
using (var client = new WebClient())
{
var json = client.DownloadString(uri);
dynamic d = JObject.Parse(json);
DateTime exchangeDate = d.date;
foreach (var rate in d.rates)
{
string toCurrencyCode = rate.Name;
int toCurrencyId;
if (currencyCodeIdMapping.TryGetValue(toCurrencyCode, out toCurrencyId))
{
var currencyRate = dto.CurrencyRate.NewCurrencyRateRow();
currencyRate.FromCurrencyId = fromCurrencyId;
currencyRate.ToCurrencyId = toCurrencyId;
currencyRate.EndOfDayRate = currencyRate.AverageRate = rate.Value;
currencyRate.CurrencyRateDate = exchangeDate;
currencyRate.ModifiedDate = DateTime.Now;
dto.CurrencyRate.AddCurrencyRateRow(currencyRate);
currencyRate.AcceptChanges();
}
}
dto.CurrencyRate.AcceptChanges();
}
}
catch (Exception ex)
{
message += "Cannot update currency {code}. ";
_log.Error("Cannot update currency {code}.", ex);
continue;
}
dto.AcceptChanges();
processedCurrency++;
_log.Information($"{code} rates were updated");
}
}
catch (Exception ex)
{
_log.Error("The job could not be completed. ", ex);
}
return processedCurrency;
}
}
Step 3: rebuild solution, reset your site to add our new Schedule job to system.
Navigate to CMS/Admin menu, we will see our schedule job in left panel.
Click on Start Manually to get first exchange rates.
Step 4: Set Active = true, in this sample, we will set schedule run everyday in 12.00 am.
So our job was FINISHED and this job will update exchange rates everyday to our site :)
You could download this file from my github.
Hope this post help your works.
/Son Do
Hi,
Nice. I would add my 2 cents:
1) you can (from v 10.3) inject ILogger interface in job via constructor injection
2) I would refactor so that *actual* exchange rate logic in somewhere outside - in some service or whatever, and scheduled job acts only as shell, as triggering mechanism that will call that service. This could make it easier to create unit/integration tests.
Hi Son, I actually created a NuGet package for this about a year ago, with two services/providers, Fixer and CurrencyLayer.
You could also use a different service by creating a different provider, see my post from last year for instructions how to do that.
@Valdis: thanks, I will update sample code for this.
@Jeroen: great to see your post and your github repo (y). You wrote out what I plan to do, this makes me feel good with currency area. Thank you.