- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2018 06:31 AM
We just upgraded our DEV instance to London Patch 1. First thing I noticed is when a request comes in one of the variables is not transferring over to the RITM. It is a required field when you complete the request. Why would it not transfer over?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2018 06:36 AM
What kind of variable is it? Is it possible there is a client script or security running against the catalog item that only applies on the ritm form? Also check to see if there is a client script running on the RITM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2018 06:53 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2018 06:53 AM
I did deactivate it and tried it again, but same results.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2018 06:58 AM
Brad, we probably have too many cooks in the kitchen here. I'll let you run with this one so we aren't sending conflicting messages. I'd probably check the 'sc_item_option_mtom' table next just to make sure the variable is actually populated there. Would tell you to look at something in the client or not. Let me know if you would like my help in jumping back in!
@pagdenl, you're in great hands!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2018 08:24 AM
Just letting you know, apparently you cannot have your variable set and the variable as the same name. It has been working all this time but in London it is not allowed. New rules now. Sorry for all the hassle.. This was to easy..
Thanks for all the advice. great information..