GraphQL API - Unexpected response using products query of virtual catalog
karimul opened this issue · 5 comments
Describe the bug
We have updated the platform version to 3.412.0, but we have an issue using GraphQL API products query when the store’s catalog is a virtual catalog (physical catalog is working properly), the response is not showing the actual data of the physical product. We have used this GraphQL query in the older platform version 3.208.0 which works fine.
Steps to reproduce
Steps to reproduce the behavior:
- Go to 'Catalog' menu
- Add virtual catalog 'TestVirtualCatalog'
- Select 'TestVirtualCatalog' and add a link to physical Category or Product.
- Go to 'Stores' menu
- Add new store and select catalog 'TestVirtualCatalog'
- Query products using GraphQL API
Expected behavior
The GraphQL API response is showing the actual data of the physical product.
Screenshots (optional)
Screenshots of the GraphQL responses using the same product:
Store using physical catalog
Store using virtual catalog (issue)
isBuyable: false (should be true)
availableQuantity: 0 (should be 98)
price.list.amount: 0 (should be 1100)
Version info (please complete the following information):
- Browser version: Google Chrome 117.0.5938.150 (Official Build) (64-bit)
- Platform version: 3.412.0
Task https://virtocommerce.atlassian.net/browse/VP-8460 has been created
Hi, @karimul! Could you describe the settings in the store where the virtual catalog is used? Which fulfillment centers are selected? Any price list assignments for this store?
@AlexTzykin I used the default settings. There is no changes I did.
I didn't select any fulfillment center
The distinction I've observed between physical and virtual products lies in the pricing information.
the price in physical product is shown
@karimul need to select the fulfillment center in the new store (where the virtual catalog is selected) to see the availability of product.
You also need to create a new pricelist assignment linked to a new store or virtual catalog.
@AlexTzykin ok thanks