Property "children" does not have setter in class Magento\Catalog\Api\Data\CategoryInterface

[diwipl]

"children" field should not be included in documentation ( http://devdocs.magento.com/swagger/index_21.html ) of possible body of POST /V1/categories in catalogCategoryRepositoryV1 or it should be ignored in webservice itself.

The same applies to documentation of body of PUT /V1/categories/{id} webservice.

Preconditions

1. Magento 2.1.7

Steps to reproduce

1. Create POST request to /rest/V1/categories endpoint with body:

{   
	"category": {
		"is_active": true, 
		"name": "Test",     
		"children": "1"   
	} 
}

Expected result

1. Category is created

Actual result

1. {"message":"Internal Error. Details are available in Magento log file. Report ID: webapi-xxxxx"}

Exception log:

Next Exception: Report ID: webapi-5953d753666e8; Message: Property "Children" does not have corresponding setter in class "Magento\Catalog\Api\Data\CategoryInterface". in /var/www/vendor/magento/framework/Webapi/ErrorProcessor.php:195
Stack trace:
#0 /var/www/vendor/magento/framework/Webapi/ErrorProcessor.php(139): Magento\Framework\Webapi\ErrorProcessor->_critical(Object(LogicException))
#1 /var/www/vendor/magento/module-webapi/Controller/Rest.php(219): Magento\Framework\Webapi\ErrorProcessor->maskException(Object(LogicException))
#2 /var/www/vendor/magento/framework/Interception/Interceptor.php(146): Magento\Webapi\Controller\Rest->dispatch(Object(Magento\Framework\App\Request\Http))
#3 /var/www/var/generation/Magento/Webapi/Controller/Rest/Interceptor.php(39): Magento\Webapi\Controller\Rest\Interceptor->___callPlugins('dispatch', Array, Array)
#4 /var/www/vendor/magento/framework/App/Http.php(135): Magento\Webapi\Controller\Rest\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))
#5 /var/www/vendor/magento/framework/App/Bootstrap.php(258): Magento\Framework\App\Http->launch()
#6 /var/www/pub/index.php(37): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\Http))
#7 {main} [] []

[misha-kotov]

Thanks for reporting this - internal ticket MAGETWO-70400 has been created to track this issue. You really shouldn't be setting the "children" to 1, as that ID is usually reserved for the root catalog, but other values didn't work for me either, even when specifying "position" and "level" fields.

[diwipl]

The value was there just so the field "children" is not empty because that is triggering the error.

[magento-engcom-team]

@diwipl, thank you for your report.
We've created internal ticket(s) MAGETWO-70400 to track progress on the issue.

[magento-engcom-team]

Hi @devamitbera. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

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

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

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

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

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

[m2-assistant]

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

[github-jira-sync-bot]

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.magento.com/browse/AC-994

[github-jira-sync-bot]

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.magento.com/browse/AC-994

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://e252ffde96c0c082564fe7548c4a9ae2.instances-prod.magento-community.engineering
Admin access: https://e252ffde96c0c082564fe7548c4a9ae2.instances-prod.magento-community.engineering/admin_a4d1
Login: 3f82b383
Password: 63c2f3f79034

[engcom-November]

As the issue is quite old, we tried to verify this on latest 2.4-develop, but it is not reproducible.

Hence closing this issue.