Skip to main content

UI- User Interface

 

Why I like  D365 products is that , they care about the users. They generate things that help users. Not just for functionality but the UI.

So these are some examples that I like to use below.


1. Saved Queries: You can save your queries and have your reports accordingly without to re-enter same information every time. For example, you want to report invoices from the local customers.You give the filter and save query. Then you only need to select the query you saved.

2.Create Workspaces: Workspaces are also can be created by users. On the work spaces, you can see the forms you selected as links, tiles or in grid view.

3.Change Forms: User can change their own forms. Add totals, hide, add fields. Also you can share your forms around the other users easily.

4. Change size of tiles: As a new functionality, you can even change the tile size. 

https://www.linkedin.com/posts/andreadc_configure-your-workspace-of-choice-as-startup-activity-6944520939745230848-JJI0?utm_source=linkedin_share&utm_medium=android_app

5. Security Options for Forms: Users are able to know the security needs to see the forms, directly from the forms , under options.

6.Power BI: Power BI reports are really easy to see and understand the data that you manage.

7.Favorites: By to add to favorites, you can even create your own menu Slight smile

8.Power Apps: I can say that Power apps is not too much part of the UI but, while you do your integrations, you can prepare your screens as you wish.

9.Mobile Devices: Mobile devices are being used by the users in the processes like WMS.

Labels:

Comments

Post a Comment

Popular posts from this blog

Manage ERP with Success - Blockers of Success

  To manage an ERP process with success is not easy at all. Even there has been processes that have been published by companies, it is mostly depend on the people. In this blog , I am going to share the reasons I see as blockers of during the projects. This is not a scientific measure but just my opinions. Sales Team:  ERP project starts from even before the sales documents are finalized. So company needs (not user/not management etc.) need to be understood wisely and to be checked if the tools can manage these needs and details need to be documented in the contract. Expectations:  Unfortunately, ERP is a software but not a hardware. So expectation management is very important. If it was a hardware, then you will be able to return and to document specific details.  Project Team:  By project team, mostly we understand the consultancy firm but project team does consist of also from customer project managers, users, power users etc. All project team need to be well...
Post a Comment
Read more

Allocation ways in D365 FO

 When we say allocations of expenses through accounts and dimension, there are various ways that can be used in D365 FO. In this blog you can find these ways and their differences from one to another. Cost Accounting Module:  If you do not need/require to post any transaction or you think that there will be too many transactions appear on voucher transactions, then you can use cost accounting module to report on your balances. This module works separate from the GL module. Data is transferred from GL module and you prepare your allocation rules in this module and do your reporting. also you can use this module for to report different versions. Allocation Rules : You can define allocation rules and within the period you want to use, system will allocate the balance to the relevant account and dimensions. The pros of this type is that, you can trigger and change the rules whenever you want to . The cons of this type is, you need to trigger each rule one by one, wait for the repo...
Post a Comment
Read more

Fast Track Recognized Solution Architect

      You may be a fast track recognized solution architect. Fast track is best practices to succeed on the project.(Called Success by Design) This process is documented by the fast track solution architects. When applied to be a fast track solution architect, evaluation is done by D365 engineering team.      Earning Criteria The architect must be nominated by the partner Must have a minimum of 5 years of experience with Dynamics CRM or ERP products Must have a minimum of 3 years of experience as a solution architect Must be the lead architect on at least 2 FastTrack governed customer implementation projects Must be responsible for the architecture and design of at least 2 FastTrack governed customer implementation projects Even if you can not fill these requirements above, you are still able to read the detailed documentation from the links below to succeed. https://docs.microsoft.com/en-us/dynamics365/fasttrack/implementation-guide/overview https://www.d3...
Post a Comment
Read more