Management Reporter Crashing while Importing / Exporting Building Blocks

When migrating reports from one management reporter server to another, the easiest way is to export the management reporter building blocks from the original management reporter server and import them into the new server.

It is a straight forward method and it doesn’t seem to encounter much efforts theoretically. Although, when you have the management report crashes all of a sudden while doing the export or import, things get too complicated.

Case Reported – Management Reporter Crashes during Import Export of Building Blocks :

As clearly illustrated in the screen shot below, on the import export wizard of the building blocks, you highlight the specific reports you want to import and click on “Import Function”. At certain import it works and at other chances it fails and MR crashes and close.

Management Reporter Crashing while Importing / Exporting Building Blocks

Import Export of Building Blocks – Wizard

Management Reporter Crashing while Importing / Exporting Building Blocks

MR Crashes – MR Dynamics ERP has stopped Working

MR Crash Cause 
The root cause of the problem above is that if the “mouse cursor” passes over the “report name” column, management reporter client pops up an info message, this functionality is not supported by a certain window update. 

Resolution 
In order to ensure that the MR client will not crash while doing the import export for the building blocks, you simply need not to move the mouse cursor over the “report name” column. Eventually, the building blocks will be imported and exported smoothly without any encountered issues. 


Best Regards, 
Mahmoud M. AlSaadi

Creating a New Company in Dynamics 365 Business Central

One of the most essential benefits of a cloud based ERP system is that it requires zero time to be install and can be setup and configured almost in a blink of an eye. In this post, we are going to demonstrate how easy it is to create and setup a new company on Dynamics 365 Business Central.

Step 1 | While you are on the evaluation company, Cronus, click on the search function to search for the “Companies” form, from which new companies can be created.

Companies

Step 2 | On the “Companies” form, click on “Create New Company” and fill out the name of the company

CreateNewCompany

Step 3 | A wizard to “Create New Company” will open up driving you through the steps to get it ready:

CreateNewCompany_01

Step 4 | Type in the company name. Then, you will have to choose the “data and setup to get started”, the available options are:

  • Production – Setup Data only
  • Evaluation

CreateNewCompany_02

That’s it … the company is created and the next step is to Setup the company and to import the data.

CreateNewCompany_03

NewCompanyCreatedSuccessfully

In order to open the company, click on the “Settings” icon on the top bar of Dynamics 365 Business Central home page, and choose the company in order to login using your credentials. Additionally, you can choose the “Role Center”

MySettings

Basic Setup for the New Company

After creating the company, the system will pop up multiple setup wizards for you to check from, this includes the primary setup of the company which includes the following:

  1. Company address information and logo
  2. Company contact details ( Phone Number, Email and Home Page)
  3. Enable Bank Fees server
  4. Company’s bank information ( Bank name, Bank Branch Number & Bank Account Number)
  5. Company’s fiscal year
  6. Costing method for the inventory valuation

Here is the screen shot for the above steps which needs to be followed when setting up the company.

Step One | Company Address

2

Step Two| Contact Details

3

Step Three| Enable Bank Fees Service


4

Step Four| Company’s Bank Details

5

 

Step Five| Fiscal Year

6.png

Step Six | Costing Method

7

That’s it

8

Here you go, Dynamics 365 Business Central is up and running,

HomePage.png

 

 

Best Regards,
Mahmoud M. AlSaadi

Dynamics GP – Inventory Reconcile to GL – Inventory HITB Report Missing Records

When reconciling inventory module with the general ledger in Dynamics GP, the historical inventory trial balance represents the most powerful tool which is used primarily by GP end users. several previous posts were introduced on Dynamics GP Essentials as part of the Essentials Series . In this post, we are shedding a light on a specific support case related to missing records in the HITB report. 


Support Case 
HITB report and Inventory Reconcile to GL retrieves data primarily from the SEE30303 table. In this essence, the following should perfectly match without any issue.
  • Inventory Reconcile to GL
  • HITB – Historical Inventory Trial Balance Report ( Reports > Inventory > Activity > Historical Inventory Trial Balance
One additional customized report for the HITB that was previously provided on this link retrieves the inventory cumulative balances as of a specific period. Here is the report details:
Inventory Balances – HITB Cumulative
Logically speaking, the following three parts should match perfectly since they all retrieve data from the HITB table – SEE30303. 


In once of the recent support cases, the client reported that there are missing transactions from the HITB, when they print both; reconcile to GL and HITB, these transactions don’t appear as part of the details. The result is that the Inventory and the GL are not reconcile. 

The variance was represented with these missing records, which total value closes the variance and results in zero difference between the GL and the Inventory module


Resolution
When checking the SEE30303 table, these transactions were available, although, they were not printing out on the HITB report since the following two columns were populated as 0 

  • IVIVINDX
  • IVIVOFIX
The resolution was to simply update the following fields in order to retrieve the correct inventory account as derived from the item card.
The following SQL Script retrieves these records which have incorrect inventory and inventory offset account index:
SELECT ITEMNMBR,
      
SEQNUMBR
,
      
DOCDATE
,
      
GLPOSTDT
,
      
DOCNUMBR
,
      
DOCTYPE
,
      
LOCNCODE
,
      
RCPTNMBR
,
      
RCTSEQNM
,
      
PCHSRCTY
,
      
QTYTYPE
,
      
UOFM
,
      
TRXQTYInBase
,
      
TRXQTY
,
      
VARIANCEQTY
,
      
UNITCOST
,
      
EXTDCOST
,
      
DECPLQTY
,
      
DECPLCUR
,
      
IsOverrideReceipt
,
      
IsOverrideRelieved
,
      
OverrideRelievedDate
,
      
RCPTNMBR1
,
      
HSTMODUL
,
      
ORTRXSRC
,
      
LNSEQNBR
,
      
LNITMSEQ
,
      
CMPNTSEQ
,
      
SRCRFRNCNMBR
,
      
VENDORID
,
      
PONUMBER
,
      
TRXREFERENCE
,
      
VCTNMTHD
,
      
IVIVINDX
,
      
IVIVOFIX
,
      
JRNENTRY
,
      
TRXSORCE
,
      
DEBITAMT
,
      
CRDTAMNT
,
      
DATE1
,
      
TIME1
,
      
DEX_ROW_ID
FROM dbo.SEE30303
WHERE IVIVINDX = 0
      AND IVIVOFIX = 0;

Important Note !
If the SQL Query above retrieved any records at all, you will have to update the inventory and inventory offset index columns and then run the HITB or the IV reconcile to GL again.
Best Regards, 
Mahmoud M. AlSaadi