First slight preface: we are attempting to bypass the shopping cart in our catalog, as we only allow one item to be ordred at a time anyway (for a variety of reasons). This means that the entire cart process (add to cart, select cart, submit cart) is unnecessary. We have modified existing request types to process as 'non-cart' items (bypassing the cart and going directly to submit). This is what the apparent purpose of 'one click' is.
However we have encountered something odd:
User selections are not populating on the subsequent interaction, however they DO appear as expected on the line items that are ordered.
So, in this example the user selection 'Printer Name', 'ASDF123' is filled out on the request and the cart is created (this happens in non-carts as well, via svccartitem table). The data is held in the 'options' field, which, according to the connector should go across per this line in the js tab :
if (options in $L.cartItem~=NULL and options in $L.cartItem~="</form>") then (svc.options in $L.file=options in $L.cartItem)
what I get however in the interaction.svcoptions field is just the fields, without their data (so I get an empty field labelled 'Printer Name', but not the corresponding data. The line items show the full setup, 'Printer Name','ASDF123' etc.
So it leaves me pretty puzzled since I was operating under the belief that the quote got its info from the interactio, but it appears to be getting it directly from the cartItem
Anyone have any thoughts on where breakdown is here? it seems to be somehow tied to the bypassing of certain cart steps (add to cart, checkout).