For anyone else encountering this error, here's a similar post in the forum that I found. My issue was indeed our Content Security Policy configuration and not a Radzen issue.
For anyone else encountering this error, here's a similar post in the forum that I found. My issue was indeed our Content Security Policy configuration and not a Radzen issue.