top of page

Current Version

We've completed Version 1 of our D365 Dashboard.

It's still in testing and review with our Dev Team.

​

The screenshots below, will help you visualise the system.

We make significant changes every day, so expect something new in the next 3 months.

​

The technologies that we use are;

​

Visual Studio 2022 with C#

Radzen Blazor Studio

JointJS for Graphing

Microsoft Azure SQL Server

Microsoft Active Directory

​

Microsoft Visual Studio 2019 with X++

Microsoft Server - D365 F&O Dev Server

Microsoft SQL Server

​

​

Home Page 

Logins are secured using the client's Microsoft Active Directory.

We use Radzen Blazor for the scaffolding in C#.

Our Dev machines are Windows 11.

​

​

Slide12.PNG

Business Rules

A copy of all Business Rules are kept in the Report Templates menu.

We're still deciding whether to refer to them as BR or RT's.

​

They have been grouped into D365 module and menu order.

​

​

Slide13.PNG

Edit Business Rule (1/2)

Business Rules contain details of the problem and solution.

This information is used to explain in detail why this is a risk to a business.

And what you could do, if it's discovered in your company.

​

The goal is to get clients to consider what other possibilities exist in your system.

And how a SQL query can detect and help remediate issues, before they come a problem.

​

Slide14.PNG

Edit Business Rule (2/2)

One the key components of every Business Rule,

is the SQL Query which is run by a D365 Agent app (also developed by Mobeez).

Slide15.PNG

Mobeez Blog

A Blog article is automatically generated for every Business Rule.

It's also published to Linkedin so that others become aware.

Slide16.PNG

Business Rule Parameters

Every Business Rule has a default set of Parameters.

These can be changed to suit each client.

And the same rule can be scheduled with different parameters,

at different times against different D365 environments.

​

​

Slide17.PNG

Report Schedule

Every Business Rule remains unused, unless a schedule is set.

A copy of the SQL statement and parameters is stored in schedule.

This is referred to by the D365 code, when generating the report.

​

​

Slide18.PNG

Report Logs

Once a report has been run, the results are returned in bulk from D365 into the Azure SQL database.

They are listed in order for a given date and specific environment and module.

Slide19.PNG

Dynamics Columns (1/2)

Because each report can contain different data, the system will automatically format the screen and any exports to display the correct columns and data type.

 

The original Business Rule can change over time and this won't affect reports history.

For example adding a new column and removing an old column will not cause

issues with previous reports to fail. 

Slide20.PNG

Dynamic Columns (2/2)

This is the second report to demonstrate that the system extracts the correct data for each report.

Slide21.PNG

Next Step

We are now developing the programmable dashboard for D365.

This is where users can create dashboards, assign D365 security groups and users.

​

Slide22.PNG

© 2023 by MOBEEZ Pty Ltd  ABN: 27 609 847 305

bottom of page