Skip to main content

Things to Know in Dynamics 365 architecture

To Consider in Dynamics 365 portal architecture:


Consider deployment. Desktop applications must be installed upon a particular nimble system and deployed for each PC. Web applications can have less deployment or update effort for hundreds or thousands of PCs.

Consider platform limitations. The desktop is limited by its hardware, and must meet the hardware requirements to intend the application. Web applications can meet the expense of admission to rarefied applications delivered from a centralized infrastructure. A Mobile device is limited by its screen place, user-within take effect memory and data association.

Consider users.  Who will be the majority of the users?  How will they be accessing Dynamics 365?  We are in a mobile driven world where most individuals surrounded by 12 to 70 years very old-fashioned own a mobile device. Of those mobile users 46% use a mobile application to urge regarding them considering shopping and a propos-the-go research.

Consider security. Does your viewpoint have protection that requires added security? What precautions compulsion to be taken? Online and mobile banking options have become preferential due to ease of goodwill and malleability they have enough child support.

Consider supported device. What is the preferred browser at your meting out?  How does leveraging the same Web application upon alternating browsers modify the fanatic experience?

Consider availability. Web applications are universally comprehensible but, rely upon internet connectivity in order to achievement.  In comparison, a stand-alone desktop utter is not inhibited by connectivity. Something before happening taking into account the money for a ruling in addition to a mobile device is that the application could quit or restart subsequent to the enthusiast receives a call.

Popular posts from this blog

sales order Totals option getting error in Axapta

Problem: On  click sales order Totals option getting below error. Please help me how to solve it. Microsoft.Dynamics.Ax.Xpp.ClrErrorException: Exception of type 'Microsoft.Dynamics.Ax.Xpp.ClrErrorException' was thrown. at Microsoft.Dynamics.Ax.Xpp.CLRInterop.MakeReflectionCall(Object instance, String methodName, Object[] parameters) at Dynamics.Ax.Application.TaxDocumentProxy.Sumbytaxaccountingprovider(TaxAccountingProvider taxAccountingProvider, TaxAcctPostingProfDistributionSide postingSide, String taxType, String taxComponent, Boolean , Boolean , Boolean ) in TaxDocumentProxy.sumByTaxAccountingProvider.xpp:line 15 at Dynamics.Ax.Application.TaxDocumentProxy.@Sumbytaxaccountingprovider(TaxAccountingProvider taxAccountingProvider, TaxAcctPostingProfDistributionSide postingSide, String _taxType, Boolean , Boolean ) at Dynamics.Ax.Application.TaxDocumentProxy.@Sumbytaxaccountingprovider(TaxAccountingProvider taxAccountingProvider, TaxAcctPostingProfDistributionSide postingSide, ...

X++ Code to run SSRS Report with parameter in D365 F&O (Example Sales Invoice )

Below is sample X++ Code to run SSRS Report with parameter in D365 F&O (Example Sales Invoice )      Args                       args = new Args();     CustInvoiceJour            custInvoiceJour;     SalesInvoiceJournalPrint   salesInvoiceJournalPrint;       select firstonly custInvoiceJour where custInvoiceJour.SalesId != '';       // Add record to be printed.     // In order to have the context table we need to set args.record().     args.record(custInvoiceJour);       salesInvoiceController = new SalesInvoiceController();     salesInvoiceController.parmReportName(         PrintMgmtDocType::construct(PrintMgmtDocumentType::SalesOrderInvoice).getDefaultReportFormat());       salesInvoiceContract = salesInvoiceController.parmReportContrac...