n:n Relationships

Options
Steve Pankrath
Steve Pankrath Customer
Name Dropper First Anniversary DACH First Comment
edited January 2021 in Idea Exchange

1. What is your idea?

Currently it is only possible to have a 1:n relationship in the datamodel. I would like to be able to have n:n relationships.

2. What specific problem are you trying to find a solution to, or what new scenario would this idea respond to?

Our problem is for example that we have various articles, that are used/produced in different plants and therefore have some plant-specific values.
Another example is, that we have the same customer in various sales organizations.

3. What workaround have you found and used so far (if any)?

Right now we have to take these specific entities out of the entity-relationship and load them alongside with the data, where the specific value is matched according to article and plant information. And each datatable/view has do be adapted, when we need the data.
In order to be able to analyse the sales information for each sales organization we have created a new low leve entity with the combination of sales-organization and customer number.

 4. What is your role in your organization?

I am responsible for Board in terms of administration as well as developing new reports.

5
5 votes

Open For Voting · Last Updated