search

intacct / intacct-sdk-net

Official repository of the Sage Intacct SDK for .NET
https://developer.intacct.com/tools/sdk-net/
Apache License 2.0
31 stars 45 forks source link

AttachmentFile MUST reference a physical file path? #190

Closed tchpowdog closed 2 years ago

tchpowdog commented 2 years ago

Please add the ability to create an AttachmentFile with a byte array instead of having to provide a physical file path. In the "cloud" world, this just isn't practical. I have a service running in an Azure Function that needs to pull files out of cloud storage and push them into Intacct. I can't create a temp local file in the Azure Function due to potential file sizes.

Is there a work around to this issue? I have the byte array and the file is represented as a byte array in the end result XML anyway, but I can't get the byte array data into the "attachment" element.

The main problem is that AttachmentFile must contain a physical file path or the WriteXml method will not resolve.

dylan-holt-sage commented 2 years ago

@tchpowdog, we currently don't have plans to implement this, but please feel free to implement and raise a PR if you'd like to and we can review that. :)

mike-at-cmap-software commented 1 year ago

@dylan-holt-sage happy to have a look at implementing this. Do you want a new issue opened or to re-open this issue?

dylan-holt-sage commented 1 year ago

@mike-at-cmap-software, raise a PR when ready. No need for another issue or reopen :)