[cool_brat]

Hi All,

Could u please let me know if there is any property in OTM which stops the auto-generation of Lanes. Currently, if I am saving itinerary multiple times then that many lane ID's are getting generated.

I am not sure if this is a bug or designed functionality. If this is a designed functionality then please let me know the reason behind this.

Regards
Vipin

[AMM]

Hi Vipin,

I don't know of anything that would stop the scenario that you have described, but that doesn't mean there isn't a property somewhere...

However, if I am creating more than a few itineraries and rates, or moving my configuration between e.g. a development environment to a test environment, my preference when configuring is to use csv files, and thus I can create lane GIDs that are non-numerical e.g. DOMAIN.XL_SOURCE_DEST, and avoid the situation that you are concerned by.

[cool_brat]

Yes, you are right that no scenario will stop because of auto-lane creation.

Only thing is that lot of unnecessary data reflects in the lane definition view. So I was just looking out to find if there is any way to stop it from auto-creating. Also, I am confused like if rate distance should be defined against all the lanes created or it should be defined only once for a lane manually created.

[new_otm]

Hi,
I have used csv to load itineraries so I have created the x_lanes by csv too. My problem is that the itinerary is not using the x_lane I have assigned and every time I access to one x_lane by power data if I click on finished I have a new numeric x_lane id. Have you solved the problem?



Thanks.

[AMM]

Sorry, I just edited one of my itineraries, and I see what you mean that OTM creates a new numerical x_lane gid and replaces the existing one. And if I edit that new numerical x_lane, it creates yet another x_lane gid for the itinerary!

Unfortunately, I haven't actually solved this problem. Our itineraries tend to be very static once we have created the itinerary that we want, and so I hadn't actually noticed this happen before. Beyond doing a update on the itinerary via csv, I'm not sure how to get around it, sorry.

[cool_brat]

I guess, technical folks can give better idea why every time a user click on Lane then system generates a new lane and system starts referencing the new lane instead of old one.