This page has moved to Adobe Experience League and will be redirected soon.
ACSD-49370: Product attribute has 'FilterMatchTypeInput' type in GraphQL schema
The ACSD-49370 patch fixes the issue where the product attribute has a FilterMatchTypeInput
type in the GraphQL schema. This patch is available when the [!DNL Quality Patches Tool (QPT)] 1.1.28 is installed. The patch ID is ACSD-49370. Please note that the issue is scheduled to be fixed in Adobe Commerce 2.4.7.
Affected products and versions
The patch is created for Adobe Commerce version:
Adobe Commerce (all deployment methods) 2.4.3-p1
Compatible with Adobe Commerce versions:
Adobe Commerce (all deployment methods) 2.3.7 - 2.4.6
NOTE
The patch might become applicable to other versions with new [!DNL Quality Patches Tool] releases. To check if the patch is compatible with your Adobe Commerce version, update the magento/quality-patches
package to the latest version and check the compatibility on the QPT landing page . Use the patch ID as a search keyword to locate the patch.
Issue
The product attribute has a FilterMatchTypeInput
type in the GraphQL schema.
Steps to reproduce :
Create Date and Time product attribute.
[!UICONTROL Type]: [!UICONTROL DateTime]
[!UICONTROL Default Label]: [!UICONTROL Date Time]
[!UICONTROL Use in Search]: [!UICONTROL Yes]
[!UICONTROL Visible in Advanced Search]: [!UICONTROL Yes]
Query the GQL API documentation for the ProductAttributeFilterInput
type definition.
Observe the input type for the created attribute.
Expected results :
The Date Time attribute shows the filter input type FilterRangeTypeInput
.
Actual results :
The Date Time attribute shows the filter input type FilterMatchInputType
.
Apply the patch
To apply individual patches, use the following links depending on your deployment method:
To learn more about [!DNL Quality Patches Tool], refer to:
For info about other patches available in QPT, refer to [!DNL Quality Patches Tool]: Search for patches in the [!DNL Quality Patches Tool] guide.
Was this article helpful?
Yes
No
0 out of 0 found this helpful