Post

Patch Power Apps images and signatures to D365 F&SCM

Diesen Beitrag auf Deutsch lesen

Use camera or add picture controls in a canvas app, convert images to base64, and patch them to D365 F&SCM attachments.

TL;DR

A canvas app can collect camera photos or add picture images, convert each image to base64 with JSON and patch the data to the D365 F&SCM sales order attachments table. A signature is patched separately using the same Archive file approach, while the add picture control changes only the Capture formula.

Original by Hardit Bhatia, on The Power Addict. Read the original

This is our own summary, not a republication or full translation.

Why it matters

  • Makers: Store each captured image with a unique ID, the selected sales order, and its image value, then use ForAll and Patch to create D365 F&SCM attachments.
  • Makers: Use JSON with IncludeBinaryData and extract the base64 payload for the Archive file field, because that field carries the image data.
  • Admins/IT: Set up the canvas app connection to the D365 F&SCM virtual entity and attachment table, since the pattern relies on those data sources.

Frequently asked questions

How do I patch camera images from Power Apps to D365 F&SCM?

Collect the camera stream in a collection, then use ForAll and Patch to create sales order attachment records in D365 F&SCM.

What value goes into the Archive file field for D365 F&SCM images?

The Archive file field receives the base64 image content extracted from JSON output created with JSONFormat.IncludeBinaryData.

Does the Power Apps add picture control require different upload code for D365 F&SCM?

Only the Capture formula changes, using the image control inside the add picture control. The Upload formula remains the same.

This post is licensed under CC BY 4.0 by the author.