From Concept to Delivery: Streamline your business with Microsoft Dynamics

MS Dynamics Nav on the ERP Ideas Blog

  • Connect with eSoftware Professionals on LinkedIn

Hierarchy of Change

Posted by David on January 5, 2012

Microsoft Dynamics NAV Code ChangesAs a Microsoft Dynamics NAV Developer we are aware, NAV is a highly customizable solution and while this is certainly an attractive attribute, it does imply a certain level of responsibility at the partner level. When we customize objects and/or code we are creating a de facto system behavior or functionality; a situation whereby events will play out in the business logic accordingly and without human interaction, input, or control. In many cases this is necessary and desired but it is important to consider that there may be alternative approaches.

To add some context let’s first recognize that there are a few options when it comes to changing the behavior and user experience of NAV; Personalization, Configuration, and Customization. Listed in this order they represent the preferred approach or hierarchy when it comes to system change.

Personalization

With Personalization, end users can add, remove, or arrange UI components and controls to best suit their individual work space preferences. Personalization allows simplified change but it is a powerful mechanism because it allows individuality within the overall solution and can be administered by the end user.

Configuration

Configuration is in my opinion the most versatile as it allows for expanded system functionality to be enabled (and in some cases, disabled) as desired. Normally configuration is thought of as having a system-wide impact but it can also parallel personalization; we see examples of this when considering business logic that is conditioned on a value in the User Setup table. Regardless of the scope of impact, the true versatility and power of configuration is recognized when it is coupled with customization.

Customization

Customization coupled with configuration adds a certain element of intelligence to our solutions through the use of global setup flags and/or the existence of certain data elements to steer their behavior. This relationship is especially important when we apply it in the context of an ISV product. As enhancements continue to grow such a product we must be thoughtful about how we position them within the overall solution because not all enhancements apply to all of our customers all of the time. The proper positioning of our enhancements will result in a product that is both powerful and flexible. What’s more is that we will have enabled the administration of this power and flexibility to occur at the customer level.

It is important to recognize the hierarchy of change and apply our resolution at the lowest level first. This is true whether we are troubleshooting a specific issue or developing an enhancement. It is easy to jump straight to the code base first to address an issue and miss out on the fact that we could handle the issue at a lower level. In the end we must not lose sight of the idea that the simplest solution is many times the best solution.

Quick Tip: How do I move to the next field in NAV 2009?

Posted by Connie on December 12, 2011

Q: How do I move to the next field in NAV 2009?
A: The RIGHT ARROW key will move to the next field or character in NAV 2009.

Want more shortcuts? Check out all the NAV 2009 Keyboard shortcuts.

Quick Tip: How do I Move to the Next Frame/Tab in NAV 2009

Posted by Connie on December 8, 2011

Q: Is there a shortcut to move between to the next frame or tab in NAV 2009?
A: Yes! CTRL + PAGE DOWN is the shortcut to move to the next frame or tab in NAV 2009.

Shortcuts make everything easier don’t they? Note: The same shortcut works in Ceres 2009.

Thanks to Janice at North Texas Food Bank for submitting this NAV 2009 tip request.

Best Practices in Project Management: How to Know You are in a Difficult Situation

Posted by Gretchen Freeman-Cromar on October 12, 2011

When managing complex projects we are bound to face some difficult situations. I consider a situation difficult if it meets any of the following criteria:

  • There is an acute gap between reality and the current plan. (We are supposed to go-live in an hour and the entire database is corrupt, and the IT director is drunk.)
  • Confusion exists about what the gap is, what is causing it, whose job it is to resolve it, or possibly whether it even exists. (What iceberg? I don’t see an iceberg.)
  • It’s unclear how resources should be applied to resolve the gap. Fear that taking action or doing nothing may make things worse. (Don’t just stand there, do something! Wait, no. Don’t do anything, you might make it worse!)

Typical causes for difficult project situations are listed here:

  • Oversight or realization
  • You or your team is forced to do something stupid
  • Failing schedule or resource shortage
  • Quality is low
  • Direction change
  • Team or personnel issues
  • Disagreement and conflict
  • Lack of faith
  • Threats of mutiny (acute form of lack of faith)

What makes these kinds of situations difficult is not the situation itself, but the context in which it occurs. During go-lives, many kinds of issues have fuzzy beginnings and endpoints. No red warning light will go off on your desk telling you that morale is low or that an oversight has just been made. You have to look for it, and even when you find it-it won’t always be 100% clear what is going on. Taking action, you may only be able to mitigate it and minimize its impact; it might not be entirely solvable. Part of what to do when you’re in a difficult situation is to dedicate time for maintaining chronic and unresolvable problems at a tolerable level. Here are a few tips on how to professionally do that.

Take Responsibility and Do Damage Control

Taking responsibility doesn’t make it your fault: it means that you will deal with the consequences and be accountable for resolving the situation.  By lending real responsibility to the problem, you instantly make the problem less dangerous to the project. In a damage control situation, you don’t usually have time to explore options or consider alternatives. There is usually something very important that is very broken, and it won’t be clear how it can possibly be resolved. To readily handle and face these situations, here are some tips:

Call an all-hands meeting.

The longer you wait to address it, the more fear the team will have to face. Don’t hide from big problems.

If people are in disagreement, find the point of agreement.

Bring it back to the last point of agreement: ‘Do we all agree that our goals are A, B, and C, and in that order?’ and work forward into the problems you are having.

What is the most recent known good state for the project?

If the damage you’re controlling is technical, find the last good back-up you can restore.

Can the problem be isolated?

Think of a boat that is currently on fire. Can the fire be contained? Can the most critical parts of the ship be protected against the fire? Think of how you can sequester the problem and prevent it from impacting the most critical parts of your project.

Can resources be applied to help with the damages?

Sometimes you can spend your way out of a problem. Throwing money or resources at things can sometimes work if your aim is good and it’s the right kind of target.

Find the point of unification.

Find the important points of unification and agreement and use those to start any discussion you have. You want to start with momentum.

Recognize personality conflicts and then ignore them.

It’s easy to fall into the trap of allowing someone’s personality traits to distract you from the goal of solving your problem. Find  a way to separate those feelings from the task at hand.

Look for mutual interest.

Lay out all the possible ways to resolve a situation, and look for choices that benefit both sides.

No matter what you do, things will go wrong.

If you can stay calm, and break problems down into pieces, you can handle many difficult situations. Taking responsibility will always expedite resolutions, and in extreme situations, go into damage control mode. Do whatever it takes to get the project to a known and stable state.

Read more about project management Theory in Practice Making Things Happen by Scott Berkun.

Get Jet Reports Express for Dynamics NAV 2009

Posted by Gretchen Freeman-Cromar on May 13, 2011

We’re pleased to share that Dynamics NAV 2009 will soon include Jet Reports Express. This great news was announced at Directions EMEA this week in Berlin.

Jet Reports logoJet Reports Express, a business reporting tool from Jet Reports, gives NAV users an easy and simple way to create high impact reports. Within a familiar Microsoft Excel environment, users will be able to access and merge Microsoft Dynamics NAV data and utilize all of the Microsoft Excel capabilities, such as Power Pivot, formatting, charting and Pivot Tables, to create powerful, insightful and well-formatted reports – quickly and easily.

Starting in September all versions of Microsoft Dynamics NAV 2009 will include Jet Reports Express. We’ll be sending current Dynamics NAV 2009 customers information on how to download Jet Reports Express when it’s available.

Stay tuned for more about this great new enhancement to Dynamics NAV 2009.

Downloading a File via FTP

Posted by Connie on January 11, 2011

To download information from eSoftware Professionals’ FTP server, please begin by accessing an FTP client such as FileZilla or FreeFTP. [This may require downloading FileZilla (a free software program) by going to the website www.filezilla-project.org]. If you need to install an FTP client, follow the Installing FTP client instructions below. If you already have an FTP client installed continue with Accessing the eSoftware FTP Site Manager instructions.

Accessing the eSoftware FTP Site Manager

  • Open the FileZilla or other FTP dialog box by going to where you installed it and clicking on FileZilla or other FTP client name [You may see the FTP program in your Start menu or from All Programs as well].
  • Enter files.esopro.com for the address or host.
  • Enter your unique Username and Password provided to you by eSoftware Professionals.
  • Click Quickconnect.
  • Once you complete the steps for installing the FTP on your computer, you can create a desktop shortcut that will allow you to click on your FTP icon and you will be immediately set up to connect to our server with one easy step.

You now have access to our ftp site and can begin download procedures below.

Downloading a File via FTP

  • You’ll see two columns in FileZilla. On the left is a listing of your local drive labeled: Local site and on the right is the FTP site labeled: Remote site
  • Navigate to the folder you want to save the file to in the Local site by double-clicking the folders until you find the appropriate folder
  • Click on the name of the folder and/or file you want to download from the right column, Remote site: /files.esopro.com/
  • Right Click and select Download (if you have multiple files to transfer, select Add files to queue)
  • From the Menu, Select Transfer, then Process Queue (or Ctrl-P) to complete the transfer

Installing an FTP Client

NOTE: This is only required if you do NOT already have an FTP Client on your computer. If you already have FreeFTP, FileZilla or other FTP client, you can simply follow the instructions for FTP Site Manager above).
  • Connect to www.filezilla-project.org
  • Click Download FileZilla Client.
  • Select FileZilla_3.0.9.1_win32-setup.exe (recommended)
  • Program should begin downloading. You may need to click on the pop up bar on the top of the window to allow the program to download.
  • Click Run twice
  • Click I Agree
  • For the next couple options you can click Next
  • When you get to destination folder, make sure you put this download in the correct folder where you will be able to find it again and create a shortcut link, (if you so choose).
  • Click next and then install.
  • Click Finish.

Year End Closing Part 3

Posted by John on January 4, 2011

Run the Close Income Statement

The second step in the year end close process is to run the Close Income Statement batch job to transfer the Income Statement account balances.

Scenario

After closing the 2010 fiscal year, Sam needs to run the Close Income Statement batch job to transfer the income statement accounts to account 3120, the retained earnings account, as part of the fiscal year processing.

  • The default general journal is used and the posting description includes the fiscal year number.
  • You need to retain the Area, Business Group, and Customer Group dimension information posted on the income account entries.

To run the Close Income Statement batch job, follow these steps:

  1. On the Navigation Pane, click Financial Management > General Ledger > Periodic Activities > Fiscal Year > Close Income Statement.
  2. Ensure that the Fiscal Year Ending date is 12/31/10.
  3. In the Gen. Journal Template field, click the AssistButton and select GENERAL.
  4. Click OK.
  5. In the Gen. Journal Batch field, click the AssistButton and select DEFAULT.
  6. Click OK.
  7. In the Retained Earnings Acc. field, enter 3120 (for the retained earnings account.)
  8. In the Posting Description field, add 2010 to the end of the text.
  9. In the Diminsions field, click the AssistButton.
  10. Click the Selected field for Area to insert a check mark.
  11. Click the Selected field for Business Group to insert a check mark.
  12. Click the Selected field for Customer Group to insert a check mark.
  13. Click OK to close the Dimension Selection window.
  14. Click OK to run the batch job.
  15. Click OK to the message that the journal lines have been created.

The Close Income Statement batch job does the following:

  • Transfers the income statement account balances to an account in the balance sheet.
  • Creates lines in a journal.
  • Closes the income statement accounts.
  • The closing entries are transferred to the retained earnings account.

After a fiscal year is closed, G/L entries can still be posted to the closed year. Do you need to post an entry to a closed fiscal year? Read tomorrow’s NAV Training Tip for step-by-step instructions on how to post a G/L entry and update the year-end close process to include the new entries. View the first article Year End Close tips and part 2 of the Year End Close process. Check back Thursday for the last installment in the year end close articles. Want more information on year end close procedures? Visit our training page and find classes to help you get the most out of your MS Dynamics NAV system.

Note: The same steps are used in both Ceres and eFood as outlined above for MS Dynamics NAV. The examples above use the Cronus International demo company.

For more tips and training for NAV, check out our Webinar MS Dynamics Training Schedule.

Year End Closing Tips Part 2

Posted by John on December 30, 2010

Closing a Fiscal Year in NAV

The first step in the year end closing process is to close the fiscal year. This process manages the periods and dates for fiscal years.
Note: A fiscal year cannot be closed before a new one is created.

To close the accounting periods, follow these steps:

  1. On the Navigation Pane, click Financial Management > General Ledger > Periodic Activities > Fiscal Year > Accounting Periods.
  2. Open Accounting Period in NAV

    Open Accounting Period in NAV

  3. Click Close Year. A message appears regarding the year to be closed. This year is suggested based on the earliest open year, and the corresponding check marks in the New Fiscal Year field.
  4. Note: To close a non-standard year, place a check mark in the New Fiscal Year check box of the last period to be included in the year to be closed.

  5. Click Yes to close the year.

After running the fiscal year closing process:

    Closed Accounting Period in NAV

    Closed Accounting Period in NAV

  • The Closed and Date Locked fields of all periods in that fiscal year are updated with a check mark that cannot be removed.
  • The period lengths of the closed periods cannot be changed.

After a fiscal year is closed, G/L entries can still be posted to the closed year. When posting in a closed year, entries are marked as prior-year entries. When subsequent entries are posted to a closed fiscal year:

  • The Close Income Statement batch job must be run to transfer the balances to the retained earnings (equity) account.
  • The transferred entries must be posted.

Note: To prevent users from posting entries in a specific period, set a date range in the Allow Posting From and Allow Posting To fields in the General Ledger Setup window.

Next steps. Running the Close Income Statement batch job to transfer the Income statement account balances. After the batch job is complete, the journal containing the transferred balances is posted. Check back Tuesday for details on the next step in the Year End Closing process in NAV.

Note: The same steps are used in both Ceres and eFood as outlined above for MS Dynamics NAV. The examples above use the Cronus International demo company.

For more tips and training for NAV, check out our Webinar MS Dynamics Training Schedule.

Year End Closing Training Tips for NAV

Posted by John on December 29, 2010

