Hi Chris
Your blogs have helped me a bunch of times so it's nice to advise you potentially.
Given that the digital signature outputs an image file you would think that the picture API, docs.microsoft.com/.../dynamics_create_picture, would be a contender. However, that API only handles a small amount of master data and I assume you want this signature for a document record? POD for example. There is an attachment API but you have also probably figured that is just the incoming documents feature: docs.microsoft.com/.../dynamics_attachment_patch
To achieve what you want some development will be needed. Sadly I haven't done it yet as I'm more of a novice when it comes to that, hence why I use your blogs. To get around the fact the BC connector is so weak I have used the HTTP connector in Power Automate very frequently. I would think that approach works here as you can call a power automate flow from your powerapp which takes the signature image. From there pass the image to a published web service from BC using the HTTP power automate connector. At least with that method you can stipulate the type of content being passed over. Would then be a case of deciding what holds the image in BC, this is where some BC based DEV could be done.
Not the final answer but hopefully a stepping stone towards it.
Thanks, Josh
