I agree with the suggested solution of manufacturer as an Item attribute.
I just wanted to add a single downfall of this. When you save pages with a filter on attribute, the count is done on item numbers, meaning it is not dynamic like normal saved pages. Should you ever need it. This might not be important to you, but it's worth remembering if it's something you will be filtering on often.
Dimensions could also be an option. This would have the added benefit that you could do fiscal reports on the cost/sales of items with dimension = Apple, and start doing analysis on this.
- Also doable using attributes in Power BI, but with dimensions you have the tools directly in BC.
It would have the added benefit of being able to do a saved page for all your apple products also.
Since you can have a 1: Many relationship between Item: Manufacturers, it is better to make it a Flow field showing the count of the number of Manufacturers (similar to "Stockkeeping Unit Exists" field on Planning tab). This doesn't allow you to look at the Item list to see the Manufacturers, but there are other ways to accomplish the same goal. Instead, go to what you know, i.e. the Manufacturer. Open the table with the Item/Manufacturer relationship defined and filter by the Manufacturer. Now you have a list of all Items from a specific Manufacturer.
If your Items only have a single Manufacturer, then I would agree with adding it to the Item Attributes so you can quickly filter to the Manufacturer attribute.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.