We are using record to populate a grid , till recently we are using this with out any issues, recently we got migrated from Appian 20.3 to 21.1 and we are facing this issue recently. Can you please help us.
Discussion posts and replies are publicly visible
Hi Ramnadh Srikanth Vemakoti,
Could you please share the exact error which you're facing? Any screenshot would be more helpful!
This is the error we are getting
Ramnadh Srikanth Vemakoti, If this issue is happening only after the upgrade, then I suggest contacting the Appian support team for help. But before reaching out to them. please check the record type configurations in the interface and make sure that they're correct.
It looks like this is appearing after a "Deactive" related action - is that correct? If so, do you expect the record to exist after you deactivate it? If not, usually the best approach to deal with this is to chain your action to a User Input task that acts as a temporary page with a link back to the record type. That way, the user would never see the error that the record doesn't exist.
Hi Peter,
Actually the "Deactivate" related action is performed and the record which is referred in the error is populated from a view which shows all the cases associated with the particular user who has been deactivated, previously we used to get the data when we are using 20.3 but recently our version got updated to 21.1 and then on wards we are facing the issue , all the security related to this is same as previous , but still its giving error intermittently,we checked if some racing is occurring but no racing is happening
Ok if you have not made any changes and you're seeing a behavior change between 20.3 and 21.1, then I'd suggest opening a ticket with Appian support.