You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
"Depends on" is needed in every type of widget (dropdown, textbox, etc.), and the way it works now assumes that the property in the dependent entity and the one in the entity it depends on are called the same. For example, when we filter cities by country, both of the properties are called "Country"; however, when we want to take the BaseUnit of a Product to work as its UoM, the names are different.
Describe the solution you'd like
"Depends on" to be checkbox added to the widget type and to contain the property which value we take, the entity which will be filtered by the taken value and the property from that entity that we need.
Another checkbox would be useful to make that field editable.
Additional context
For example, we want the UoM property to take the value of the BaseUnit for the chosen Product. In this case, the "Depends on" option for UoM will take the Product value (Id), link it to the Product entity, and take the BaseUnit property of the Product entity.
Another case would be getting the Price value from the Product entity and using it in OrderItems. However, here we would make that field editable.
Is your feature request related to a problem? Please describe.
"Depends on" is needed in every type of widget (dropdown, textbox, etc.), and the way it works now assumes that the property in the dependent entity and the one in the entity it depends on are called the same. For example, when we filter cities by country, both of the properties are called "Country"; however, when we want to take the BaseUnit of a Product to work as its UoM, the names are different.
Describe the solution you'd like
Additional context
For example, we want the UoM property to take the value of the BaseUnit for the chosen Product. In this case, the "Depends on" option for UoM will take the Product value (Id), link it to the Product entity, and take the BaseUnit property of the Product entity.
Another case would be getting the Price value from the Product entity and using it in OrderItems. However, here we would make that field editable.
Acceptance Criteria
Country-City use-case:
At entity: Customer
At property: City
Product-UoM use-case:
At entity: SalesOrderItem
At property: UoM
The text was updated successfully, but these errors were encountered: