Sunday, December 9, 2012

Calling all Developers! Get ready for GP 2013 - Dexterity Training in St. Lake City! December 17th–21st, 2012


16447-White-Person-A-Workaholic-Floating-On-A-Yellow-Inner-Tube-In-The-Ocean-While-Typing-On-A-Laptop-Computer-Clipart-Illustration-Graphic
This is short notice, but if you can come, it'll be worth it! All of you VS Tools and VBA programmers, you really need to learn this stuff!

I’ll be doing a one-week class that will incorporate two weeks of training material. If you ever wanted to drink Dexterity through a fire hose, then this class is for you.

We’ll go non-stop for one week passing through very basic scripts, up to cross-dictionary work. No previous experience in Dexterity is required except going through the Quick Start manual that is included with the Dexterity documentation.

You’ll start writing integrating sanSript the first day of class!

This class was architected by T Hoecherl, a senior developer with Premier Computing, Inc. T is the man with all of the answers when it comes to logistics and cost. He can be reached at the following numbers:
Office: 801-487-8400, ext. 130
Cell: 801-259-7786
T tells me his classroom can hold eight people and he has a couple of spots left that he would like to fill. So, come to Salt Lake City on December 17th and get that training you need before GP 2013 hits the shelves!

The one-week Dexterity Basics class is still scheduled to go in Orlando in February of 2013, but here’s an earlier offering if February just seems too far away.

I hope to see you in Salt Lake City!

Kind regards,

Leslie Vail 972-814-8550




Monday, November 12, 2012

Dexterity Basics training February 11–15, 2013 in Orlando



Looking for Dexterity training? Come to Orlando!

I will be teaching the Dexterity Basics class at Integrated Business Group (IBG). The training will take place in Orlando, Florida from February 11th to February 15th, and will provide the basic foundations any Dexterity programmer must have.

This is an opportunity for all of you VSTools programmers to learn how to build your user interface in Dexterity instead of WinForms so that your application will run with the new GP 2013 Web Client. Your existing code will hook right up to the Dexterity events,  you may even like the Dexterity forms designer even better than VS Tools!

For more information, contact the training coordinator, Roxanna Alvarez at ralvarez@ibgnet.com or at her direct line +1 (407) 965-9299.

Hope to see you  in Orlando!

Monday, October 8, 2012

**ERROR: Batch level errors were encountered.

 

If you have ever received the above error on a posting journal or edit list, check to make sure the fiscal period for the batch you are trying to post is open. The posting journal/edit list should have another clue about what was causing the error at the top of the report.

The image below shows the error and the hint.

Batch level errors

Until next post!

Leslie

Monday, September 17, 2012

When things go Wrong - I need to delete a printed SOP document

Dynamics GP presumes that any document that you print becomes a critical document in the business cycle and typically, does not let you delete it. But sometimes, you must delete it.

What to do?


The SOP module keeps track of the number of times you have printed a document. If you print it once, and printing to screen counts as printing, you cannot delete it. Therefore, you need to set the system back to believe it has never been printed in order to delete it.

Of course, this is not a supported solution, so use it at your own risk. The first step is to back up your System (DYNAMICS) and company databases. The name of your company database is displayed on the Company Setup window.

USE YourCompanyDatabase
GO

UPDATE SOP10100
SET TIMESPRT = 0
WHERE SOPNUMBE = 'your_SOP_Doc_Number'

When things go Wrong - Error registering table GL_Account_MSTR

Here's what happened.





 



You've just installed the workstation, you launch it and are greeted with this:


What to do?

You'll be delighted to know that this is an easy fix. The problem comes up when folks copy the Dynamics.set file to one worksation from another before they synchronize the existing Dynamics.dic to the systems account framework.

All you need to do is change the dex.ini file so that the following entry exists:

Synchronize=TRUE

Most likely, yours says FALSE

You need to make sure you only have one of these entries in your Dex.ini file. If you have more than one, the first one rules.

After you change the Dex.ini setting (in the Data folder of your application folder), you'll need to launch Dynamics Utilities in order to complete the synchronization process.

Once the synchronization process is complete, the error should go away, and Dynamics GP should launch.

Don't ya' love all of the 'should's' in that dialog?

Live the Dream!

Leslie

Thanks to David Musgrave's keen eye I changed this post to the correct setting. I had it backward originally. Unforgivable for the dex.ini queen.