GraphQl error in customerOrders query: "\"model\" value should be specified"

[artskirk]

Preconditions and environment

• Magento 2.4.X

The following GraphQl error occurring in customerOrders query:

This is the body of GraphQl:

``

{
{
           {
         customerOrders { 
       items {
               increment_id
               status 
               order_number
               id 
               created_at
               items
{
 id status } 
      }
  }
  }
  }}

The issue occurring in module-sales-graph-ql/Model/Resolver/OrderItems.php:56. Undefined index $value<'model'> that should contains OrderInterface object

Steps to reproduce

1. Use the following GraphQl query:

 

{ {          
  {         
    customerOrders {       
                        items { 
                             increment_id 
                            status 
                           order_number id 
                          created_at
                     items { 
                              id status
                                       }
                                    } } }
 }}  

1. Observe the error output:
   }}`{{ { "errors": < Unknown macro: { "debugMessage"}
   ,
   }}

Expected result

GraphQl works with no errors

Actual result

Internal server error:

Additional information

No response

Release note

No response

Triage and priority

• [ > Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• < > Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• < > Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• < > Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• < > Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @artskirk. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Lima. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Lima]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Lima. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Lima, here is your Magento Instance: https://ecee69ee9b0ce378fe86fa9cea52c4aa.instances.magento-community.engineering
Admin access: https://ecee69ee9b0ce378fe86fa9cea52c4aa.instances.magento-community.engineering/admin_f448
Login: 90035302
Password: 526b41620fad

[engcom-Lima]

Hi @artskirk ,

Thanks for your contribution and collaboration.

Kindly use query given in official documentation .As query used by you showing deprecated.

{
  customer {
    firstname
    lastname
    suffix
    email
    addresses {
      firstname
      lastname
      street
      city
      region {
        region_code
        region
      }
      postcode
      country_code
      telephone
    }
  }
}

Below is the screenshot for your reference:

Let us know if you are facing any issue.

Thanks

[artskirk]

Hi @artskirk ,

Thanks for your contribution and collaboration.

Kindly use query given in official documentation .As query used by you showing deprecated.

{
  customer {
    firstname
    lastname
    suffix
    email
    addresses {
      firstname
      lastname
      street
      city
      region {
        region_code
        region
      }
      postcode
      country_code
      telephone
    }
  }
}

Below is the screenshot for your reference:

Let us know if you are facing any issue.

Thanks

Thank for your feedback! Anyway I would suggest to remove this line from schema.graphqls as deprecated functionality

[artskirk]

Hi @artskirk ,
Thanks for your contribution and collaboration.
Kindly use query given in official documentation .As query used by you showing deprecated.

{
  customer {
    firstname
    lastname
    suffix
    email
    addresses {
      firstname
      lastname
      street
      city
      region {
        region_code
        region
      }
      postcode
      country_code
      telephone
    }
  }
}

Below is the screenshot for your reference:
Let us know if you are facing any issue.
Thanks

Thank for your feedback! Anyway I would suggest to remove this line from schema.graphqls as deprecated functionality

Even is deprecated functionality it should working without issues.
Thank you!

[engcom-Lima]

✔️ Issue confirmed

Issue got reproduced in 2.4-develop branch.

Description: Graph ql error while running query to get details of customer orders.
Pre-requisite:
Fresh magento 2.4-develop should be installed.

Steps to reproduce:

1. Use the following GraphQl query:

{
  customerOrders {    
    items {
      increment_id
      status         
      order_number
      id      
      created_at
      items {
          id
          status
      }     
    }
  }
}

2. Check the response.

Expected result: GraphQl works with no errors in the response.
Actual result: Getting error in the response.
Screenshot:

Hence, confirming the issue.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-6084 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Lima. Thank you for verifying the issue.
Issue Available: @engcom-Lima, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[artskirk]

@magento I am working on this

[engcom-Hotel]

Hello,

As I can see this issue got fixed in the scope of the internal Jira ticket AC-6084 by the internal team
Related commits: https://github.com/magento/magento2/search?q=AC-6084&type=commits

Based on the Jira ticket, the target version is 2.4.6.

Thanks