Metaobject reference by handle instead of indecipherable IDs?

[lpscleay]

So when importing a product CSV file with metaobject references, any metafield containing metaobject references must use the ID, e.g.:

["gid://shopify/Metaobject/7110654347","gid://shopify/Metaobject/7110682215"]

This is super inconvenient to the point of being almost unusable, necessitating looking up and matching IDs to handles. The handles must be unique, so why not just use the handle as the reference?!

And as a kicker, when testing I had a few import errors that are even more indecipherable e.g:

UPDATE: Found by ID | Value: must belong to the specified metaobject definition gid://shopify/MetaobjectDefinition/312872443. 

The insane thing about this is that these metaobject definition IDs returned by shopify are not published or available anywhere (it's not in the URL as usual), so it's next to impossible to locate the error.

I'm using matrixify to import / export, but I assume this applies to all apps/methods. I've been back and forward with both matrixify support and shopify support with no progress.

All of this would go away if shopify would allow the use of handles instead of meaningless IDs to reference metaobjects.

Anyone have any ideas? — if I can't solve this then I'll be forced to ditch any use of metaobjects — they seem half-baked at best right now...

[prettypetty]

Maybe store the ID as a metafield?

[CavyArt]

Is this still the case? I have the same issue I'm trying to resolve right now.