Relationship Filters, not just Lookup Filters
Currently, customizers can add filters to lookups, which restrict selectable values. This can be done in the form definition itself, by using the "Related Records Filtering" section, or in Client Side Scripting, by using addCustomFilter. The problem is that these filters are form specific and on...
Auto Numbered fields should be read-only, and not required.
If you change a string field to use an Auto-Number format, the field is set to Read-Only, and Requiredness is ignored on any form in the Classic UI. However, in the Unified Interface, the field remains editable, and if you try to save the record without supplying a value, and the field is requir...
Multiple Form Notifications with the same ID
Right now, we have two methods to interact with form notifications; SetFormNotification and ClearFormNotification. ClearFormNotification requires that a Unique ID be specified in the call to SetFormNotification. If you call SetFormNotification a second time with the same ID, the existing notifica...
Allow sorting Views based on sort order of Option Set Values.
Currently, when sorting a view based on an Option Set column, the view will sort based on the alphabetical order of the Label of the Option Set Values. However, there are occasions when the values of an Option Set represent a sequence that have a meaningful order, independent of their alphabetic...
Allow creating a blank record via the WebApi in the UCI.
There seems to be an explicit restriction in the UCI that doesn't allow the creation of a blank record. If you run this code in the classic interface: const data = {}; Xrm.WebApi.createRecord(targetType, data).then(...); The appropriate record will be created as expected. However, the same co...
Actions in Form Notifications
I'd like the ability to add actions to form alerts.
Add isUci method to supported Client Side API.
There exists a method, "Xrm.Internal.isUci()" which determines whether the code is running in the UCI or the classic interface. However, using methods in the Internal namespace is not supported. Please add this method to the supported Client Side API.