Skip to main content

Notifications

Announcements

Share Your Journey with Power Pages and Help Shape Its Future!
News and Announcements icon
Dynamics 365 Community / Forums / Customer Service forum / Is linkToConversation ...
Customer Service forum
Suggested answer

Is linkToConversation now broken? (JavaScript API)

(1) ShareShare
ReportReport
Posted on by DanNewton 151
 
Is anyone else suddenly encountering this failing with 400 Bad Request?

For example, even running the code via the browser console from the documentation page now returns a 400 error, despite passing a valid incident ID and a UI message appearing saying the conversation was linked successfully.

//Linking an incident record with the current conversation 
Microsoft.Omnichannel.linkToConversation("incident", "06318998-607a-ef11-ac20-002248c6bc8a").then((response) => { 
    // Refreshing the tab UI  
    Microsoft.Apm.refreshTab("tab-id-3"); 
}, (error) => { 
    console.log(error); 
});
It seems the payload (generated on the backend) is now invalid, leading to the 400 error. I've been trying to escalate this through support, but seem to be stuck with the usual frustrations around mandatory phone calls/screen share sessions causing significant delays on a ticket where the contact preference is email and issue has been clearly articulated.
 
 
Categories:
Omnichannel
  • DanNewton Profile Picture
    DanNewton 151 on at
    Is linkToConversation now broken? (JavaScript API)
    Hi @PerezAguiar - it looks like ConversationID is optional so we are only passing entity incident and incident id but getting the 400 bad request error.
     
    I just tried with Entity, RecordID and ConversationID (as below) but still get the 400 bad request:
     
    //Linking an incident record with the current conversation 
Microsoft.Omnichannel.linkToConversation("incident", "41d96efa-2f7b-ef11-ac20-0022480089c8", "52e7e8dd-df27-4936-8619-7ec97dff09c3").then((response) => { 
    // Refreshing the tab UI  
    Microsoft.Apm.refreshTab("tab-id-3"); 
}, (error) => { 
    console.log(error); 
});

    This has worked previously so I think there is a backend issue/bug - unfortunately landing that message with support and getting it escalated to the developers isn't as easy as it should be.

     
  • Suggested answer
    PerezAguiar Profile Picture
    PerezAguiar on at
    Is linkToConversation now broken? (JavaScript API)
    Hey
     
     
    Have you tried running this with the 3 parameters? Entity, RecordID and ConversationID?
     
    Regards,

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Share Your Journey with Power Pages and Help Shape Its Future!

Quick Links

Anton Venter – Community Spotlight

Kudos to our October Community Star of the month!

Announcing Our 2024 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Dynamics 365 Community Newsletter - September 2024

Check out the latest community news

more Community News

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,524 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 228,469 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans