Share via

Is there a full list of all Field Extraction properties?

Del 0 Reputation points
2024-03-29T00:02:39.05+00:00

Is there a full list, or can a full list be provided, of ALL properties that can be used / mapped for field extraction?

For example, on the following Microsoft webpage, for AI Document Intelligence, it lists a total of 36 properties that can be setup for field extraction.

https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/concept-invoice?view=doc-intel-4.0.0

However, I've counted a total of 115 total properties that can be used for field extraction, some of which have minor differences, in particular, some of the Address related properties have minor differences. I would like to request a full list of those 115 properties, listing out the name and data type, just as the table shown on the Microsoft webpage linked above.

Can such a list be provided?

Thank you.

Azure Document Intelligence in Foundry Tools
0 comments No comments

1 answer

Sort by: Most helpful
  1. VasaviLankipalle-MSFT 18,736 Reputation points Moderator
    2024-03-29T03:02:05.61+00:00

    Hello @Del , Thanks for using Microsoft Q&A Platform.

    I understand that you were looking for a comprehensive list of all the Field Extraction properties, but unfortunately, there is no such documentation available at this moment. Each model has its own detailed supported field list, and the model overview page provides all the information regarding the available models.

    However, I can share your feedback with the product team. Please note that there is no ETA regarding this.

    The temporary workaround you can do is to gather the list of properties yourself.

    I hope this helps.

    Regards,

    Vasavi

    -Please kindly accept the answer and vote 'yes' if you feel helpful to support the community, thanks.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.