In the Playbook form there is this fancy Regarding lookup with views of the five Sales entities. Too bad, it’s just a matter of copying the activities from the Playbook template (in case Progress is not tracked) to the regarding record. Somehow the Playbook service should check whether the targeted entities are enabled for Activities, that’s all.
#Autotrash callable only on entities code#
Probably the code is not generic enough to let it all work. Looking at the plumbing of the Playbook service there are a lot of plugins involved to do the action. In OData, only declared navigation properties and declared named streams can be represented as properties without values. When I publish the Playbook template and open an Account form, the button ‘Launch playbook’ is shown.īut when I launch the playbook an error occurs:Īn error occurred while validating input parameters: : An undeclared property ‘regarding_account’ which only has property annotations in the payload but no property value was found in the payload. The Account entity and my custom entity are enabled for Activities. So would these also be available in the Playbook templates? Yes, they do. You can add extra entities to this list, including custom entities. Looking at the Playbook related entities in the Advanced Find, there is an entity called ‘Playbook Callable Contexts’ that holds the entities that are available to choose from in the Playbook template. So I wanted to find out if Playbooks can be enabled for entities other than the five Sales entities (Lead, Opportunity, Quote, Order, Invoice), even better for custom entities. Kevin Annfield did his part about Automating Dynamics 365 Playbooks. Jukka Niiranen wrote an excellent blog post about Playbooks for Dynamics 365 Activity Templates. Reading the October ’18 Release Notes I got interested in the new Playbooks functionality. Since the release is rolling out I started playing around with Playbooks.
0 kommentar(er)
