Power Apps Ideas

D365Ideas_Admin · ‎02-04-2019

When will the Developer Toolkit be available for CRM 2015/Visual Studio 2013?

D365Ideas_Admin · ‎02-04-2019

Workflows are triggered by events (create, update, assign etc), however in many cases the ability to schedule workflows on a periodic basis is also required. CRM already has a scheduling engine, used for many system processes, as well as some user-defined processes such as Bulk Record Deletion. Why can't we open this up for schduling workflow? In addition, we could make this available to schedule plug-ins as well, providing total flexibility for developers.

D365Ideas_Admin · ‎02-04-2019

I have several times needed to set few values at run-time (like I can with a dialog process) - and then execute that against multiple 'targets' (like I can with a workflow.) The current limitation of a Dialog Process means that I can only run it against a single record - if I need to run against multiple records, I need to create a workflow and then it isn't flexible.

Pershadtech · ‎12-07-2019

While developing one of my Power Virtual Agent I feel there are many questions which needs lot of efforts from our side so as to get the users right answer. But i remember same questions were answered with in seconds by Power BI when asked in its Q&A section. Why can't we link the Power BI Q&A inside Power VA so that we can save whole lot of time in creating exact answers for users. Just a thought. Regards Ashok

D365Ideas_Admin · ‎02-04-2019

It is not currently possible to move a stage or a step in the workflow designer. It would be useful to be able to move a stage or a step in your Workflow. For example, your business logic has changed or you might just want to update the order of the execution steps/stages. I would like to click on a step, drag it and drop it elsewhere in my Workflow and click save instead of recreating that step and deleting the older one. I guess one of the workaround (never tried it before) would be to manually change the XML of that Worfklow, but it would then require a "skilled" developer. This is not necessary something that your customer can easily do.

D365Ideas_Admin · ‎02-04-2019

Workflow cannot currently update fields that are set to disabled on a form. The workaround is to add script to set the field to be disabled so workflow may update it. As a customiser, I'm tired of having to do this and it also increases the performance overhead when loading a form. I don't see the point of restricting workflow update steps from updating read only fields. Pretty please, enable this and save all the customisers out there some precious time.

D365Ideas_Admin · ‎02-04-2019

CRM 2013 has a new process type called Action, that is meant to encapsulate complex business logic into a process that is triggered on non-CRUD mechanisms. Actions can be associated to a specific entity, but can also be defined as global. Actions can be triggered through the web service SDK and client SDK, but they cannot be triggered by other workflows or actions. This limits the value of actions because they cannot be implemented in the middle of other business processes defined in workflows. Workflows and Actions should be able to call other actions, in the same way that workflows can call other workflows. With this new capability, Actions would become incredibly useful.

D365Ideas_Admin · ‎02-04-2019

The Plug-in Trace Log stores timestamps such as PerformanceExecutionStartTime as datetime fields, but milliseconds is always 0. To be able to make correct analysis of execution sequences, these fields need to include milliseconds, as it is now impossible to know in which order plugins were actually executed.

dpardpar · ‎02-04-2019

It'd be great to be able to use Business Rules and Workflows with Multi-select Option Sets. The ability with Business Rules to show/hide, make required field or not, etc. would be great. As well, with Workflows being able to set a value with a Multi-select Option Set would be great.

D365Ideas_Admin · ‎02-04-2019

Using the ITracingService only works for plug-ins registered in SandBox. Since this service is so much better/easier to use than e.g. logging to file on the server, this should be enabled also when using plug-ins not registered in isolation.

DavidYack · ‎02-04-2019

Visual Studio has now been released please update the Dynamics 365 Developer Tools to work with the current version

D365Ideas_Admin · ‎02-04-2019

The CRM 2011 Developer toolkit should allow a user to right click and deploy a single project or file instead of the whole solution. This affects multiple developers working on the same solution.

mashup · ‎12-03-2019

Hello, I have an app where I want to use Flow which gets data from a REST API service secured by Azure AD. Everything worked flawlessly when I set everything up and tested myself. However, when I shared it with a new user, they were met with the following connection screen when launching the app: It's not very user friendly to ask end user these kind of parameters just so that they can establish connection with an API. I had filled in these credentials when I added this connector my app. It would be great if there would be a possibility to store the credentials when adding this connector to your app without the need to re-enter them for any new user. Some of the community threads that express having this problem: https://powerusers.microsoft.com/t5/General-Power-Automate/Using-quot-Http-with-Azure-AD-quot-How-to-pre-populate-quot/m-p/246728 https://powerusers.microsoft.com/t5/Building-Power-Apps-Formerly/How-to-bypass-the-prompt-for-Base-Resource-URL-for-PowerApp/td-p/315234 https://powerusers.microsoft.com/t5/Building-Power-Apps-Formerly/Connector-quot-HTTP-with-Azure-AD-quot-asks-credientals-for-end/m-p/414460

