Layers for Menu Items
Learn about Layers data for menu items and menu item components.
Overview
In the Menu tab of the Fillet web app, open the Layers tab to view the following tables:
This data is useful for a wide range of purposes, especially tracing the hierarchy of nested components.
These concepts may be familiar to you if you already use the “List all ingredients” feature in the mobile apps.Ingredient Layers table
Columns
This table shows all the ingredients contained in the selected menu item, including ingredients inside recipes.
This table consists of the following columns:
- Ingredient
- Layers
Data
This table presents the following data:
-
Each ingredient that is inside in the selected menu item.
(This includes ingredients inside sub-recipes, which are recipes inside the selected menu item.)
-
The chain of relationships between each ingredient and the selected menu item.
The chain of relationships consists of layers of sub-recipes. The top-level layer is the selected menu item.
Insights
This table provides the following insights:
-
Usage frequency of each ingredient
- See how frequently each ingredient is used in the selected menu item, and within which layers of recipes.
-
Role of each ingredient in a nested hierarchy
- Get insights about how ingredients are used in different contexts and purposes, in various intermediate materials.
-
Troubleshooting
- Detect any ingredients that are in need of issue resolution.
- Precisely identify where to input essential information, such as ingredient density.
Simple versus complex relationships
Ingredients in menu items
In a menu item, an ingredient is often contained in nested hierarchy of recipes.
This hierarchy may be a chain of simple relationships or complex relationships.
Recipe Layers table
Columns
This table consists of the following columns:
- Recipes
- Layers
Data
This table presents the following data:
-
Each recipe that is inside in the selected menu item.
(This includes sub-recipes inside recipes, which are inside the selected menu item.)
-
The chain of relationships between each recipe and the selected menu item.
The chain of relationships consists of layers of sub-recipes. The top-level layer is the selected menu item.
Insights
This table provides the following insights:
-
Usage frequency of each recipe
- See how frequently each recipe is used in the selected menu item, and within which layers of sub-recipes.
-
Role of each recipe in a nested hierarchy
- Get insights about how recipes are used in different contexts and purposes, as an intermediate material.
- Review combinations of recipes, as integrated into other intermediate materials.
-
Troubleshooting
- Detect any recipes that are in need of error resolution.
- Precisely identify where to input essential information, such as unit conversion.
Simple versus complex relationships
Recipes in menu items
In a menu item, a recipe is often contained in nested hierarchy of recipes.
This hierarchy may be a chain of simple relationships or complex relationships.
Comparison to "List All Ingredients"
In Fillet mobile apps, the “List all ingredients” feature provides a list of all ingredients in a selected menu item, including ingredients contained inside sub-recipes.
Layers is an even more powerful tool: You can trace the hierarchy of nested components, that is, the chain of relationships from the lowest level (the component) to the top level (the selected object). This is useful for reviewing how components are used in different objects: the different combinations, hierarchies, sequencing, etc.
As well, Layers helps you to more efficiently diagnose and resolve problems such as unit conversion errors. For instance, the Origins tab depends on unit conversion to standard mass or volume units of measurement. If any components have conversion issues, these issues must be resolved before Origins data can be computed. In this situation, Layers tab is useful for reviewing each component in the selected object and identifying which components are causing issues.