We’re experiencing consolidation data import failures through ION workflows on ICS 2023-1. The workflow processes multi-currency transactions but consistently fails during the mapping activity phase.
The error indicates currency conversion issues when importing subsidiary data. Our workflow includes currency conversion logic, but the exchange rate updates don’t seem to apply correctly. The mapping activity configuration shows all required currency fields mapped, yet the consolidation process blocks at the currency validation step.
We’ve verified exchange rates are current in the system, but ION appears to use cached or outdated rates during the workflow execution. Has anyone encountered similar currency conversion problems in consolidation workflows? Need guidance on proper mapping activity configuration for multi-currency imports.
Here’s the complete solution based on your ICS 2023-1 environment:
Currency Conversion in Workflow:
The core issue is that your consolidation workflow uses static exchange rates initialized at workflow start. You need dynamic rate lookup for each consolidation batch.
Mapping Activity Configuration:
Modify your mapping activity to reference workflow variables for exchange rates instead of static configuration values
In ION Desk, edit the mapping transformation rules - change currency conversion from ‘Fixed Rate’ to ‘Variable Rate’ mode
Configure the mapping to use variables: ${workflow.exchangeRate.USD}, ${workflow.exchangeRate.EUR}, etc.
Remove any hardcoded conversion factors from the transformation logic
Exchange Rate Updates:
Add a new activity before your mapping activity: ‘Currency Rate Fetch Service’
Configure it to call the CloudSuite Currency Conversion API endpoint
Set the activity to execute synchronously and store results in workflow variables
Add error handling - if rate fetch fails, use fallback rates with warning flag
In ION Desk Connection Points, verify ‘CurrencyConversionService’ endpoint is active and properly configured
Implementation Steps:
Export your current workflow definition from ION
Add the currency fetch activity with output mapping to workflow variables
Update mapping activity input to reference these variables
Configure refresh interval - for real-time needs, fetch per batch; for daily consolidation, fetch once at workflow start but add manual refresh capability
Test with a small dataset first to verify exchange rates are applied correctly
Additional Configuration:
In CloudSuite Financials, go to Currency Management and ensure ‘Enable Real-time Rate Updates for ION’ is checked. This setting allows ION workflows to access the latest exchange rate cache. Also verify your consolidation entity mappings include the currency code field - without it, the workflow can’t determine which rates to apply.
After implementing these changes, your consolidation imports should process correctly with current exchange rates. The workflow will fetch fresh rates before each mapping activity execution, eliminating the currency validation errors you’re experiencing.
This draft is based on general Infor CloudSuite knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.
I’ve seen this before. The issue is often timing-related with exchange rate refresh in ION workflows. The mapping activity might execute before the currency conversion service retrieves updated rates. Check your workflow sequence and add a delay or synchronization point after the exchange rate lookup activity. Also verify the currency conversion service is properly registered in ION.
Thanks for the suggestion. I checked the workflow sequence and there’s no explicit delay configured. The exchange rate lookup and mapping activity run consecutively. Should I add a wait activity between them? Also, how do I verify the currency conversion service registration in ION? Is there a specific service name or endpoint I should look for in the ION Desk?
Check ION Desk under Connection Points and look for the currency conversion service endpoint. It should be listed as ‘CurrencyConversionService’ or similar. Also review your mapping activity configuration - specifically the transformation rules for currency fields. The mapping might be using static conversion logic instead of dynamic rate lookup. In ICS 2023-1, there’s a known issue where mapping activities cache conversion rates at workflow initialization rather than real-time lookup. You may need to restructure the workflow to force rate refresh before each consolidation batch.
We had the exact same problem last quarter. The root cause was the mapping activity using the wrong currency conversion method. Instead of calling the dynamic exchange rate service, it was using hardcoded rates from the initial workflow configuration. You need to modify the mapping transformation to explicitly invoke the currency service API for each transaction record, not just once at the workflow start.
That makes sense. I reviewed the mapping configuration and it does appear to use static conversion logic. The transformation rule references a fixed exchange rate table loaded at workflow initialization. How do I modify it to call the currency service dynamically? Is this done through the mapping activity properties or do I need to add a separate API call activity in the workflow?
You’ll need to restructure the workflow slightly. Add a loop activity that processes records individually rather than batch processing. For each record, insert an API call activity that invokes the currency conversion service before the mapping activity. This ensures fresh exchange rates for every transaction. Alternatively, if batch processing is required, add a pre-processing step that fetches all required exchange rates and stores them in workflow variables that the mapping activity can reference. The second approach is more efficient for large data volumes.