Can we default notifications (setFormNotification) to expand

(0) Share

Report

Posted on by Community Member

Hi,

The notifications on a CRM form is important to us.

Sometime there are 4 notifications (Warnings), but they are all collapsed. Once the user clicks on the notification at the top, they expand and all 4 are visible. Below is the code we use:

ClientApi.FormContext(executionContext).ui.setFormNotification("This record requires a mobile number", "WARNING", "new_mobile_notification");

Is there a way to write some OnLoad jScript that will default the notifications to be expanded, instead of being collapsed. We don't want the users to miss out on the important warnings.

Many thanks,

gideon

I have the same question (0)

All responses (4)

Answers (2)

Verified answer

meelamri 13,216 User Group Leader on at

Like (0)

Report

Hi gideon,

Unfortunately, this is not possible.

Good Luck !

Was this reply helpful? Yes No
Verified answer

Timothy Bohte 44 on at

Like (0)

Report

Hi Gideon,

I'm afraid that's not possible. Microsoft changed those notifications since version 9 to be less intrusive. You need to think workarounds here.

You could change the notification type from Warning to Error or change this field mandatory by JavaScript. Then the user can't save the record and in the last case it will show an error also besides the field as well.

Another workaround is creating your own pop up window. Find more info from Microsoft here: docs.microsoft.com/.../openWebResource

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Mehdi & Timothy,

Thank you very much for your responses and confirming my doubts. I might have to look at workaround.

Many thanks,

gideon

Was this reply helpful? Yes No
Suggested answer

jork 12 on at

Like (1)

Report
Hi Gideon,

I did find one VERY unsupported approach to auto-expanding setFormNotification notifications. You can override the Xrm.Page.ui.setFormNotification function to do some additional DOM manipulation after an alert is called. The below example currently works in a sandbox environment I have access to. The element selectors can probably be fiddled with, but can also hypothetically change whenever Microsoft makes changes:

// Override Xrm.Page.ui.setFormNotification Xrm.Page.ui.setFormNotification = (function () { var cached_function = Xrm.Page.ui.setFormNotification; return function () { var result = cached_function.apply(this, arguments); // use .apply() to call it setTimeout(function () { var notificationWrapperMessage = parent.document.querySelector("[data-id='notificationWrapper_message']"); if (notificationWrapperMessage !== undefined && notificationWrapperMessage !== null) { var notificationWrappers = parent.document.querySelectorAll("[data-id='notificationWrapper']"); if (notificationWrappers !== undefined && notificationWrappers !== null) { var expandBanner = false; for (var i = 0; i < notificationWrappers.length; i ) { var ariaExpanded = notificationWrappers[i].getAttribute('aria-expanded'); if (ariaExpanded !== undefined && ariaExpanded !== null && ariaExpanded === "false") { expandBanner = true; } } if (expandBanner) { notificationWrapperMessage.click(); } } } }, 100); return result; }; })();

One additional note: setTimeout is being utilized so that the DOM manipulation happens AFTER the notification is generated. Hope this is helpful to someone out there.

Was this reply helpful? Yes No