An Azure service that turns documents into usable data. Previously known as Azure Form Recognizer.
Thanks for sharing the details and JSON schema that helps a lot.
Here are a few steps to try, based on what you described:
- Validate the ParsedResult Structure
- After your
GETcall from the Extract (trained) model, inspect the actual output JSON. Sometimes what you think the schema is and what the service returns can differ. - Make sure that the fields you map in Business Central (BC) exactly match the JSON structure, including nested paths. For example, if
PONumberis underresult → documents[0] → fields → PONumber → valueString, then your “Apply to each” / mapping logic in Power Automate should navigate the same path.
- After your
- Check the “Apply to Each” Logic
- It seems “Apply to each” is not “opening up,” which likely means the array you're looping over is either empty or not being referenced correctly. Confirm that you’re iterating over the correct array in the parsed JSON (e.g.,
documentsarray). - If
documentsis empty, that means Document Intelligence might not be detecting any document data which could either be a parsing issue or a problem earlier in the flow.
- It seems “Apply to each” is not “opening up,” which likely means the array you're looping over is either empty or not being referenced correctly. Confirm that you’re iterating over the correct array in the parsed JSON (e.g.,
- Schema Mapping in Power Automate / Logic Apps
- When you do “Parse JSON” in Power Automate, ensure the schema in that action exactly matches the shape of
ParsedResult. If there’s a mismatch, subsequent steps (like Apply to each) will not receive the data as expected. - Sometimes, using a dynamic schema (i.e., fewer “type” constraints) helps you debug: first you log the raw
ParsedResult, then build up a stricter schema only once you're confident about the structure.
- When you do “Parse JSON” in Power Automate, ensure the schema in that action exactly matches the shape of
- Logging / Debugging
- Add a “Compose” / “Log” action right after the GET call, so you can dump the
ParsedResultand visually inspect it in each run. - This will help you verify what data is actually coming back, and how to correctly point to fields for the BC “Create Records” mapping.
- Add a “Compose” / “Log” action right after the GET call, so you can dump the
Why this could be happening (context):
- Document Intelligence returns a nested JSON structure; if your mapping doesn’t exactly match, data won't flow into Power Automate’s loop correctly.
- The schema you defined for “Parse JSON” must match the real response — even small mismatches (like using
valueStringvsvalueInteger) will break downstream logic.
If you are still facing the issue, please share your error details, your current flow configuration, and the raw ParsedResult (with sensitive info removed) so the community can help you more accurately.
Thankyou!