We are thinking of what the best practice could be regarding tabular data.
Lets say we have chemical data, that could be an Id, Name, Description and an Image/Icon.
We want to relate this on a set of products and/or articles. But i want to refrain from using Multi-field as this means that the customer has to change the image on all 700 articles using that chemical code. I rather the customer change it in one place and it changes on all 700 articles.
So basically what Im thinking is a classical Field with a value, that points to some form of row in a table. But i want to make sure Im not missing out-of-the-box abilities to solve the issue.
One thought ive had is creating a custom back-office implementation of tabular data, but then the remaining part is having an easy way of pointing to a table and row on articles, so this also feels like it wont be a good user-experience.
tl;dr: Any input of ways of solving classical tabular data with x amount of columns to be pointed to a product and/or article is welcome.