I spent a little while looking into why this was happening and found a few posts saying to copy the Dex.ini file into a Data folder in the dictionary location, but this had no effect.
Instead the Dex.ini file should be copied into a
%ProgramFiles(x86)%\Microsoft Dexterity\Dex 16.0
Once the Dex.ini file had been copied into the installation folder of Dexterity, I was able to enter debug mode without further issue.
I had quite a busy day on day 2 with a lot of sessions.
The first session, I was attended was Developing All-In-One Document Viewer. This session showed how they developed the All-In-One Document Viewers. One point the presenter stressed, was that there had been no new additions to Dexterity to allow these windows to be created; it was all done using standard functionality.
It’s very interesting how it was done, as these windows look and behave most unlike the other windows in Microsoft Dynamics GP.
The short version of this, is that there are other controls laid over the usual scrolling window controls to hide the 3D effects and a temporary table used to control how many records are displayed. Tricksy.
As a side note, I took my life in my hands for this session and sat next to David Musgrave (he’d tried to poison me earlier in the week).
The tenth Feature of the Day is .NET Interop. The new Service Based Architecture enables Microsoft Dynamics GP and ISV products to expose and consume services. Services are the backbone of the cloud and this feature supports new and exciting scenarios around cloud based interaction.
Developers can now directly reference .NET assemblies and their objects in sanScript in order to leverage capability offered in the .NET Framework. This includes the ability to call out to services or use objects as a means of data handling and processing.
The roles targeted by this feature are:
Today, it is time for part 5 of my review where I look at Chapter 6: Deploying a Dexterity Solution where Leslie covers the following key topics:
- System requirements
- Versions and builds
- Table creation routines
- Completing the application
- Creating the chunk file
- Testing in a multi-dictionary environment
- Distributing the completed application
This chapter has a fair bit of explanatory text covering each of the key topics.
Today I’m taking a look at Chapter 5 which covers sanScript and how to add it to windows to enable the required functionality. The key topics to be covered are:
- Introduction to sanScript
- Scrolling Windows
This chapter is all about Building the User Interface which Leslie does by getting the reader to build an interface for customer contacts integration and covers:
- Creating base resources
- Creating tables and keys
- Creating forms and windows
- Creating scrolling windows
- Working with window fields
- Completing your windows
So from this chapter I expect to get a good grounding in creating an entirely new window which should look like this:
Well, I now have a bit more time so I’ve returned to the book to take a look at chapter 3, Getting Started with Dexterity which gives a thorough look at Dexterity; how to install it’s development environment, what the components are and how they hang together and the pitfalls to watch out for.
However, Microsoft Dynamics GP 2013 was available I’ve decided to perform the practical examples using this version rather than GP 2010 because I had just finished building a customisation environment with GP 2013 installed in it and I could easily add Dexterity and the other tools used in the book to the environment.
As I was following the steps in Chapter 3 of the book, which is an introduction to Dexterity, where common errors and issues encountered in Microsoft Dynamics GP 2010 and how to resolve them are explained, I came across an error which was specific to Microsoft Dynamics GP 2013;