Akira Homma

Using the following API, we can create PDFs in SSRS and download them to local PC.

/Reserved.ReporViewerWebControl.axd

If there was a way to save this in the Annotation table instead of on the local PC, the range of options would expand and we could expect further business deployment.

Data displayed on view as a mobile app is shown as card form when the screen size is small.

Currently, displaying customized card form is doable only on deprecated legacy read-only control. 

However, Power Apps Grid Control cannot display customized card form.

Customized card form can display many columns and can sort columns.

It would be much more convenient if Power Apps Grid Control could display customized card form, because legacy read-only control can display it.

In Real‑Time Marketing (RTM) segments, marketers often need to include Parent contacts when a linked Child contact (connected by a Connection role such as Guardian) meets a condition on a related custom table (e.g., an EnrollmentDate fits within the current academic year).

Please allow the segment builder to follow the relation chain Parent Contact → Connection (role) → Child Contact → Custom table and include the Parent when such a Child exists that satisfies the rule.

It would be useful when users set complicated conditions in a segment on RTM segments. 

This unlocks common parent/guardian and household scenarios without redesigning data.

In Real‑Time Marketing (RTM) segments, marketers often need to include Parent contacts when a linked Child contact (connected by a Connection role such as Guardian) meets a condition on a related custom table to Child contact (e.g., an EnrollmentDate fits within the current academic year in custom table related to a Child Contact record).

Please allow the segment builder to follow the relation chain Parent Contact → Connection (role) → Child Contact → Custom table and include the Parent when such a Child exists that satisfies the rule.

It would be useful when users set complicated conditions in a segment on RTM segments. 

This unlocks common parent/guardian and household scenarios without redesigning data.

Currently, there is no way to completely disable Allow Range Selection for users in model-driven apps.

The default Read Only Grid always has "Allow Range Selection" enabled (Yes), and its properties cannot be changed.

Even if we add a "Power Apps Grid Control" and set Allow Range Selection to No, users can still switch back to the default grid using the "Show As" option, which re-enables range selection on a grid.

This makes it impossible to meet security/compliance requirements where multi-row selection must be disabled.

Using classic grid might be a workaround, but this legacy grid is going to be deprecated in the future.

Please provide a supported way to:

・Change Allow Range Selection for the default grid.

・Prevent users from switching back to the default grid via Show As.