Microsoft Dynamics 365 | Integration, Dataverse...

Uncaught Type Error: cannot read properties of undefined (reading 'set')

(3) Share

Report

Posted on by JP-23041643-0

Hi we are having an issue with microsoft dynamics whenever we log in or load the page, we receive an error message: uncaught typeerror: cannot read properties of undefined (reading 'set').

Just for quick context we have the Five9 adapter installed and the URL is coming from five9. Please see attachment for a screenshot.

Categories:

Dynamics 365 general

image (16).png

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Holly Huffman 6,530 Super User 2025 Season 2 on at

Like (0)

Report
Good morning, afternoon, or evening depending on your location!

It looks like the error is coming from the msdyn_ciLibrary.js file within the Five9 adapter integration on your Microsoft Dynamics instance. This type of error typically occurs when a script is trying to access an undefined object or property.
Possible Solutions

Check Five9 Adapter Compatibility

Ensure that the Five9 adapter version is compatible with your current Dynamics 365 environment.

If there was a recent update to either Dynamics or Five9, check for any breaking changes.

Clear Cache & Cookies

Sometimes, browser cache issues can cause JavaScript errors. Try clearing your cache and cookies, then reload the page.

Verify Script Dependencies

The error suggests that the script is trying to call .set on an undefined object.

Check if all required dependencies for msdyn_ciLibrary.js are properly loaded before execution.

Check Five9 Configuration

If the error occurs only when logging in via Five9, review the integration settings.

Ensure that the correct authentication and API endpoints are configured.

Hope this helps!

Was this reply helpful? Yes No
Suggested answer

Jonas "Jones" Melgaard 4,980 Most Valuable Professional on at

Like (0)

Report

Hi @JP-23041643-0,

What Dynamics 365 product are you working with? Sales, Customer Service etc.?

I don't see how integration settings can affect this error. Dependencies should also come from the solution provided by Five9.

My advice is to contact Five9 for advice. Maybe a recent release wave broke the adapter, we had an update a few weeks ago.

Was this reply helpful? Yes No