Skip to main content

Types and Database Updates Via Multiple Robots

Article # 3048200 - Page views: 15


When using multiple robots that use a common type, how can the updates to records be retained when all robots process the same record?




When using a type shared across multiple robots, database updates are done using primary keys. When configuring a type, use the Part of Database Key option to mark the fields as primary keys.

For example, robot1 and robot2 processes invoices. Robot1 loads the invoice into the database and robot2 updates those invoices when it is paid. The type shared by both of these robots could have the invoice number and status fields as part of the database keys. When robot1 runs, the invoice number (which stays the same) coupled with the status (which will change from "open" to "paid" for example) would create a unique key for each update, thus creating two rows in the database.


Level of Complexity 



Applies to  

Product Version Build Environment Hardware
RPA 11.x      



Article # 3048200
  • Was this article helpful?