Akira Honma (Japan Concentrix KK)

Currently, according to the public information below, there's a limitation for users to create rollup fields.

Title: Rollup column considerations

URL: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/define-rollup-fields#rollup-column-considerations

Depending on customer's business operation, they would like to have more than 10 rollup fields in one table.

It would be much better for users if limitation could be off or the number of limitation could change regarding rollup fields.

Currently, the changed values are not synced to Power Platform organizations when changing email on Microsoft 365 Admin Center or Azure Portal except first time.

In terms of managing emails in bulk, always syncing would be desirable.

It would be much better if we could sync the email values on Microsoft 365 Admin Center or Azure Portal to Power Platform organizations all the time.

After 2022 Release Wave 2, Teams user presence is unintentionally displayed.

Currently, there is no settings to turn off this function.

Not all users are using Teams license, so this presence is sometimes disturbing and confusing users.

Users frequently see this user presence, some customers think this presence is displayed too many times.

Knowing on and off regarding user presence is not always beneficial.

Also, adding new features to table view made load performance low.

It would be much better if admins can turn off this Teams user presence feature.

On current behavior regarding user record, all records have user icon at the top of record name.

There is no way to hide these icons so far.

This user icon display may cause unnecessary loading or delay.

Sometimes it is difficult to see the UI, so it would be great for some users to hide these user icons.

It would be much better if these user icons could be hidden on Power Platform admin center or table (entity) settings.

Currently, when uploading attachment file with Post on Timeline, it causes an error if the file name has Japanese name.

The error does not occur if the file name is consisted of English name and numbers, but this restriction sometimes makes users difficult to instantly see file names.

It would be great if Japanese file name, other than English and numbers, could be uploaded with Post on Timeline.

On Project Operations, when the org is configured with Dual-Write, sometimes unintentional price list is set to the field (PriceLevelId) on creating quote records.

This behavior stems from that the PriceLevelId field is automatically set by default onload JS depending on SQL GUID sort scheme, so sometimes not expected price list is set to the PriceLevelId field.

The record which is set to this lookup field can be manually changed, but it takes some steps, and it is laborious.

Also, when unintentional record is set to this PriceLevelId field, it took sometimes to notice the wrong record is set on this so it makes difficult for managing quote records.

It would be great if customers could set the price list record for the PriceLevelId before creating quote records.

It would be also convenient if users could know which price list record is set in advance before newly creating quote records. 

Currently, total amount field value would change even though after activating quote records and make them read-only.

The total amount field after getting read-only would change when importing or changing the values from sub-grid.

It would be more convenient if we could lock the field values because admins get confused when the total amount values change unintentionally.

Currently, when it takes some time to query records on like both quick find and filtering, SQL timeout error occurs if there are so many records.

This is by design, but there is no explicit description on public information regarding this behavior.

This information could be useful when facing this issue.

Without this information, users cannot judge this behavior is expected or not.

It would be great if explicit information regarding SQL timeout error when querying records on like both quick find and filtering.

Currently, users need to do register JavaScript to each form one by one.

Thus, it takes some time to manually register JavaScript when a lot of JavaScript needs to be registered.

Users sometimes register same JavaScript to multiple table forms with same conditions and trigger.

It would be great if users could register JavaScript to multiple table forms in bulk.

Currently, the display of records on grids changes depending on both the screen size and zoom %.

It's good for many users, but some users would like to fix the display, such as how many rows are displayed and not having record initial icon.

There is no feature so far regarding fixing the display.

It would be useful for administrators if the display could be fixed like above.