Ritika Indrakumar

We have a very specific business need which requires that some of the fields on subset of contact records need to be hidden from most of the users and available to a subset of them.

We want around 5-6 fields of the around 100 contacts from the contact entity to be to be hidden from almost all the users while it should be available for the super managers.

These fields must be visible for the other contacts records except the 100 records to all the users.

We want to make visible a specific sitemap of our main app only for specific people in my organization by configuring entity privileges. We have attempted to restrict visibility to a specific subarea on the sitemap of our main app by configuring entity privileges.

The subarea we are trying to hide is the standard "Quote Product" (quotedetail) table. 

We created a new table named "Sitemap Organization Privileges" and created a security role with privilege "create" for that table.

Then we assigned this security role to the user who has to see the subarea and added the table in the Properties of the specific subarea in the sitemap.

Unfortunately the subarea remains visible for everyone.

The ask here is to hide a single entity from the sitemap for certain users and make it visible only for users with Sales management (group)security role.

While creating an appointment with Dateonly field from 4/10/25 to 4/20/25, the calendar should display the entire appointment period.

As of now, the end date’s time is set to 12:00 AM. As a result, the calendar interprets it as the end of the previous day and displays the appointment by one day short.

The workaround provided by the product team is to add the dateandtime field.

The proposed approach is to ensure that appointments that are created using DateOnly fields should display the entire appointment period—without factoring in the default 12:00 AM time setting.

 We’ve observed that the online portal has a character limit of 600 for a specific field. However, when attempting to paste content exceeding this limit, the field remains empty and no data is pasted. In contrast, if the content is under 600 characters, it is pasted successfully. Additionally, manually typing into the field works regardless of the character count.

When content of up to 600 characters is pasted into the field, we expect the first 600 characters to be accepted. A message should then appear indicating that the maximum character limit has been reached.

For custom entities and it was a permissions thing, admin users can toggle on/off for toast notifications but users didn't have correct permissions to do it.

Going forward I think D365 need to have a window popup providing a warning saying permissions not granted or something just to give admin users a message.

When the test user attempts to reply to an email which contains a contact record from a higher or cross Business Unit, there should be a warning or indication highlighting the specific contact. Ideally, the contact should either appear greyed out or display only the email address—similar to how it behaves in Outlook.

Suppose there are 10 contact records in the 'To' field of an email, and the user does not have access to one of them. In such cases, it does not allow the user to reply to the email. Users often find it difficult to identify which specific contact is causing the issue, and it takes considerable time to pinpoint the problematic record. Therefore, providing an indication—such as greying out the inaccessible contact while replying—would significantly enhance the user experience.