Tag: erp

Posted on

Jet Reports Integration with Dynamics NAV 2009 through ODBC Drivers

Jet Reports is a reporting and analytics tool that allows users to create and automate reports in Excel, using data from various sources, including Dynamics NAV. In this blog post, we will explore the steps involved in integrating Jet Reports with Dynamics NAV 2009 through ODBC drivers.

Step 1: Install Jet Reports The first step in integrating Jet Reports with Dynamics NAV 2009 is to install the Jet Reports software. You can download the software from the Jet Reports website and follow the installation wizard to complete the installation process.

Step 2: Set Up an ODBC Connection Once Jet Reports is installed, you need to set up an ODBC connection to the Dynamics NAV database. This involves creating a Data Source Name (DSN) in the ODBC Data Source Administrator on the computer where Jet Reports is installed.

To set up the ODBC connection, follow these steps:

  1. Open the ODBC Data Source Administrator.
  2. Go to the System DSN tab and click on the Add button.
  3. Select the Microsoft Dynamics NAV ODBC Driver and click on Finish.
  4. Enter a name for the DSN and select the database server and database name.
  5. Enter the authentication details for the database and click on Test Connection to verify the connection.

Step 3: Create a Jet Reports Data Source After setting up the ODBC connection, you need to create a Jet Reports data source to connect to the Dynamics NAV database. This involves specifying the ODBC connection details and selecting the tables and fields to be included in the data source.

To create a Jet Reports data source, follow these steps:

  1. Open Jet Reports and go to the Data Source Designer.
  2. Click on the New button to create a new data source.
  3. Select the ODBC option and enter the DSN name and authentication details.
  4. Select the tables and fields to be included in the data source and specify any filters or sorting criteria.
  5. Save the data source and test the connection to verify that the data is retrieved correctly.

Step 4: Create a Jet Reports Report Once the data source is set up, you can create a Jet Reports report using the data from the Dynamics NAV database. This involves selecting the data source and designing the report layout using Excel.

To create a Jet Reports report, follow these steps:

  1. Open Jet Reports and go to the Report Designer.
  2. Select the data source created in the previous step.
  3. Drag and drop the fields from the data source into the Excel sheet to create the report layout.
  4. Add any formatting, calculations, or other elements to the report as needed.
  5. Save the report and schedule it to run automatically or run it manually when needed.

Conclusion In conclusion, integrating Jet Reports with Dynamics NAV 2009 through ODBC drivers involves setting up an ODBC connection, creating a Jet Reports data source, and designing a report using Excel. By following these steps, users can retrieve data from the Dynamics NAV database and create customized reports for analysis and decision-making. Jet Reports is a powerful tool that can help businesses streamline their reporting processes and improve their operational efficiency.

Posted on

Dynamics NAV 2015 objects migration to Business Central SaaS

As businesses grow, so do their needs for better and more efficient systems to manage their operations. For many companies, Microsoft Dynamics NAV 2015 has been the go-to solution for enterprise resource planning (ERP) software. However, with the introduction of Business Central SaaS, many businesses are now considering upgrading their existing Dynamics NAV 2015 systems to take advantage of the benefits of cloud-based ERP.

But upgrading a system as complex as an ERP can be a daunting task, especially when it involves migrating existing customizations and objects. In this blog post, we will discuss the continuing upgrade of Dynamics NAV 2015 objects migration to Business Central SaaS.

Step 1: Evaluate Your Current Dynamics NAV 2015 Environment

Before starting the migration process, it’s important to evaluate your current Dynamics NAV 2015 environment. This will help you identify any potential issues that may arise during the migration process and help you plan accordingly.

Step 2: Identify Customizations and Objects

Next, identify any customizations or objects that you have in your current Dynamics NAV 2015 environment. These may include modifications to existing forms and reports, custom code units, or new objects that you have created.

Step 3: Assess Compatibility with Business Central SaaS

Once you have identified your customizations and objects, you will need to assess their compatibility with Business Central SaaS. Some customizations may not be supported in the cloud environment or may require modifications to work properly. It’s important to evaluate each customization or object and determine the level of effort required to make it compatible with Business Central SaaS.

Step 4: Upgrade Your Customizations and Objects

After assessing compatibility, you can begin upgrading your customizations and objects. This may involve making changes to the code or modifying forms and reports to work properly in the cloud environment. It’s important to test each customization thoroughly to ensure that it works as expected.

Step 5: Test Your Upgraded System

Once all customizations and objects have been upgraded, it’s important to thoroughly test your upgraded system to ensure that it works as expected. This may involve testing business processes, running reports, and verifying data integrity.

Step 6: Deploy Your Upgraded System

Finally, when you are confident that your upgraded system is ready to go, it’s time to deploy it. This may involve migrating data from your old system to the new one, configuring settings, and training users on the new system.

In conclusion, upgrading from Dynamics NAV 2015 to Business Central SaaS can be a complex process, especially when it involves migrating customizations and objects. However, by following the steps outlined in this blog post and working with a qualified partner, you can successfully upgrade your system and take advantage of the benefits of cloud-based ERP.

Posted on

Preparing release of Progress Reporting Management app

General

o Introduction of “Sync on Sign out” if an app user is being signed out with unsynced data.

o Visual updates and introduction of new colour schemes across app

Measure

o Introduction of Horizontal scrolling in Measure sheets. (user based permission, can be set based on app user preference in app user setup)

o Introduction of “Company Scope” on Column setup to allow narrowing of companies from drop down lists eg on Cable schedules

Allocation Module

o User based permission to allow exceed clocked values (NAV app user setup)

o Introduction of Data limits for types of resource eg Operatives, 24 and Company, 5000 per day.

o On WBS selection, Introduction of Tree like function to enable user quickly find value. User can search this also

o On System/Asset selection, the system list has a search function aswell as select from list function.

o Both WBS and System Asset also have a feature that shows last selected entry on top of list for repetitive data entry tasks

o The “Company Scope” of Measure columns list will obey the same setup, ie help narrow the list of systems under a resource

o Introduction of cross device sync, all app users can see previous entries from different app users for same Resource

o Introduction of complex entries, app user can add additional entries for same Resource & system, but with different WBS and System/Asset allocations

o Clock value for current day now comes into allocation view, app user can exceed this value, but not for previous days

Diary

o On WBS selection, Introduction of Tree like function to enable user quickly find value. User can search this also

o On System/Asset selection, the system list has a search function aswell as select from list function

o Both WBS and System Asset also have a feature that shows last selected entry on top of list for repetitive data entry tasks

Testing

o Bug fix on rejected test sheet where user could not see rejected sheet on device from which previous test sheet was completed, but could see from different device

Snags

o On WBS selection, Introduction of Tree like function to enable user quickly find value. User can search this also

o On System/Asset selection, the system list has a search function aswell as select from list function

o Both WBS and System Asset also have a feature that shows last selected entry on top of list for repetitive data entry tasks

o Changes to Mandatory fields in snag card inline with QA dept requirements

o Draft Snags (incomplete mandatory fields) will not transfer to NAV and assigned app users

o Search bar now can handle multiple search requests, so for example you can search a Discipline, an Assigned Company and System/Asset by placing a space between key words eg ELEC YR

o New Power BI visual to allow BI users interact with project layouts using assigned WBS for snag locations