NAV Training Tips: Closing a Fiscal Year Part 1

Before you start the Year-End Closing you’ll want to know the answers to the following questions. This will help you prepare for your Year-End Closing steps.

Question: What are the three main steps of completing the year end closing process?

Answers:

  • Post the general journal.
  • Transfer the Income Statement account balances.
  • Close the fiscal year.

Question: What occurs after the Close Year process is run?

Answers:

  • Subsequent entries posted in the closed year are marked as prior-year entries.
  • The Closed and Date Locked check boxes in the Accounting Periods window contain check marks that cannot be changed.
  • Period lengths of closed periods cannot be changed.

Question: How Do I Post in a Closed Year?

Answer:

  • The Close Income Statement batch job must be run and then the transferred entries must be posted.

Question: What happens during the Close Income Statement batch job?

Answers:

  • Transfers the income statement account balances to an account in the balance sheet.
  • Creates lines in a journal.
  • Closes the income statement accounts.

Question: What type of account are closing entries transferred to?

Answer:

  • Retained Earnings.

Question: What occurs when posting the journal containing the closing entries?

Answers:

  • An entry is posted to each income statement account so that its balance becomes zero.
  • The retained earnings accounts are updated for the gain or loss.

Question: In the closing process, what occurs when an additional reporting currency has been set up in the General Ledger Setup window?

Answer:

  • The journal is automatically posted when the Close Income Statement batch job is run.

Question: What is used to transfer the income statement account balances to a balance sheet account?

Answer:

  • Close Income Statement batch job.

Question: What must occur to prevent users from posting in a closed period?

Answer:

  • Set a date range in the General Ledger Setup window.

Now that you know the answers to these basic Year-End Close questions you’re ready to start the steps. Check back Thursday to see the first steps in the Year-End Close process in MS Dynamics NAV. For more tips and training for NAV, check out our Webinar MS Dynamics Training Schedule.

Note: The same steps are used in both Ceres and eFood as outlined above for MS Dynamics NAV.

Will our ERP system work with computers running Windows 7?

Posted by David on December 7, 2010

Tip Tuesday: Microsoft Dynamics NAV Tip

If you have already asked yourself the question “Will our ERP system work with computers running Windows 7?”, then you’re probably ready for the next question:

What steps do I need to make before I add Windows 7 computers to the network?

Where did these lamps come from?

Microsoft Dynamics Tips

As you know, Windows 7 is now the only operating system available for new laptops and computers. Most Dynamics NAV systems will need an upgrade to support Windows 7. To make them compatible, you’ll want to work with your Dynamics NAV partner at eSoftware to upgrade your system. Not to worry, our Dynamics NAV experts have created an Executable Upgrade that will help make it a smooth transition to Windows 7 support.

Here are the steps you’ll need to take for the upgrade.

  1. Planning for the Upgrade
    1. Verify your NAV version and licensing.
      You will need NAV 4.0.3.6 or higher to support Windows 7.
      Note: The NAV executable version you can upgrade to will depend upon your database version and other add-ons.
    2. Create a list of the upgrade components on your system for example: Clients, NAS, Database Server, AE, Jet Reports, etc. (Work with your Dynamics NAV partner if needed)
    3. Verify the status of your support plan.
      You need a current support plan for upgrades.
    4. Determine whether you will need to make any other adjustments including:
      - Halting the sync server  prior to the upgrade
      - Is the existing server being upgraded?
      - Notify aidmatrix
      - NAV Licensing, etc.
  2. Test Environment Upgrade
    Depending upon the hardware components you are upgrading, your test environment may include a new server or it may simply be one or more client machines. The hardware components you are upgrading will determine whether the test environment can be configured within your network or whether it must be configured internally by eSoftware.

    1. Prepare a recent Backup from your Production Server
    2. Obtain the new NAV executable version from eSoftware.
      - Restore to new executable version onto test environment (or restore to current executable version and reopen in a new version to convert)
    3. Test select process and verify database stability
    4. Create a Backup from the new executable version
  3. Production Environment Upgrade
    1. Suspend any systems you identified in step 1.c.
    2. Install new executable files in production environment including client computers, server and all items identified in step 1.a.
    3. Upgrade the executables by restoring to the new executable version (or restore to current executable version and reopen in new version to convert)
    4. Test select process and verify database stability
    5. Restart any systems previously put on hold

We’ll be ready to assist when you’re ready to add new computers running Windows 7 to your Microsoft Dynamics NAV system. Contact your eSoftware Partner today at support@esopro.com.

Note: Microsoft Dynamics NAV is a 32 bit application. 64 bit Windows operation systems support both 32 bit and 64 bit applications. 32 bit applications are supported on 64 bit operating systems via the Windows on Windows (WOW) 32 bit compatibility mode.

Blog Directory