We are looking to create a solution where an end-user can upload an image, and then attach it to a SerializableCart or PurchaseOrder or something similar. We can attach the image as base64 as a property, but it's not ideal and I don't know what limitations we have on size etc.
I've noticed that there is a ImageFile-metafield that we could add to our Order-object, but how would one implement such a feature?
We would suggest to upload the image as an asset, then attach the link to the asset to SerilizableCart/PO as a field. MetaFile is a legacy solution and is not very performant/scalable
If there a downside to this solution? For example if an end-user uploads several images over and over again? or should we have a job that deletes the assets after a month or something?
- May 27, 2019 11:27
You can just make sure the image is overwritten if the end user upload multiple time per lineitem
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
Hi!
We are looking to create a solution where an end-user can upload an image, and then attach it to a SerializableCart or PurchaseOrder or something similar. We can attach the image as base64 as a property, but it's not ideal and I don't know what limitations we have on size etc.
I've noticed that there is a ImageFile-metafield that we could add to our Order-object, but how would one implement such a feature?
Has anyone done anything similar?
Best regards