Manuel Ruiz Molina

Good evening, My tarjet is to create an incident on the correct element by selecting their Elements like an Hierarchical view. On Html I have seen the function: MscrmControls.HierarchyControl.HierarchyControl-leftPaneContainer I would like to Enable this Control on Portals

I suggest to include those three entities on the entities available to be Selected on the Workflows. Now JS and Flows (both together) are needed for updating each of these entities when a customized related registry is triggered with the OOB Workflows Trigger available. This is causing our Customers many differents issues regarding the time that the Flows takes to be executed while the registry card is still opened by the user.

I suggest to record all stages changes from a Business Process Flow on a "new entity" to store the actual start, actual end, duration, stage and Regarding to the main registry on the BPF Table. It something that many Customers had asked me to customize and I'm sure It should be great to improve the OOB Solutions so we could use future improvements. Till 2020 there exists some other fields (Stage ID, Process ID, Traversed Path) that now are deprecated without any other solution to replace it.

On CRM Connection Setup (5330) add a bolean Attribute to select the integration Order for the Quote Lines. On Dynamics 365 a report using Word Templates could be sorted by Sequence Number or by Creation Date and It should by asked MS to apply that change on the environment. - On normal scenarios the creation and the sequence number are correlative (item 1, created at 00:01, sequence number 0; tem 2, created at 00:02, sequence number 1 ...). But on Word Templates the sort by option only allows to use creation date on ascending order OR sequence number on descending order. On BC the creation sales lines are created following the sequence number on ascending order so, if you select on Dynamics the option to sort using Sequence Number, you get the lines in inverse order. This has been told to Dynamics Team 20 weeks ago (120090724005295) and they are trying to resolve it but has no timeline. I suggest to add this workaround directly on BC so if you need to use the Sequence Number option on Dynamics 365 the creation Sales Lines on BC should be done using sequence number on descending and if you select the Creation Date option on Dynamics 365 the creation Sales Lines on BC should be done using sequence number on ascending (the standard).

On the ActivityMimeAttachment table enable the selection of the attachments that should be saved on Sharepoint. The amount and variety of the attachments on the actual emails force to select which attachment should be saved and which not. To enable this selection let's create a new bolean field. With this new option the Developers could create Flows that could save the fields to the selected Sharepoint Folders.

Please enable the translation capability on any entity like It's available on Product. Notice that this is one of the most common issue relative to translation. It's not easy to use translation and If we don't allow the customer to use the basic functionality on all entities we will be on troubles. I already know there exists an API to use translation, but customers often needs to use word templates, and we are not allowing them to use translations on them.

Create a configuration Tab on Advanced Configuration to enable/disable common configurations that should be used by Business Central Integration Team on the integration coding. e.g. the sort by order selected on Dynamics 365 used to print the Sales Quotes on the Forms and the Word Templates (that affects dramatically on how the lines are created on BC, inverse order) e.g. the button visibility on Sales Professional (the standard Active Button, from Sales Hub Solution, or the Active Button from Sales Professional Solution) e.g. the button visibility on Sales Professional (the Sales Order Creation button, from Sales Hub Solution, that is needed to send the Sales Order to BC) e.g. values from Contact (Contact Type) or Account standard Choices to be add easily to Business Central without the need of creating an extension each time a new choice value is added on Dynamics 365

Hello, When a Service Contract is created from a Quote Service Contract, the Service Contract is created as Signed. I'm reading carefully this doc (https://docs.microsoft.com/en-us/dynamics365/business-central/service-how-to-create-service-contracts-and-service-contract-quotes). I suggest two things: - As we are managing Service Contract Quotes I suggest adding on the Service Contract Configuration a Series Number Loockup like It's available on Service Quote - As It's needed to change the Numeric Series (Quotes are not the same as Contracts), I suggest adding on the Service Contract Configuration the possibility to change this functionality: "a service contract is created with the status Signed". So we could change the Service Contract Number before signing. So it should be enabled not to create as signed mandatorily.

Add the msdyn_taxcode and msdyn_taxcodedetail on all Out-Of-Box Solutions. The Tax Codes are not included on Sales Hub not on Sales Professional. Taxes should be necessary on Sales App as on FieldService App (on this App both entities are available)