Kunal Murarka World Bank Group Solution Architect

In some business use cases it is important to the geo-location of the respondent to have better analytics on survey response. There should be an ability for respondent to block the location sharing or acknowledge the risk of location share to address privacy issue.

Offline / Mobile App capability to support various data collection scenarios to address any internet connectivity issue in the remote area.

At this point, intermediate save is automatic. Having explicit "save" button with some user friendly message will convey the message to the end user that information submitted so far will be retained and rest of the survey can be submitted at later stage. Automatic reminder on incomplete survey. This feature is important for survey with lots of questions.

At this point we can read data from survey specific entities in CDS and use Microsoft Automate to create survey invite. Having direct API Support for various forms pro survey function/capability will increase the boundary to serve various real-life use case.

Use of access team helped to optimize the number of entries in POA as compared to traditional record sharing for primary entity, however, platform still leverages the traditional sharing approach (makes multiple entries in POA) for implicit sharing scenarios. In a scenario where record level access has to be implemented and there are multiple child entities (with parental relationship) to a primary entity. Having access team enabled for child entity does not helps to optimize the POA entries. Platform having ability to leverage POA for implicit sharing would help to reduce the on going maintenance and improve the performance of the CDS / D365 platform.

There is no OOB capability to support in CDS/D365, Attribute-based access control (ABAC), typically we leverage access team and field level security to achieve the same which is effort intensive as lots of customization/testing is needed. Attribute-based access control (ABAC) requirements are very common whenever we implemented any approval workflow etc with restricted access control.

"Edit data in Excel" (Microsoft PowerApp Office Add-In available via maker portal) and "Open in Excel Online" feature allows 2 way sync via excel. Ability to restrict these features at instance and entity level will help to avoid any accidental bulk update/delete.

Category and additional custom fields are very frequently used in the case entity, ability to map additional fields will bring help to cover increased number of usecase.

D365/Dataverse/Power Platform to capture & display log in D365/office security compliance center for an unauthorized access for any Dataverse API call due to lack for security role/permission.