Sorry if this is not the correct topic but there wasn’t one for Admin UI.
Currently when using the bulk editor, you can change the query parameters to reflect which columns you want, this works great when you are in your own editor.
As soon as you give that link to someone else the editor view changes completely overriding the list of custom columns you had set. Making it really difficult to share predefined views and edits with each other.
Hey hey again @JordanFinners 
I took a look at this on our end, and the current behaviour does look expected from what I can see. Without sharing too much internal info, right now the edit= values in the URL are used as a starting point for the visible columns, but the bulk editor also normalizes that view based on what the current user/shop/session can actually render. So it can end up changing when the link is opened by someone else, rather than behaving like a fully shared saved view.
I definitely get why that’s not super ideal though. Can I ask what the main use case is here? Are you sharing these links with clients, teammates on the same store, or using them more like reusable internal quick-edit templates/bookmarks?
Happy to pass along feedback as always, just want to make sure I’m grabbing all the context I can 
One of the biggest issues with this at the moment as well, which maybe I’m misunderstanding as well, is if you have a lot of products and scroll you get columns added back in which clutters up the view.
I can’t imagine that’s actually expected behavior where you lock down the view only to the metafields or whatever properties you want and then as additional products load that you get more fields cluttering up the admin.
The predefined views are really helpful to share with clients easily when they have to make updates in the future. Otherwise we’re pushing them towards paid apps for something that has historically worked quite well natively.
This happens regularly with client work at least to make things easier on the merchant. If you send them to a view that then gets completely distorted, it loses its value and it’s not a trusted place to make updates at all as it increases the likelihood of staff making errors.
For example my app has a custom metafield called Pack Size, just a standard number metafield
It would be helpful to be able to send a merchant this view so they can better understand they can bulk edit it
However if I then follow that link, in just another tab the bulk editor decides to add 7, I open it again and this time it adds 15 columns (for no apparent reason)
And so suddenly a simple view is now filled with other information which wasn’t requested and Pack Size is hidden. In this example its the 2nd column but not always.
Its just incredibly inconsistent experience, that I have no confidence sharing with a merchant
Hey folks - thanks for the extra context here!
Just to separate the two pieces a bit: the URL/shared-view behavior I mentioned above is still the expected limitation from what I can see, in that the bulk editor URL can be normalized depending on the current user/shop/session rather than acting like a fully saved shared view.
That said, the part where additional columns/metafields are being added back while scrolling or when reopening the same bulk editor link is a different behavior, and I definitely get why that would make the view feel unreliable for merchants. We’ve seen a similar report around columns being added back on scroll, so I’m going to pass this example along there as well since Jordan’s metafield example is a useful concrete case.
I can’t guarantee a timeline from here, but I’ll keep this thread in the loop if I get more info to share. Let me know if either of you notice a specific pattern in which fields get added back, especially whether they’re category/generated metafields, product fields, or app-owned metafields.
