Implemented
CRS Interface Logic
1 Comment
Our CRS cannot send the origin codes to Rover and this is a big issue for us. Rover therefore put a default origin to all reservations but we can't have proper tracking, analysis and therefore strategy.
Please adjust this so that the logic for the CRS interfaces goes like:
> If market, source and origin are in the XML, take it from the XML as long as the codes exist in Rover> If they don't exist in Rover - for Market, Source and Origin, take from the rate details.
5 people like this idea
Currently, if Market and Source codes are not received in the XML or the codes don't exist in Rover, Rover will use the default Market and Source Code as defined on the rate code first. Can we have this same logic applied to Origin codes, so that if the origin is not in the XML, we use the default on the rate rather than the interface default?