web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / Microsoft Dynamics 365 Support / Configuring a Category hier...

Configuring a Category hierarchy with your POS button grids

Views (9)
Randy Higgins Profile Picture Randy Higgins
In your Screen layout and Button Grids there is an option to utilize the Action = Search to set a Category that would provide the user with a result of pre-selected products within that Category.  In configuring this button, there is a stipulation that the category must be within the Navigation category hierarchy assigned to the Retail store to correctly pull this specific category result set.  If you do not use these linked Navigation hierarchies, then POS will generically show all products. 
 
To get the category to display properly, a suggested solution is to add a new Category Node to the existing Navigation hierarchy.  
 
  1. Go to the Channel categories and product attributes form. 
  2. Select the Channel for your store.
  3. In the Category hierarchy field, click this hyperlinked value to open that Navigation hierarchy.
  4. Edit this hierarchy
  5. Create a new category node for “XYZ”
    1. Add the associated products
  6. Go to the Screen layout > Button grids
  7. Open the Designer for the button grid to host this category button
  8. Add/Edit the button to point to the new Navigation hierarchy node (see screenshot below)
    1. Action: Search
    2. Search type: Category
    3. Hierarchy: hierarchy from the Channel categories and product attributes for this store
    4. Select the “XYZ”
    5. NOTE: You must select a hierarchy node in the grid
  9. Sync down the data (1090-Registers) to the CSU
  10. Launch POS and log into a new shift
  11. Test the button
 
NOTE: You may need to create a new node on the Navigation hierarchy like this for each store if they are using different Navigation Hierarchies.  Products can be part of multiple Navigation hierarchy nodes. 


Comments