Hello Community, I am using Related Record action to update a case, using Rv!identifier as context to pass the case ID which needs to be updated.
And passing the identifier through rule input in the interface using a!recordActionItem, but it is not taking the correct input(case Id) in this scenario. Any idea why this is happening.
Discussion posts and replies are publicly visible
It is working perfectly with a!startProcess, only while using related action I am getting the error
And there is no node between the start node and the UIT that could be modifying this value?
Well for sure something is improperly mapped somewhere.
No nothing is present that would modify the value...But this error is only coming while using related record action not facing any issues while using start process link which is also implemented for the same use case
Any solution? The same thing is happening to me. I always get the same error identifier.
I try to create another related action with the same parameters and I obtein another error identifier.
I check the security of PM and RT, I also check the PM parameters and it is allright.
As a curiosity I started to get this error after cleaning the recordt type elements in db. Before the related action runs correctly.
I have synchronised the record type, updated the list...And nothing solves the error.
I would be very grateful for any help.
I don't know why it happens but I have seen it before fv!identifiers or rv!identifiers don't match with the primary key of that particular record.
Harshit Bumb (Appyzie) said:For clearing the blocker, for now, you can index the primary key field of the record type.
For now try doing this .
I had another record with relationship of the record in which I was facing the same issue. So I created Related Action on the other record type instead and it is working properly.
Hi,
As you mentioned that you are getting different ID when clicked on edit case .There will be possible scenarios for this error.1. rv!identifier is not the case ID (not primary key in that record), Case ID is different and identifier is different .2. When calling a!recordActionItem you are saying that you are passing through rule input. here also check whether the case ID is primary key or not. May be there is chance that you are showing one summary and that is having another field as primary key but by mistake you may consider it a case ID.
For example:- the summary is related to another record and having fieldA as primary key and in that summary when you are trying to use this related action, you are by mistakenly passing that fieldA as primary key .And you mentioned 69 , check any field in DB that is having 69 as value.
Thank you.