Azure-docs: TypeError - Detection Doc

Created on 23 Jul 2019 · 9Comments · Source: MicrosoftDocs/azure-docs

Hi, I tried the quickstart for Node.js, but it didn't work. I get in the prompt command and return to me the following Error: TypeError: TypeError: TrainingApi.TrainingAPIModels.Region is not a constructor

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d7a8e780-2ab0-2e3e-2232-d90eb7b13f01
Version Independent ID: 453992f2-180e-6af4-a872-a08feb884a50
Content: Quickstart: Create an object detection project with the Custom Vision SDK for Node.js
Content Source: articles/cognitive-services/Custom-Vision-Service/node-tutorial-object-detection.md
Service: cognitive-services
Sub-service: custom-vision
GitHub Login: @areddish
Microsoft Alias: areddish

Pri3 assigned-to-author cognitive-servicesvc custom-visiosubsvc product-issue triaged

Source

glaucia86

All 9 comments

@glaucia86 Thanks for the feedback. We are investigating into the issue and will update you shortly.

RohitMungi-MSFT on 23 Jul 2019

👍1

@areddish We can confirm that this issue occurs with the latest version of the package. Does the recent migration of nodejs packages to JS packages causing the issue?

RohitMungi-MSFT on 23 Jul 2019

👍1

@RohitMungi-MSFT Yes, this is due to recent migration. I'll need to investigate a solution.

areddish on 25 Jul 2019

👍1

I'll try to see something that I may help. I saw a same problem with another issue as well HERE

It would be a same solution? Just saying...

cc: @areddish and @RohitMungi-MSFT

glaucia86 on 30 Jul 2019

I also got the same error.
It is the same error to try this.

sato-sato-fixer on 2 Aug 2019

any update on this issue

Jegannathan on 12 Dec 2019

A small workaround to this issue is instead of TrainingApi.TrainingAPIModels.Region() just replace with {} empty object. this solves my issue

Jegannathan on 12 Dec 2019

@areddish just see it this answer.

A small workaround to this issue is instead of TrainingApi.TrainingAPIModels.Region() just replace with {} empty object. this solves my issue

glaucia86 on 13 Dec 2019

This has been identified as a product issue, not a doc bug or enhancement.
We want you to get an answer as quickly as possible so, please take a look at this document and post your issue to the relevant forum.