Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.0.5 SOAP API: Encoding: object has no 'label' property #4630

Closed
mch35 opened this issue May 23, 2016 · 3 comments
Closed

2.0.5 SOAP API: Encoding: object has no 'label' property #4630

mch35 opened this issue May 23, 2016 · 3 comments
Labels
bug report Component: Framework/Webapi USE ONLY for FRAMEWORK RELATED BUG! E.g If bug related to Catalog WEB API use just Catalog Fixed in 2.2.x The issue has been fixed in 2.2 release line Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@mch35
Copy link

mch35 commented May 23, 2016

Hello,

I try to use Magento 2.0.5 SOAP API. I am not able to retrieve attribute options. Attribute with code dm1 exists in the shop.

Request

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:def="XXX/soap/default?services=catalogProductAttributeOptionManagementV1%2CintegrationAdminTokenServiceV1">
   <soap:Header/>
   <soap:Body>
      <def:catalogProductAttributeOptionManagementV1GetItemsRequest>
         <attributeCode>dm1</attributeCode>
      </def:catalogProductAttributeOptionManagementV1GetItemsRequest>
   </soap:Body>
</soap:Envelope>

Response

<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
   <env:Body>
      <env:Fault>
         <env:Code>
            <env:Value>env:Receiver</env:Value>
         </env:Code>
         <env:Reason>
            <env:Text>SOAP-ERROR: Encoding: object has no 'label' property</env:Text>
         </env:Reason>
      </env:Fault>
   </env:Body>
</env:Envelope>
@SteveRohrlack
Copy link

same here

As a reference, I created a dump from catalogProductAttributeRepositoryV1Get for the attribute.

At first I thought this has something to do with the option labels per store but all options already have separate labels for store and admin.

@choukalos
Copy link

Tracking internally - MAGETWO-53431

@vkorotun vkorotun removed the PS label Aug 4, 2016
@vkorotun vkorotun added the Component: Framework/Webapi USE ONLY for FRAMEWORK RELATED BUG! E.g If bug related to Catalog WEB API use just Catalog label Aug 22, 2016
@veloraven veloraven added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Oct 26, 2016
magento-team pushed a commit that referenced this issue May 12, 2017
- MAGETWO-53431 [GITHUB] SOAP API Encoding Object has no 'label' property #4630
- MAGETWO-58652 [GitHub] REST API multiselect attribute values are sent in an incompatible format and cannot be cleared #6120
- MAGETWO-62567 Make static file versioning number not based on timestamp
- MAGETWO-63741 [FT] Magento\Catalog\Test\TestCase\Product\CreateSimpleProductEntityTest fails on CI
@magento-engcom-team magento-engcom-team added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development bug report Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Component: Framework/Webapi USE ONLY for FRAMEWORK RELATED BUG! E.g If bug related to Catalog WEB API use just Catalog labels Sep 11, 2017
@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented Sep 20, 2017

@mch35, thank you for your report.
The issue is already fixed in 2.2.0

@magento-engcom-team magento-engcom-team added 2.0.x Fixed in 2.2.x The issue has been fixed in 2.2 release line labels Sep 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Component: Framework/Webapi USE ONLY for FRAMEWORK RELATED BUG! E.g If bug related to Catalog WEB API use just Catalog Fixed in 2.2.x The issue has been fixed in 2.2 release line Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests

6 participants