- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2023 10:49 AM
Hello SNC,
In to the story, I created an INC and on the incident i am clicking on UI-Action 'create outage' which has to create an outage record in cmdb_ci_outage. My test is running fine untill this step but the I am not able to open the record, I am getting the following error.
FAILURE: Failed to open the 'cmdb_ci_outage' form with id '371745b68762e550c540c916cebb35a4' Table 'cmdb_ci_outage' does not have a record with id '371745b68762e550c540c916cebb35a4' |
below(attached)is the test result,
has anyone faced it, FYI, I build other steps and same approach worked for othr and not for this, can anyone tell why?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2023 11:25 AM
I was able to figure it out myself.I created a submit record step after clicking the UI action.
Then the record was saved to the data base and was able to query for the record.
I followed the below approach..
My test was success now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2023 08:09 PM
not very sure then what's the exact issue.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2023 10:18 AM
Thanks @Ankur Bawiskar ,appreciaate your effot in trying to resolve it.
did anyone has the same issue??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2023 11:25 AM
I was able to figure it out myself.I created a submit record step after clicking the UI action.
Then the record was saved to the data base and was able to query for the record.
I followed the below approach..
My test was success now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2023 11:40 AM
I trust you are doing great .
Double-check the ID: Ensure that the ID '371745b68762e550c540c916cebb35a4' is correct and corresponds to an existing record in the 'cmdb_ci_outage' table. You can cross-verify this by searching for the record in the table directly.
Review the 'create outage' UI action: Examine the UI action configuration and associated script to verify that it is correctly creating a record in the 'cmdb_ci_outage' table and assigning the appropriate ID to the record.
Check for any related errors: Look for any other error messages or warnings in the system logs or browser console that might provide additional information about the issue.
Ensure proper access permissions: Verify that the user executing the 'create outage' UI action has the necessary permissions to create and access records in the 'cmdb_ci_outage' table. Check the ACLs (Access Control Lists) and ensure they are properly configured.
Regards,
Riya Verma