Ariest Dibya

There's a bell/chime icon on the left of settings icon on the menu bar. It's present in both on prem and on cloud but there's not a single way to utilize it for our purpose (I've searched everywhere, it's believed it's used only for "marketing purpose" from Microsoft).

Is there any plan to give BC (both cloud and on prem) so that "notification" can be fully repurpose to our needs instead giving a misleading idea, especially to our customers, that BC somehow supports notification similar to social media like notification (since that bell/chime icon cannot be hidden)?

Fyi, the power platform model driven app has provided that notification feature here

https://learn.microsoft.com/en-us/power-apps/developer/model-driven-apps/clientapi/send-in-app-notifications?tabs=clientapi

Hopefully BC will have something similar in the future.

Hi,

We have setup several codeunits as job queue, but as the codeunit name itself follow patterns like _, it is quite confusing for users even for admins. We do put the codeunit's description but name and description are in different column in job queue.

I notice codeunit does not have caption unlike any other objects (table, pages, etc.). Why is that?

May we have a caption in codeunit so any object that lookup to it may read its caption instead of its original name?

Thank you.

Hi,

We've been researching to create custom control add ins. However, during research, we found something that limit many the control add ins features and visibility.

First is the iframe and html body that hosts the control add in is by default hiding the scroll both horizontally and vertically. Please add a config in the control add in to specify whether the scroll will be shown or not. 

For iframe, the config should translate "scrolling" attribute to "yes" or "no" AND for the body, the config should translate "overflow" attribute to "hidden" or "scroll", they should be based on the config. 

The solution is: maybe inside the control add ins can be added something like this

controladdin DemoControl

{

  AllowScroll = true;

}

Second, the default placement of script inside control add ins is always before the body. Due to how some Javascript library works, sometime it's necessary to put the script tag AFTER the body because some of those library manipulate the document.body. document.body will be null if the scripts are runs before the body itself.

https://www.helpfulbean.com/article/javascript_document_body_null

The solution is: maybe inside the control add ins, script can be configured to a something like this

controladdin DemoControl

{

  Scripts = { placement: 'before', 'script1.js' }

      , { placement: 'after', 'script2.js' }

}

Hopefully those two features can be implemented someday.

Thank you for the attention.

Hi,

I know the form design from Dynamics NAV and continued to BC always consists of fasttabs that can be collapsed and expanded. However, after some feedbacks from users, this design somehow is quite uncomfortable since it requires them to scroll and scroll when a form has a lot of fasttabs (and of course fields).

In model driven app, fasttabs are represented by tab instead. Of course the more tabs it has, eventually at the rightest part, those tabs will be grouped into a dropdown. This is quite desirable experiences to them, instead of fasttabs which requires them to scroll down to find it, they love to navigate through tabs which stretch from far left to fat right.

Is there any plan for BC to have tabs similar to model driven app in other Dynamics 365 product? At least the dropdown to select tabs in the right corner of form if stretching tabs from left to right is not possible?