D365Ideas_Admin · ‎02-04-2019

I would like to see an option where individual views can have a colour coding option associated with them (say in properties) based on the status reason code. The option should allow each status reason code to have a colur associated with it. When the view is displayed the background colour of each row would be based on the status reason code. Another way of doing this could be to add a colour option to the attribute and have an option in the view to turn colour control on or off. This will allow for a simple visual way of identifying sets of data which need dealing with in a prioritised way. ie you can have a single view with all outstanding actions say red at the top followed by amber etc...

D365Ideas_Admin · ‎02-04-2019

Rescheduling the common asynchronous service (scalegroup) maintenance jobs is imperative to maintaining a high-performing environment. These jobs include: DeletionService(14), IndexingManagement(15), ReindexAll(30), CleanupInactiveWorkflowAssemblies(31), AuditPartitionCreation(41), CheckForLanguagePackUpdates(42), RefreshRowCountSnapshots(46), RefreshReadSharingSnapshots(47). Currently, these jobs are rescheduled via a community tool provided by Premier Field Engineering that uses an internal/unsupported approach. This tool was originally provided for CRM 4.0 and was updated for CRM 2011. http://crmjobeditor.codeplex.com/ The DeploymentService and associated SDK should be extended to provide API's for scheduling or disabling the common maintenance jobs. PowerShell cmdlets for invoking these API's should also be provided.

D365Ideas_Admin · ‎02-04-2019

Allow us to run a workflow with a run option of "Run on all records in all pages" (i.e. allow workflow to run on more than 250 results at a time in an Advanced Find). Otherwise it takes a long time to go through 10,000 records. We could do an export to Excel and update that way, but sometimes running a Workflow is the best way to do it.

D365Ideas_Admin · ‎02-04-2019

The REST service currently only supports access to data using the schema names of entities/fields. It would be great if logical mapping support was added to the service so that the logical names of entities and fields could be used instead. This is much simpler to deal with when working with the REST service from JScript and would make it easier to transition back and forth between the REST and SOAP endpoints if needed.

D365Ideas_Admin · ‎02-04-2019

The concept of workflows is great, but their capabilities are somewhat limited. The following functionality would greatly enhance their usability and reduce the dependence on plugins for even very basic actions: 1. Ability to run workflows synchronously. 2. Ability to run workflows in scheduled intervals (e.g. every night). 2. Ability to identify the user who runs the workflow. 3. Ability to access and manipulate child records (for-each loop functionality). 4. Ability to share record with users. 5. Ability to delete records.

D365Ideas_Admin · ‎02-04-2019

Thank you for your feedback. This is a great suggestion! We are considering this in our roadmap. Sincerely, Srikumar Nair PM, Microsoft

D365Ideas_Admin · ‎02-04-2019

The Plug-in Trace Log attribute Message has a MaxLength of 1073741823 bytes, and the underlying field in the database is of type nvarchar(max). Still the message block is truncated by code to only show the last 10k characters. The truncation is not documented anywhere in the SDK, but in the code it is motivated with comment: // do not let trace buffer get too large - keep most recent entries This constraint limits investigation and debugging of complex plugins, and should be configurable with the system settings where you activate the Plug-in Trace Log.

Share your ideas and vote for future features

Dynamics CRM Developer Toolkit for CRM 2015/Visual Studio 2013

Schedulable Workflows & Plug-Ins

"Diaflows" Allow a Dialog Process to target multiple records in a view. (Like a workflow process)

Integrate Power BI Q&A with Power Virtual Agent

Modify the Workflow Designer to move steps and stages

Enhance Workflow so it may update disabled fields

Allow workflows and actions to call actions

Store milliseconds in Plug-in Trace Log

Multi-select Option Sets Availability with Business Rules and Workflows

Write to the Plug-in Trace Log from assemblies outside SandBox

Dev Toolkit support for Visual Studio 2017

CRM 2011 Developer toolkit single project or file deploy

Prevent "HTTP with Azure AD" connector from asking end user connection parameters

Colour code views based on status reason (conditional formatting)

Extend Deployment Service/SDK to Provide API's for Managing Common Async Maintenance Jobs

Ability to run Workflows based on Advanced Find

Add option for logical mapping to REST service

Improve Workflows

Copy & Paste in WF Designer

Define Plug-in Trace Log message size

Helpful resources

Ability to Map the new "user role" to office 365 o...

Share an app with an office 365 group

Share PowerApps with Office 365 Groups

Spell Check

Formula bar auto-select active property when click...