Record Type Field

docs.appian.com/.../fnc_array_a_update.html

Thanks for your quick response. I ran the update for a vehicle record type to update the image number, it ran an returned the correct value, but when I queried the underlying data it still holds the old value.

This does not modify the data in an external system. This includes the database. Use the write records functionality to persist the modified data.

I am sorry, can you please point me to an example?

https://docs.appian.com/suite/help/22.4/Write_Records_Smart_Service.html

docs.appian.com/.../Process_Modeling_Tutorial.html

Isn't there an easier way to change a field value in a row?

Depends on how you approach Appian as a platform. Seems like the patterns you are used to, collide with the way how Appian works.

What do you want to achieve? What do you want to build?

I uploaded bunch images in to a folder in Appian and they all got new Ids, In my sample app the source table in the database has different Ids. I just wanted to update them with the new values. That's all.

So, in general you cycle of modifying data is to query it and store it in a local variable or in a process variable. Then you modify it and lastly write it back to the DB. For the last step, you use a!writeRecords() in an interface or the Write Records smart service in a process.

My perspective on Appian is, that is is made to build business processes. And by this, I mean the organizational aspect of that process that orchestrates people and systems. I talk about this in my podcast episode with Malcolm Ross, VP of Product Strategy at Appian.

So, if you approach Appian as a low-code platform in the same way as e.g. PowerApps, you will probably get into a painful collision with the reality of Appian solution design.

Find my podcast and other Appian related stuff here: https://appian.rocks

So, in general you cycle of modifying data is to query it and store it in a local variable or in a process variable. Then you modify it and lastly write it back to the DB. For the last step, you use a!writeRecords() in an interface or the Write Records smart service in a process.

My perspective on Appian is, that is is made to build business processes. And by this, I mean the organizational aspect of that process that orchestrates people and systems. I talk about this in my podcast episode with Malcolm Ross, VP of Product Strategy at Appian.

So, if you approach Appian as a low-code platform in the same way as e.g. PowerApps, you will probably get into a painful collision with the reality of Appian solution design.

Find my podcast and other Appian related stuff here: https://appian.rocks