- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
I have created the Order guide using 2 forms, once form is Manual form and another one is API from which is auto provision access by connecting with IIQ, it is an integration form.
I have written condition to display the form based on the selection.
It is working fine for Grant access, when i try to submit the request for revoke it is not connecting to IIQ and cancelling the request.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
28m ago
hey @sureshs3
i faced a similar issue with an Order Guide having two items, one manual form and one integration form connected to IIQ.
In my case, Grant access was working correctly but Revoke access was failing with the error
No record found in Look Up Record action on sys_user table.
After debugging the flow execution, I found that during Revoke the user sys_id being passed to the Look Up Record action was empty. Because of this, the Look Up Record action failed and the flow stopped before calling IIQ.
The main reason was how Order Guides handle variables. When forms are shown or hidden based on conditions, variables from the other item may not be populated at runtime. In my setup, the Grant form was correctly setting the user, but the Revoke form was either using a different variable or not populating the same value.
What helped resolve the issue
I stopped depending on catalog item variables for user lookup. Instead, I used the Requested For value directly from the RITM in the flow. This value is always available for both Grant and Revoke scenarios and works consistently.
Alternatively, if different users must be selected, both forms should use the same variable name and type, and that single variable should be referenced in the flow.
As a safeguard, it also helps to add a condition before the Look Up Record action to check whether the user sys_id is empty, so the flow does not fail unexpectedly.
After fixing the user context, the Revoke request connected to IIQ successfully and the cancellation worked as expected.
*************************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.
Regards
Vaishali Singh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Getting below error message.
An error has been dectected: 1. Details are No record found in Look Up Record action. Context id: xxxxxxxxxxxxxxxxxxxx, table: sys_user, encoded query: sys_id=
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
28m ago
hey @sureshs3
i faced a similar issue with an Order Guide having two items, one manual form and one integration form connected to IIQ.
In my case, Grant access was working correctly but Revoke access was failing with the error
No record found in Look Up Record action on sys_user table.
After debugging the flow execution, I found that during Revoke the user sys_id being passed to the Look Up Record action was empty. Because of this, the Look Up Record action failed and the flow stopped before calling IIQ.
The main reason was how Order Guides handle variables. When forms are shown or hidden based on conditions, variables from the other item may not be populated at runtime. In my setup, the Grant form was correctly setting the user, but the Revoke form was either using a different variable or not populating the same value.
What helped resolve the issue
I stopped depending on catalog item variables for user lookup. Instead, I used the Requested For value directly from the RITM in the flow. This value is always available for both Grant and Revoke scenarios and works consistently.
Alternatively, if different users must be selected, both forms should use the same variable name and type, and that single variable should be referenced in the flow.
As a safeguard, it also helps to add a condition before the Look Up Record action to check whether the user sys_id is empty, so the flow does not fail unexpectedly.
After fixing the user context, the Revoke request connected to IIQ successfully and the cancellation worked as expected.
*************************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.
Regards
Vaishali Singh
