When I try to add a custom order through admin interface, I don't get an option to select the attributes of the line item. But when I save it, I see that the default value of the Attribute is taken and is visible.

So when I go to edit, shouldn't I get an option to edit the Attribute?

Considering my use-case :

I am building a website for sale of Teeshirts. Whenever there is an offline sale I want to create an order so that all the sales(orders) are online. But when I try create new orders, I can't select the Tshirts Size which is an attribute. How can I select that when I am adding an order?

Thanks in advance,
Gokul N K

CommentFileSizeAuthor
Selection_293.png10.58 KBgokulnk
Selection_294.png13.12 KBgokulnk

Comments

rszrama’s picture

rszrama commented
Category: bug » support
Status: Active » Closed (works as designed)

Actually, there's a difference here between the front-end and back-end forms, and this represents one of the big challenges for Commerce 2.x. The back end of DC knows nothing about whatever product groups you may have created on the front end through your product reference fields. The only reason you see attribute options on the front end is because of the Add to Cart form being generated from these multi-value fields. On the back-end, you just have to specify directly the full SKU of the variation from the group that you're intending to add to the order.

So, technically speaking there's no bug here, but there's definitely a UX problem that's on the docket for fixin' in 2.x. More details as we get closer to opening the 2.x branch around DrupalCon Munich. : )

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Status: Closed (works as designed) » Postponed

Awaiting #1467180: Open 2.x Drupal Commerce branch.

rszrama’s picture

rszrama commented

I don't particularly care to keep this one open, as the issue in question was "works as designed". Tackling product groups is a much larger issue than simply how things appear on the back-end form, and it's not certain that tackling the primary issue will necessarily solve the back-end issue. Any other reason to keep this open? I can always just expand on the "2.x" issue (which we've been hesitant to open to prevent early distraction ; ) with the need to tackle product groups and just close this one out if that's fine with you. I'm allergic to dangling issues. : )

rszrama’s picture

rszrama commented
Issue summary: View changes
Status: Postponed » Closed (won't fix)

Issue queue maintenance. Commerce 2.x development has actually moved past this point already.