web
You’re offline. This is a read only version of the page.
close
  • Option to attach documents on Opportunity Card, Service Order, and Service Quote

    Currently, the only options from those pages are to attach link with a description, or notes, and I believe it would be a great implementation to also add the option to attach documents in the Opportunity Card, Service Order, and Service Quote, as the functionality already exists for other parts of Business Central such as Sales Order, Sales Invoices, and more.
  • Automates the execution of an import process of multiple txt files

    I believe it would be a useful for our customers to implement a feature that automates the execution of an import process of multiple txt files that they leave in shared paths of a local server or SharePoint, without the intervention of a user, via project queue.


  • Business Central feature to do batch insertions of journals lines into one journal, using the API.

    I believe it would be a great addition to our Business Central product if there is a feature to do batch insertions of journals lines into one journal, using the API.


    Additionally, it would be beneficial to include all the quirks and features as well as limitations to the above in our official Microsoft doc articles once implemented.

  • Server side printing (Schedule A Report feature) to be allowed for SaaS deployment.

    I believe it would be a great improvement if we enable server side printing (Schedule A Report feature) in a SaaS deployment, as this is currently a limitation of our product, and our partners have expressed their opinions for the implementation for this subject.

    PRINTING options using 16.x Web Client - Dynamics 365 Business Central Forum Community Forum

  • Increasing our Modification Changes Limit for Triggering Flows

    As there was an incident in relation to triggering flows and its limitation being around 100 changes within 30 seconds, I believe it would be a great addition to our product to increase the limitation in a future build of our product, in order to provide more headroom and assist our partners, and their customers to operate their businesses more sufficiently.



  • Locking in Job Queue entry when sending Records to Dataverse functionality development

    A partner has experienced a locking issues of Job Queue Entry table when sending Records to Dataverse. Sometimes the "Integration Table Mapping" table is locked and sometimes the "Job Queue Entry" table is locked.


    Upon further investigation they have shared that this is due to a recursive call of processes and that these will never end in an endless loop but can end in a deadlock such in their case.


    This is the callstack of the error:

    AL ErrorCode:NDBCS:Deadlock Connection type:Background Message: Message not shown because the NavBaseException constructor was used without privacy classification StackTrace: 

    "Job Queue Entry"(Table 472).DeleteTasks line 2 - Base Application by Microsoft 

    "CRM Int. Table. Subscriber"(CodeUnit 5341).OnAfterDeleteIntegrationTableMapping line 10 - Base Application by Microsoft 

    "CRM Int. Table. Subscriber"(CodeUnit 5341).OnCleanupAfterJobExecution line 15 - Base Application by Microsoft 

    "Job Queue Entry"(Table 472).CleanupAfterExecution line 16 - Base Application by Microsoft 

    "Job Queue Entry"(Table 472).FinalizeRun line 4 - Base Application by Microsoft 

    "Job Queue Dispatcher"(CodeUnit 448).HandleRequest line 47 - Base Application by Microsoft 

    "Job Queue Dispatcher"(CodeUnit 448).OnRun(Trigger) line 19 - Base Application by Microsoft


    They have shared that this is due to 2 event subscriber in the codeunit 5341 "CRM Int. Table Subscriber".

     - OnAfterDeleteIntegrationTableMapping

     - OnCleanupAfterJobExecution


    That said, they have also provided us with a possible change which I believe it would benefit our product greatly and will provide better functionality to our partners and customers: (Change in capital letters)


    .........


      [EventSubscriber(ObjectType::Table, Database::"Job Queue Entry", 'OnAfterDeleteEvent', '', false, false)]

      local procedure OnCleanupAfterJobExecution(var Rec: Record "Job Queue Entry"; RunTrigger: Boolean)

      var

        IntegrationTableMapping: Record "Integration Table Mapping";

        RecordID: RecordID;

        RecRef: RecordRef;

      begin

        if Rec.IsTemporary() then

          exit;


        RecordID := Rec."Record ID to Process";

        if RecordID.TableNo() = DATABASE::"Integration Table Mapping" then begin

          RecRef := RecordID.GetRecord();

          RecRef.SetTable(IntegrationTableMapping);

          if IntegrationTableMapping.Get(IntegrationTableMapping.Name) then

            if IntegrationTableMapping."Delete After Synchronization" then

              IntegrationTableMapping.Delete(true);

        end;

      end;


    .........


      [EventSubscriber(ObjectType::Table, Database::"Integration Table Mapping", 'OnAfterDeleteEvent', '', false, false)]

      procedure OnAfterDeleteIntegrationTableMapping(var Rec: Record "Integration Table Mapping"; RunTrigger: Boolean)

      var

        JobQueueEntry: record "Job Queue Entry";

      begin

        if Rec.IsTemporary() then

          exit;


    //+CHANGE

    if IntegrationTableMapping."Delete After Synchronization" then

      exit;

    //-CHANGE


        JobQueueEntry.SetRange("Object Type to Run", JobQueueEntry."Object Type to Run"::Codeunit);

        JobQueueEntry.SetFilter("Object ID to Run", '%1|%2', Codeunit::"Integration Synch. Job Runner", Codeunit::"Int. Uncouple Job Runner");

        JobQueueEntry.SetRange("Record ID to Process", Rec.RecordId());

        JobQueueEntry.DeleteTasks();

      end;


    .........



  • Extending the functionality of CRM and Business Central Integration - Company drop down select menu

    A partner has raised a limitation of our product being the CRM Business Central integration only taking a single company into consideration without the option to choose which company that would be if there are two or more available in the Business Central environment.


    An idea from 2018 goes over the scenario and there is positive feedback, however, the functionality has not been implemented since:

    Microsoft Idea (dynamics.com)


    I believe it would be great improvement of our product if our partners and customers are able to choose either one or multiple companies which are to be connected to CRM, if more than one is present in Business Central.



  • Balance fields and Dataverse synchronization

    An interesting scenario related to Balance fields drew my attention and I believe that it would be a great idea moving forward that that Balance fields on Customers and Vendors should be synchronized to Dataverse even if the user is not synchronizing Dynamics 365 Sales.