Wakako Watanabe

This Ideas is related to the following Microsoft Ideas:

https://experience.dynamics.com/ideas/idea/?ideaid=20dee30e-8d9c-ed11-9ac4-0003ff45ac2b

*Assumptions: User from tenant B is a guest user in tenant A and access the BC environment in tenant A.

In case of teams integration

When a guest user opens any table record from the Sales Hub app and initiates a Teams chat, the contact can only see users from his/her tenant.

We have confirmed in the MS doc below that this is by design.

https://learn.microsoft.com/en-us/microsoftteams/trusted-organizations-external-meetings-chat?tabs=organization-settings#manage-chat-with-external-teams-users-not-managed-by-an-organization

However, this is very inconvenient for the end user.

If this feature is implemented, it will make Teams integration more convenient.

Currently, if we want to give the same security role to users belonging to a security group, there are only the following methods.

These are not efficient in terms of operation.

 - The system administrator manually grants security roles to users.

 - Create an Azure AD group with security roles and add users to that group.

 - Use XrmToolBox to give security roles to all users at once.

If this feature is implemented, we think it will make Dynamics 365 more convenient to use security groups and security roles more conveniently.

Currently, the only addresses that can be specified for email notifications in Duplicate detection jobs are the UPNs of users registered in that environment.

Some end-users want to specify external group email addresses.

Implementing this feature will make Duplicate detection jobs more convenient.

Currently, when duplicate detection rules are applied, it is the owner who created the duplicate record who can decide whether to merge or ignore the record.

However, some end-users want this action to be the Owner who created the record before it was duplicated.

Duplicate detection rules would be more useful with the feature to select owners who can act on duplicate detection rules.

Currently, "Child Items Parent Id" property pulldown "Bind to a value on a field" in Power Apps Grid currently only supports Lookup fields with N:1 relationship.

However, depending on the operation, we want to use N:1 or N:N relationships.

Once this feature is implemented, we will be able to use Dynamics 365 and Power Apps more conveniently.

If we place a date column on a Marketing form, a calendar will pop up when we enter a record.

We think having the feature to customize the dates that can be selected on, this calendar would make the use of Marketing forms more convenient.

Example: User can only select dates that are within 5 business days and within 2 weeks of the system date, excluding weekends and holidays.

Currently, the following system phonetic name (in Japanese: furigana) fields are not available in Marketing Forms.

Schema Name:

yomifullname

yomimiddlename

yomilastname

yomifirstname 

The MS doc states that some system fields are not available on the Marketing form, so it seems that system furigana field is the target.

https://learn.microsoft.com/en-us/dynamics365/customer-insights/journeys/real-time-marketing-form-create

---------------------------------

Some system fields may be hidden, as they can't be used in the form. 

---------------------------------

It is possible to use a phonetic name field on a Marketing form by creating custom phonetic name fields in the Contact and Lead tables.

However, this requires more effort on the part of the user.

We think that the feature to use the system's phonetic name fields on Marketing Forms, it will make Dynamics 365 more convenient and efficient tool for users in Kanji regions, including Japan.