Simon Grieshaber

I often give the duplicate detection rule a name based on the fields or key fields sued. If one of those fields is no longer needed, then the name reflects incorrectly what's in the rule. There is no way to change the name of the rule once it's created. This would be a very nice feature to have.

Request is to increase the size of the Segment Query definition. Our customer has quite complex segment needs and when the segment editor converts the code to the query language, they often get the ‘you have exceeded the 4,000 character limit’ error. They are looking to building sub-segments and including these but wondered if they could increase the size of the query definition field to 6,000 or 8,000 characters?

Could the limit be extended or set at 4,000 and allow each installation / system to change it via a configuration setting say up to a max of 10,000 characters?

It would be great to be able to create a Booking and then set a recurrence pattern (e.g. run each week, each month etc.) If the same resources were kept by default, this and time slot details can all be amended for the recurring bookings - i.e. agent would need to very these before confirming the booking resource.

It's great that you can use Sharing to share a record between users to help with data management. However there is no way to use ta option to filter record when say creating a View (e.g. show me records I own plus all those that are shared with me.)

I understand this is baked into the security model so if you pick 'All Contacts' shared records will show - but you not want to provide the 'All' option and it would be great to have an ability to include Shared records when filtering.

It would be great to also extend that into Custom pages too so data pulled into a Collection would be able to pick up this filtering option.

Suggest the url addressable link e.g. https://

When creating a model driven app, there is a baked-in rule that means you cannot completely exclude all Business Process Flows. This feels like a very odd restriction when you can control most things about what is included in an app.

We have a need to removed this but cannot so it so had to leave one in place ta was inactive to work around this - not very nice really.

Alternatively, make it an app or system controllable rule to set it as it is right now or opt to remove the feature.

It would be really beneficial to have a way for the system to display when a table is close to its maximum limits in terms of number of fields and bytes.

There are a few tools out there that show how many columns a table has but none truly and accurately show the total size in bytes. Both are critical but the number of bytes is almost impossible to calculate accurately and the only way you know when you have reached the limit, is when you create a new field and it then tells you that you have exceeded the limit and cannot continue.

The system has its limitations, but we don’t have all the necessary tools to be able to actively monitor these.

Ideally a simple display showing the number of fields vs max number of fields plus a bar type graph showing green, amber and red to indicate how much space (in bytes) is used up (with red being close to the max etc.) Where? Either in the Power Platform Admin portal or Maker Portal.

This way we can then bring up the issue with the customer and discuss redesign, refactoring etc for any tables showing amber or red. It will provide more proactive design and discussion with our customers.