Something similar has already been suggested in the past and I fully support this one. It would be great instead of having to switch tabs all the time to find the id to search the brick.

I like this idea too!

Yes, that would be helpful. I'm not quite sure what exactly you mean with "inventory setup". Placing all parts directly in the scene (in rows by given number, if it's that what you suggest) would use up a large footprint and make it cumbersome to find parts when the model is big. Due to the different part dimensions it might be difficult to implement, too (would need sort of nesting).

I could imagine the following: importing a csv file creates a custom library section for the current scene holding all its parts with any duplicates filtered out (scene inventory). This way, searching would be limited to one tab and only parts appearing in a scene. Even if the parts in the inventory would be uncolored, that would already be a huge time-saver. Having a scene inventory would also make it easier to create different versions of a set.

I agree. An individual scene inventory by a CSV file makes more sense instead of picking the parts in the scene directly.

Apart from an inventory import function: Having a scene inventory built on the fly for every scene would be a welcome enhancement as well, as it would provide a library usage history: if a certain part shall be added again, after some other part has been looked up, it could be found in the inventory, so no navigating back to the respective part section or search (of course a part can also be copied, but it might be at a location in the model which is difficult to access or the orientation of the copy would have to be reset before further use).

Hello,

how to import a CSV file in the workhop, in order to use the set of pieces?

Thanks.