The Table output binding to ICollector works for inserts only. If you try to write values that already exist it errors. It would be neat if there was a way to allow the Function writer the option to specify insert behaviour so that they can choose Insert / InsertOrReplace / InsertOrMerge.
This will save Function writers having to code this behaviour from scratch. A simple use case is the output binding sample - it will error after the the first run because the binding is Insert only.
(A previous ticket #8 requested default behaviour as InsertOrReplace)
This comes up quite a bit. We should do the work. Again on SO here: https://stackoverflow.com/questions/42492777/how-to-update-a-azure-table-row-in-azure-function-using-bindings. Assigning back to triage so we can reconsider. We just did similar work recently for DocumentDB - it supports updates naturally. We should do the same here.
I vote for this feature.
@MikeStall to investigate the cost.
Voted as well. This is an important feature please
Hi @MikeStall @christopheranderson @lindydonna there have been no updates on this issue since April. Is this going to be considered for a fix or do we still need to rely on using the Azure Storage SDK to write to table?
Would be nice to get a "correct" way of doing it =) tablebinding seems like the simplest way but.
It'd be great if can have updates on this. Have been waiting long to see this feature.
Any update on this?
It's almost a year since the bug is open. Any updates?
How can this still be an issue after all this time? It is the most frustrating thing and really does not instill confidence in Azure functions
This functionality would be very nice :)
This is still an issue?! Wow...there goes my plan!
My hope that this issue would have an answer was pretty high when I saw that the first comment was made back in 2016. my hope slowly died as I read through all the comments on this thread.
Will be very useful feature.
I also need this
Please?
Pretty please?
This works if you set the ETag of the entity to "*".
Setting ETag to "*" does indeed work here (I didn't actually know that!). We'll treat it as an InsertOrReplace operation. There's a stackoverflow post with an example here: https://stackoverflow.com/questions/36792547/azure-functions-table-binding-how-do-i-update-a-row/55527201#55527201.
It looks like this does not work from node, however. #2311 is tracking that.
Amazing 馃帀
Most helpful comment
I vote for this feature.