Can we extract fields from document to one target field using Document intelligence ?

[Kien Luc Tuan]

Hi everyone, I'm new on the journey to discover power of Automation Engine and I'm trying to practice the Document Intelligence Tool.

Following the document intelligence solution and documentation,  after configuring use case - keys, ..etc.. based on guidelines about Document intelligence setup that I wonder if can be applied or not:

My question is:
Could we have many Keys with the same Target field in use case?

For example
Various data along with keys extracted from the document then they are populated to the custom field "Payload" in the table using an object format like below:

payload: {
      key 1: data1,
      key 2: data2,
      key_group:   {
                    key3:   data3,
                    ......
     },
     .......
}

If this work, I can continue my process, retrieve extracted data using flow designer via "Integration setup" in the related list of Use case

Please let me know your idea.

[Loic1 · Accepted solution]

Hi @Kien Luc Tuan,

Can you share more details about what you are trying to achieve?

To answer your question, if you have more than one Key with the same Target Field, and you use the OOB Flow, the value in that field will be overwritten and only one Key value will show in that Target Field.

But it seems like you are trying to do something a bit more custom, in which case I'd recommend that you fetch the values directly from the di_extracted_value table. The "Retrieve Extracted Values" Action in the OOB Flow is doing something similar.

I hope this answered your question, please share additional details if you need.

[Community Alums]

Hi @Kien Luc Tuan ,

You can create multiple tasks to achieve it.

follow the doc and the links mentioned inside:

https://docs.servicenow.com/en-US/bundle/utah-intelligent-experiences/page/administer/document-intel...

[Kien Luc Tuan]

Hi @Community Alums, thank you for your response, there are some questions:
1. I wonder if we can upload multiple attachments per document task as I just want to get extracted data of some desired attachments and add all data to "Payload" field as mentioned.
2. could we return the sysid for each attachment extracted?

*I currently use OOB flow designer as Integration setup of use case

I really appreciate your upcoming answer. Thank you

[Loic1 · Accepted solution]

Hi @Kien Luc Tuan,

Can you share more details about what you are trying to achieve?

To answer your question, if you have more than one Key with the same Target Field, and you use the OOB Flow, the value in that field will be overwritten and only one Key value will show in that Target Field.

But it seems like you are trying to do something a bit more custom, in which case I'd recommend that you fetch the values directly from the di_extracted_value table. The "Retrieve Extracted Values" Action in the OOB Flow is doing something similar.

I hope this answered your question, please share additional details if you need.

[Kien Luc Tuan]

Hi @Loic1, thank you for your response.
My context is about identifying desired attachment to only save correct data to a custom field "Payload" on sn_hr_core_task table as format: 
      {    "key":  "",     //key might be the unique data for each attachment

           "sysid_attachment":   "" //the attachment sysid on target attached record  (for this case is "HR task" record)

}
For example: after 1 HR task record is created, I attach many files to it. 
There is just one attachment containing data I want to save to "Payload" as the format above.
But following your answer, the value will be overwritten when many Keys have the same Target field.

So, is there any way to save extracted data into the same field as the format above, not overwritten?
How can we track which attachment is extracted via Flow Designer in case the flow trigger created target record has uploaded many attachments? Did we need a custom action on Flow to return desired Output containing sysid attachment?

I am so excited to hear your idea, please share your opinion. Thank you.