OLE Notes and Microsoft Dynamics GP 2013 Web Client

In the past years, I have written extensively about Microsoft Dynamics GP OLE Notes and the Dexterity OLE Container application, in the hopes of finding a way to extract the Container documents and links (unsuccessfully so far) as a result of several issues I have encountered in the past with customers attempting to migrate their notes to a different server, see:

All about the Dexterity OLE Container
All About Dexterity OLE Container - Follow Up

My good friend David Musgrave has also written a couple articles on the subject of record notes in two articles as well, see:

Understanding Notes and the Note Index field
OLE Attachments and Record Notes

Now with the release of Microsoft Dynamics GP 2013 Web Client, a new challenge is presented around the use of OLE Notes: the OLE Container cannot be exposed to the Silverlight application.

The Dexterity OLE Container, from past articles, is a 32-bit C++ application and as such, calls to the paperclip attachment button made from the Silverlight application will launch the Container in the Silverlight application - that is expected.

Let's take the following sequence of events, where an OLE attachment is added to an item number in the rich client environment. The attachment and all the behavior we expect occur normally and we get an indicator of an attachment being present.

Rich Client with OLE Container Note

Under the web client, you will still get an indicator of the record note being present, along with the "OLE Link present." message, but will not be able to access the OLE attachment as there's no paperclip button - and by definition, you cannot load a Win32 program from within a Silverlight application front-end - again, this expected.

Web Client displaying attachment present, but no paperclip button

Upon closing the note window, the note indicator disappears for the record being displayed, conveying the impression that there's no record note attached.

Web Client no longer shows an attachment being present

But back in the rich client, if you retrieve the record once more, the "OLE Link present." message is restored and the OLE attachment is certainly present.

Rich client still shows attachment and re-adds the "OLE Link present" text.

In summary, it seems this is just a behavior you will experience on the Web Client, but rest assured that your notes and attachments are still there, just the visual cue is not updating properly upon closing the note window under Web Client. I am sure the good folks in the Microsoft Dynamics GP Development team are already looking into this.

Now, since you are not able to use the Dexterity OLE Container in the Silverlight application, the alternative is to - perhaps - slowly but surely migrate your notes to the more robust Document Attachment feature. I will talk more about this in my next installment and will also compare it to your traditional Dexterity OLE Container notes.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

"You have too many note windows open. Close a note window" Error Message

Recently, a system administrator reported a user getting this error and was asking what could be the possible cause for this.



Replicating the error is very simple, and for this, we need a Microsoft Dynamics GP window where many note windows can be entered/opened at once, take for example the Sales Transaction Entry window, which has access to 7 potential notes: the document type, the document number record note, the customer ID record note, the batch ID record note, the site ID record note, the currency ID record note, and the item number record note.



If you attempt to access all these notes at a time will prompt the system to error out when attempting to open a 6th note window. Taking advantage of the Windows 7 Aero interface, one could see why an end user will not realize they have 5 note windows opened at once.



But now to the technical issue...

To display notes -- record level notes -- the Dynamics GP development team has created five forms, righfully called Form_Note_1, Form_Note_2, Form_Note_3, Form_Note_4, and Form_Note_5. Each time a note is added, the code will check for the availability of one of these 5 forms to be able to open the corresponding note window so the user can either type a new note or read an existing one. If all note forms are opened at the same time, then an attempt to open a sixth note will fail with the error described at the beginning. The solution? Close an unused note window.

Why not create more note forms? 25 years and 11 major releases later, this is an expensive proposition. There is a lot of code in older Microsoft Dynamics GP forms that handle their own calls to validate which of the 5 note forms is open. In newer form objects, these call checks have been replaced by a single call to methods added to the NoteObj form, but unfortunately, "retrofitting" the entire Microsoft Dynamics GP application to work with the NoteObj form is a project in itself that would require tons of testing to make sure nothing gets broken in the process. Certainly, if all the application could be retrofitted to handle calls to the NoteObj form, then adding an extra note form is not so much of an issue anymore... but there lays the problem. Adding this extra form would also cause all third party developers and ISVs to retrofit their code to manage this extra form too. Then comes the philosophical question... what if we want to open a 7th note, or an 8th... do we keep adding more forms? How many note forms would be enough?

More information on Notes, Note Index and OLE Attachments can be found at:

Developing for Dynamics GP - Click here
The Dynamics GP Blogster (this site) - Click here

Until next post!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC.
http://www.maximumglobalbusiness.com/

Read More