Azure-Samples / Azure-Samples/document-intelligence-code-samples

DocumentIntelligenceClient has no begin_analyze_document_from_url

Aberta
#32 3 comentários 0 reações 0 responsáveis Ver no GitHub
Linguagem predominante
C#
Estrelas
201
Forks
115
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

> Please provide us with the following information:
I am using Document AI for extract information from Invoices:

```from azure.ai.formrecognizer import DocumentAnalysisClient```

This one is working fine for both online and local file upload using
```
document_analysis_client = DocumentAnalysisClient(
endpoint=endpoint, credential=AzureKeyCredential(key))
poller = document_analysis_client.begin_analyze_document_from_url(
"prebuilt-layout", document=file)
result = poller.result()
```

But this one for normal documents mine specific use case is for Invoices and upon using it, I am getting error saying 404 resource not found. I am using this:
```
document_intelligence_client = DocumentIntelligenceClient(
endpoint=DOCUMENTAI_ENDPOINT, credential=AzureKeyCredential(DOCUMENTAI_KEY))

poller = document_intelligence_client.begin_analyze_document(
"prebuilt-invoice", AnalyzeDocumentRequest(url_source=pdf_url)
)
```
> ---------------------------------------------------------------

### Error messages given by the failure
>
azure.core.exceptions.ResourceNotFoundError: (404) Resource not found
Code: 404
Message: Resource not found

### Expected/desired behavior
> It should work, I should get the normal output

### OS and Version?
> WSL Linux (Ubunutu 22.04)

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

Start at the DocumentIntelligenceClient.begin_analyze_document entry point and compare it with the working DocumentAnalysisClient.begin_analyze_document_from_url example in the issue. Confirm the supported request shape for invoice URLs and verify that the expected poller result is returned without a 404.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
azure, python
Domínio
api, cloud
Tipo de issue
Funcionalidade
Dificuldade
4/5
Tempo estimado
3-5 dias
Status de atividade
Estagnada
Clareza
Razoavelmente clara
Facilidade para iniciantes
35/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.