ODataUnrecognizedPathException Error - at my wits end!!

(1) Share

Report

Posted on by AC-27061552-0

Hi,

Below is my current workflow.

The purpose of the workflow is the following:

Step 1- Trigger of the workflow is the incoming email into a shared mailbox.

Step 2,3 & 4- Set the case number as a variable and trim it down to 16 characters in case the customer has included any additional text other than the CAS number.

Step 5-List rows of cases where the casenumber matches that on the subject of the email, selecting incidentid for later use.

Step 6-List rows of the incoming emails where subject contains the case number I have grabbed from the incoming email

Step 7-Condition if case exists, (set regarding cases value to incidentid):

a. Apply to each email where subject contains CAS number grabbed in Step 6.

b. For each case with the incidentid that has been returned in step 5.

c. Regarding value is set to incidentid which I know is valid and present as I confirmed from json logs earlier.

I know that as far as step 6 is working as I've tested each individual component to ensure all my id's are correct etc.

However no matter what value I input into step 7 to set the case regarding value I get the following error:

 "error": {
    "code": "0x80060888",
    "message": "URL was not parsed due to an ODataUnrecognizedPathException. Resource not found for the segment provided in the URL."
  }
 
Screenshots below of my workflow.
 
Any help would be much appreciated, I'm new to this!

Screenshot 2024-0...

All responses (3)

Answers (1)

Suggested answer

AC-27061552-0 9 on at

Like (0)

Report

ODataUnrecognizedPathException Error - at my wits end!!

So, to solve this I did the following:

1. Check for when row is added against the email messages table name

2. Initialize a variable, in my case I called it 'caseNumber'

3. Set a condition under the following criteria:

a. Direct is equal to false (this means direction of email is incoming

b. From does not contain {mailbox domain E.G. sharedmailbox@test.com}

4. If yes, set variable caseNumber as substring (The substring finds CAS- within the email subject and grabs from 0 to 16 indexes which covers the entire case number)

5. I then list rows under cases table, selecting column incidentid with a filter of ticketnumber eq caseNumber (caseNumber being the variable from what we set in step 4).

6. I then do 2 things, I apply to each:

a. Update a row email message and set 'Regarding (Cases)' to 'incidents(Case)' - Case being the caseId of the incident we grabbed in step 5.

b. Update a row 2 - table name cases, row ID is unique case identifier and I update the status reason to the custom status reason I created relevant to my company.

End of steps (Not interested if condition is no).
Anthony Blake 2,179 Super User 2024 Season 2 on at

Like (0)

Report

ODataUnrecognizedPathException Error - at my wits end!!

Hi, could you share your solution?
Verified answer

AC-27061552-0 9 on at

Like (0)

Report

ODataUnrecognizedPathException Error - at my wits end!!

Resolved. No further input required.

ODataUnrecognizedPathException Error - at my wits end!!

Helpful resources

News and Announcements

Quick Links

December Spotlight Star - Muhammad Affan

Top 10 leaders for November!

Community AMA December 12th

Leaderboard

Featured topics

Product updates

ODataUnrecognizedPathException Error - at my wits end!!

Helpful resources

News and Announcements

Quick Links

December Spotlight Star - Muhammad Affan

Top 10 leaders for November!

Community AMA December 12th

Subscribe to

Leaderboard

Featured topics

Product updates