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

How to set up parent project in project accounting in ax 2012

create simple project and then go to the project hierarchy fast tab and there you must define sub-project ID format "-#" and then your sub-project will be enabled. For resource assigning in Project first you need to configure the HR module, in that you need to maintain the calendar for those employees and then you need to define the cost of that particular employee (for expense) and for Revenue you need to define the sales price of that particular employee. In the project accounting module you need to mention the calendar in scheduling fast tab and then you need to define WBS, in WBS activity you can be able to assign resources.

Sales order posting Error - Voucher do not balance as per date in axapta 2012

Problem - How to get rid of this error if its coming while doing the sales invoice . "The transactions on voucher V-00001 do not balance as per 4/11/2014. (accounting currency: -1111- reporting currency: -232) " .  Suggestions: 1.Exchange rate setup , number sequence of invoice voucher, currency rounding all are done correctly , but still this error exists 2.Define currency for each account..or go in currency setup and check currency and rounding up rules 3.Check with penny difference in GL 4.Check there is proper conversion exchange rate defined for reporting currencies. 5. Check Rounding of option of for primary and reporting currencies both. 6.Check all the posting accounts defined in Posting profiles 7.check COGS, Customer, issue, revenue accounts are mapped. 8.Check primary and reporting currency has proper exchange rates and rounding rules defined. 9.Try to increase the value in the penny difference and then post the sales invoice. 10. Make sure ...