I have tried to update the fields using the following expression, however the data which got from interface is becoming null and record type is updating only with the expression values. Can any one pick it up and shoot it?
Discussion posts and replies are publicly visible
Interesting answer Stefan Helzle , because I would have thought just the opposite. Putting a bunch of a!save() into the UI just doesn't feel right to me. Is this still Appian's best practice strategy? I was hoping the end of this thread was going to say NOT to add a bunch of save's into the UI button event.
the documentation even explicitly states that "You can pass just the record's identifier and the new <field>, and only the changed field will be updated in the source."
<field>
https://docs.appian.com/suite/help/25.4/Write_Records_Smart_Service.html#update-existing-records
It seems like poor design to have to rely on a bunch of save's just to preserve existing values. it's difficult to maintain if you add new fields because now you have to go back to every object to update that.
Appian's functionality should handle this but it seems enough people have issues with it that I wonder if there's a way to prevent this issue from happening on the developer side.
Stefan Helzle