Site Forum

Just a quick heads up for the set fixers that submit IRs to move a standalone set beneath another set: Admin implemented a block this morning that prevents us from submitting IRs on base sets that still have inserts/related beneath them.

Real example, we had an IR earlier this year requesting to move 2012-13 Panini Dominion (previously a standalone set with inserts and parallels) into 2012-13 Panini Prime where it was distributed. The IR was submitted on the base set, the IR was double-approved, and the base set now appeared as an insert in Prime. All good there. Unfortunately, none of the inserts and parallels moved with it, so they weren't listed anywhere and couldn't be found unless we searched for them, and when we went into them, they still showed "2012 Panini Dominion" as their parent.

Moving forward, if we submit an IR on a set that still has inserts and we provide a link to a new set where it should be moved to, we'll now receive a warning message: "Insert sets must be moved first."

(Admin also updated the parent SID on all the missing inserts/parallels, and they now appear under 2012-13 Prime)

I was at first worried by the title that my DAV set migration flow would have to be worked around, but phew. Another useful and great feature added by Admin.

What a nightmare, thanks for helping correct things