Power App Grid control to support Business rule logic and lookup prefiltering

The current implementation of IP Cookie Binding is VERY disruptive to end users. There are a number of activities normal users take that will trigger the IP Cookie Binding workflow. When this happens the user experience is intrusive and disruptive. It forces a user to log out and in some cases shows a "classic" error message that "scares" the user. In other cases we have found users end up in a loop of logins.

We have opened a Ticket and the result was the current experience is by design. Below are some specific things we would like to see:

1. The user doesn't need to sign back in. If they have a valid session, simply clear the old cookie and create a new one.
2. If the user needs to sign back in they do not receive a classic error message.
3. The warning the user gets is helpful to the end user to understand why they might have received the message.

There is a bug in dataverse when configuring option sets to allow for multiple selection. TLDR: a simple semicolon will break your field!

Currently:

• I (a system administrator) can add a semicolon character in the label for an option set value.
• I can save/ publish the option set field and add it to a form in my application.
• When a user interacts with the option set in the application, they are unable to select the value with the semicolon in the label.

As an application user, it is unclear to me why I cannot select this value. As a system administrator, it is similarly unclear to me what I did wrong in configuring this field. After opening a support ticket, Microsoft confirmed that they can reproduce the issue but that it is operating by design.

Request:

• A user can not add a semicolon to an option set value label and is presented with a helpful error message if they do.
• A user is prevented from save/ publish of the option set if a semicolon is included in a label.
• The character restrictions of option set labels are published on Microsoft's publicly available documentation.

so that we don't always have to use the Finance and Operations AxDB table for PowerBi reports. We would like to have the AxDB tables available in the Azure Synapse Link.

Issue - On Change event is not triggering when a multi-select field is updated on the portal

Navigations :

Access portal Management

Go to Advanced forms

Fill advanced form steps Let say (1,2,3,4,5). From customer JQuery we add advanced form steps

Access portal and when the multi select data type field, based on option value which should shows as hide.

Copilot result for the Ask - The issue with the OnChange event not triggering when a multi-select field is updated on the portal can be due to various factors such as code bugs, event handling configurations, or specific behavior of the multi-select field in the portal environment. To troubleshoot this problem, it is essential to review the event handling logic for the multi-select field, ensure that the OnChange event is correctly configured for multi-select fields, and consider any specific limitations or requirements for triggering events on multi-select fields in the portal environment. Additionally, checking for any known issues or limitations related to multi-select fields and event triggers in the relevant documentation can provide insights into resolving this issue effectively.

Ask : is this possible way ?

Enable dynamic retrieval of IP lists and provide an improved interface for managing them. Currently, all IP addresses that need to be restricted must be entered into a small text box, which is inefficient. Additionnaly, the feature should allow for the inclusion of service tags for better organization and management.

After introducing New Look in Dynamics 365 sales and case management, the "New Look" enabled Case Type filed value and case priority filed value is break down into multiple row. if it does not fit width of the drop down which creates confusion to the user that the value in the drop down showing as two rows for single value. In the "Old Look" value for the case type field is not break down into multiple rows even the field value length is more than the drop down width. Our customer is not happy about this design changes, we are suggesting to change the design of "New Look" dropdown's for case type and case priority as same as "Old Look".

Currently GUID is displaying under "Top Workflows by Failures" section. Instead, it should display the system job name.

Currently, if there are any in-progress solution imports, we get an error and cannot start another import. Instead, Users should have the option to import the solutions anytime without any failures and the solutions should be imported sequentially and asynchronously.

This will avoid failures in ADO pipeline automated deployments. Also, we don't have to set a maximum duration for solution import as even with the same solution, the import time varies in the same instance or different environments.

Currently the dataverse connector allows makers to perform actions in different dataverses to the one they are building an app/flow in, as long as they have a security role in that dataverse environment. This can introduce risk, as often environments have additional user facing controls in place, and users being able to create their own apps/flows to directly interact with dataverse can bypass these.

We need a control to prevent app/flow makers from interacting with dataverses other than the one in the current environment.