Developing for Dynamics GP

Removing Extender Data when deleting Transactions or Lines Revisited

David Musgrave — Wed, 10 Feb 2010 01:00:00 GMT

Last week, I tackled the subject of orphaned records in the Extender tables when the parent records were deleted and the Extender data was left behind. If you have not read this post the link is below:

Removing Extender Data when deleting Transactions or Lines

If you read through the comments, you will see that Konrad Berger (an Australian Partner Consultant) mentions the idea of checking the Open (or History) table to see if the transaction has been moved to the next stage (ie. posted) rather than deleted.

The concept works because most of the posting code in Microsoft Dynamics GP adds the records to the Open (or History) tables before it removed the old record from the Work table. This gives a SQL table trigger the ability to tell the difference between a record being deleted by the user and a record being posted.

So this post will take the triggers attached to the previous post and modify them to use this concept. The updated triggers are shown below and also are attached to this post. These updated triggers can be used in a live system and do away with the need for the Visual Basic for Applications (VBA) code in the previous post.

Extender Window Example - using IVTRF_1 & IVTRF_2

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[IV10000_DELETE_IVTRF_1]') and OBJECTPROPERTY(id, N'IsTrigger') = 1)
drop trigger [dbo].[IV10000_DELETE_IVTRF_1]
GO

SET QUOTED_IDENTIFIER OFF 
GO
SET ANSI_NULLS OFF 
GO

CREATE TRIGGER [IV10000_DELETE_IVTRF_1] 
ON [dbo].[IV10000] 
FOR DELETE 
NOT FOR REPLICATION 
AS 

DECLARE @ExtenderID char(15) 

select @ExtenderID = 'IVTRF_1'

SET NOCOUNT ON 

BEGIN 


DELETE A FROM EXT00101 A -- Strings
JOIN EXT00100 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30200 D 
      where D.IVDOCTYP = 3 and D.DOCNUMBR = C.IVDOCNBR)


DELETE A FROM EXT00102 A -- Dates
JOIN EXT00100 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30200 D 
      where D.IVDOCTYP = 3 and D.DOCNUMBR = C.IVDOCNBR)


DELETE A FROM EXT00103 A -- Numbers
JOIN EXT00100 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30200 D 
      where D.IVDOCTYP = 3 and D.DOCNUMBR = C.IVDOCNBR)


DELETE A FROM EXT00104 A -- Times
JOIN EXT00100 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30200 D 
      where D.IVDOCTYP = 3 and D.DOCNUMBR = C.IVDOCNBR)


DELETE B FROM EXT00100 B -- Mapping
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30200 D 
      where D.IVDOCTYP = 3 and D.DOCNUMBR = C.IVDOCNBR)
END
GO
SET QUOTED_IDENTIFIER OFF 
GO
SET ANSI_NULLS ON 
GO

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[IV10001_DELETE_IVTRF_2]') and OBJECTPROPERTY(id, N'IsTrigger') = 1)
drop trigger [dbo].[IV10001_DELETE_IVTRF_2]
GO

SET QUOTED_IDENTIFIER OFF 
GO
SET ANSI_NULLS OFF 
GO

CREATE TRIGGER [IV10001_DELETE_IVTRF_2] 
ON [dbo].[IV10001] 
FOR DELETE 
NOT FOR REPLICATION 
AS 

DECLARE @ExtenderID char(15) 

select @ExtenderID = 'IVTRF_2'

SET NOCOUNT ON 

BEGIN 


DELETE A FROM EXT00101 A -- Strings
JOIN EXT00100 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR and B.Key_Strings_2 = C.LNSEQNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30300 D 
      where D.DOCTYPE = 3 and D.DOCNUMBR = C.IVDOCNBR and D.LNSEQNBR = C.LNSEQNBR)


DELETE A FROM EXT00102 A -- Dates
JOIN EXT00100 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR and B.Key_Strings_2 = C.LNSEQNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30300 D 
      where D.DOCTYPE = 3 and D.DOCNUMBR = C.IVDOCNBR and D.LNSEQNBR = C.LNSEQNBR)


DELETE A FROM EXT00103 A -- Numbers
JOIN EXT00100 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR and B.Key_Strings_2 = C.LNSEQNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30300 D 
      where D.DOCTYPE = 3 and D.DOCNUMBR = C.IVDOCNBR and D.LNSEQNBR = C.LNSEQNBR)


DELETE A FROM EXT00104 A -- Times
JOIN EXT00100 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR and B.Key_Strings_2 = C.LNSEQNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30300 D 
      where D.DOCTYPE = 3 and D.DOCNUMBR = C.IVDOCNBR and D.LNSEQNBR = C.LNSEQNBR)


DELETE B FROM EXT00100 B -- Mapping
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR and B.Key_Strings_2 = C.LNSEQNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30300 D 
      where D.DOCTYPE = 3 and D.DOCNUMBR = C.IVDOCNBR and D.LNSEQNBR = C.LNSEQNBR)
END
GO
SET QUOTED_IDENTIFIER OFF 
GO
SET ANSI_NULLS ON 
GO
 

Extender Detail Window Example - using IV TRANSFER FORM

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[IV10001_DELETE_IV_TRANS_FORM]') and OBJECTPROPERTY(id, N'IsTrigger') = 1)
drop trigger [dbo].[IV10001_DELETE_IV_TRANS_FORM]
GO

SET QUOTED_IDENTIFIER OFF 
GO
SET ANSI_NULLS OFF 
GO

CREATE TRIGGER [IV10001_DELETE_IV_TRANS_FORM] 
ON [dbo].[IV10001] 
FOR DELETE 
NOT FOR REPLICATION 
AS 

DECLARE @ExtenderID char(15) 

select @ExtenderID = 'IV TRANS FORM'

SET NOCOUNT ON 

BEGIN 


DELETE A FROM EXT00181 A -- Strings
JOIN EXT00185 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR and B.Key_Strings_2 = C.LNSEQNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30300 D 
      where D.DOCTYPE = 3 and D.DOCNUMBR = C.IVDOCNBR and D.LNSEQNBR = C.LNSEQNBR)


DELETE A FROM EXT00182 A -- Dates
JOIN EXT00185 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR and B.Key_Strings_2 = C.LNSEQNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30300 D 
      where D.DOCTYPE = 3 and D.DOCNUMBR = C.IVDOCNBR and D.LNSEQNBR = C.LNSEQNBR)


DELETE A FROM EXT00183 A -- Numbers
JOIN EXT00185 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR and B.Key_Strings_2 = C.LNSEQNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30300 D 
      where D.DOCTYPE = 3 and D.DOCNUMBR = C.IVDOCNBR and D.LNSEQNBR = C.LNSEQNBR)


DELETE A FROM EXT00184 A -- Times
JOIN EXT00185 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR and B.Key_Strings_2 = C.LNSEQNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30300 D 
      where D.DOCTYPE = 3 and D.DOCNUMBR = C.IVDOCNBR and D.LNSEQNBR = C.LNSEQNBR)


DELETE A FROM EXT00180 A -- Lines
JOIN EXT00185 B ON A.PT_Window_ID = B.PT_Window_ID and A.PT_UD_Key = B.PT_UD_Key
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR and B.Key_Strings_2 = C.LNSEQNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30300 D 
      where D.DOCTYPE = 3 and D.DOCNUMBR = C.IVDOCNBR and D.LNSEQNBR = C.LNSEQNBR)


DELETE B FROM EXT00185 B -- Line Mapping
JOIN deleted C ON B.Key_Strings_1 = C.IVDOCNBR and B.Key_Strings_2 = C.LNSEQNBR
WHERE B.PT_Window_ID = @ExtenderID and not exists(select 1 from IV30300 D 
      where D.DOCTYPE = 3 and D.DOCNUMBR = C.IVDOCNBR and D.LNSEQNBR = C.LNSEQNBR)
END
GO
SET QUOTED_IDENTIFIER OFF 
GO
SET ANSI_NULLS ON 
GO
 

You will need to test the triggers for your window to be sure that the concept of checking the Open (or History) table does work for the particular posting code. You should also have the Table Link or SQL Trigger to cleanup when the records are removed from History.

Hope you find this useful. Thanks Konrad for the idea.

David

Microsoft Dynamics GP Source Code Program for Asia Pacific

David Musgrave — Tue, 09 Feb 2010 01:00:00 GMT

I have some fantastic news for developing partners in the Asia Pacific region. The Microsoft Dynamics GP Source Code Program is finally available for Asia Pacific.

Before Microsoft acquired Great Plains, there was a source code program available for partners worldwide. When Microsoft completed its acquisition of Great Plains the program was suspended. Existing Source Code partners would continue to have access to source code, but no new partners could sign up.

Eventually, the program was restarted. Initially only available to North American partners, but later it was also opened to Partners in the LATAM (Latin American) and EMEA (Europe, Middle East & Africa) regions. Partners in the Asia Pacific region had not been able to get access.... until now.

If you wonder what the benefits of having access to the Source Code is, please have a read of my previous post on the topic:

Do I need access to Microsoft Dynamics GP Source Code?

Here is the PartnerSource link for the documentation for the program:

Source Code Program for Microsoft Dynamics GP - Asia Pacific
https://mbs.microsoft.com/partnersource/worldwide/asiapacific/partneressentials/mspp/SourceCodeProgramGP_APAC

If you have any questions, email gpsource@microsoft.com.

I am really excited as this is something I have been pushing for for a number of years and it is finally here.

David

See you at Microsoft Dynamics Convergence 2010

David Musgrave — Mon, 08 Feb 2010 01:00:00 GMT

Fantastic News. I am going to my first Convergence conference and, even better, I will be presenting 2 concurrent sessions with my partner in crime, Mariano Gomez.

Back in November, Mariano and I presented together at the Microsoft Dynamics GP Technical Conference 2009 and it was a huge success.

So now, we get a chance to do it again at the Microsoft Dynamics Convergence 2010. Details on our sessions will be posted later.

Please see the video below for details of some of the great volunteering opportunities that will be happening at Convergence.

This is going to be a fantastic opportunity to catch up with members of the Dynamics GP community. Mark Polino will be back presenting his Tips session.

Check out Mariano's announcement post on his blog.

Looking forward to seeing you in Atlanta (24^th - 27^th April 2010).

David

Fixing missing Note Index values

David Musgrave — Fri, 05 Feb 2010 01:00:00 GMT

A recent newsgroup post asked about how to fix the error message shown below from occurring when clicking the Attach button on the Note window for a record level note.

"The note ID has not been set."

The cause of the message is that the 'Note Index' value for the Transaction or Master record has not been set and so remains at zero.

The post Understanding Notes and the Note Index field explains how the Note Index is used and where the next Note Index comes from. It also explains how cross linked notes can occur. This post will discuss missing Note Index values and how they can occur.

The usual cause is because the data has been imported in some way and the import process did not populate the 'Note Index' field. Depending on what the import process actually is, you might need to log this issue with support so that it can be fixed.

Also, If you can make this problem occur for a master record or transaction newly entered via the user interface, then there is a bug in the code for that window and you will need to log this issue with the developer.

So, once there is data with a missing Note Index value, how can we fix it.... The answer is "easily".

My friend, Robert Cavill, provided me with a script he had created which can scan a table for missing 'Note Index' values. The script updates the table with the next Note Index for the company. It does so by using the existing DynamicsGP stored procedure: smGetNextNoteIndex. This AssignNoteIndex.sql script is attached to the bottom of this post. You just need to specify the table name to process by editing the value at the top of the script.

Before using AssignNoteIndex.sql, I would suggest running the script in the Knowledge Base (KB) article Cross-linked or incorrect notes indexes in Microsoft Great Plains (KB 872678) . This will ensure that the Note Index values used are higher than any existing values. The FindMaxNoteIndex.sql script from this KB is also attached to the bottom of this post.

Should you make regular use of the sample company Fabrikam (TWO database), I would also suggest running the FindMaxNoteIndex.sql script on this database as well. This is especially worthwhile if you have third party products that have added sample data.

The AssignNoteIndex.sql script and the FindMaxNoteIndex.sql script are available from the attachment at the bottom of this post. They can be executed against any company database.

For other posts on the topic of Notes and OLE Attachments see the following posts:

Understanding Notes and the Note Index field

OLE Attachments and Record Notes

All about the Dexterity OLE Container

Copying Record Notes and OLE Attachments between Companies

I hope you find these scripts useful.

David

The "Right" Way to Maximize the Growing Number of Online Resources for Microsoft Dynamics GP

David Musgrave — Thu, 04 Feb 2010 01:00:00 GMT

My friend Victoria Yudin (MVP) has written a great article which has been posted on the MSDynamicsWorld.com site.

The article: The "Right" Way to Maximize the Growing Number of Online Resources for Microsoft Dynamics GP, discusses the best methods to get help from the online resources and Microsoft Dynamics GP community. The main tips she mentions are:

Be specific and thorough in describing your problem.
Try to find the answer yourself first.
Be a smart "buyer".
Be considerate.

However, you will need to read her article to get the details. It is well worth the time. You can also check out Victoria's post from her blog:

Maximizing Dynamics GP online resources

Note: To read the entire article, you will need to sign up for a free account, if you don't have one already.

I am a firm believer in helping people help themselves. I am happy to point people in the right direction after they have done their own research on a topic. This way they learn how to find the answers themselves and get a much better understanding of the problem and the subsequent solution.

Thank you Victoria.

David

Limitations of Dexterity Table Triggers

David Musgrave — Wed, 03 Feb 2010 01:00:00 GMT

"Why doesn't my Dexterity table trigger fire when the table is changed."

I have heard this question asked a number of times and so I thought I would highlight some of the possible reasons for the trigger failing to fire. Some of the reasons can be resolved by coding, while other reasons are a limitation in the way Dexterity table triggers work and cannot be resolved from inside Dexterity.

Dexterity triggers are client side triggers which work from inside the current instance of the Dexterity application. They can only "see" what happens in the that instance of the application. A Dexterity table trigger does not involve anything at the database level, there will not be a SQL Server trigger registered.

Dexterity table triggers are registered against a particular table and can be set as application wide (by using a 0 for the second parameter below) or restricted to a single form. You can register multiple triggers to have triggers restricted to multiple forms. They are registered for specific table event(s).

The syntax for the registration of Dexterity table triggers is shown below:

Trigger_RegisterDatabase(anonymous(table table_name), form form_name , table_operations, script processing_procedure {, tag})

where table_operations can be any of the following operations (add the constants together when more than one operation is needed):

TRIGGER_ON_DB_READ (1)
TRIGGER_ON_DB_READ_LOCK (2)
TRIGGER_ON_DB_ADD (4)
TRIGGER_ON_DB_UPDATE (8)
TRIGGER_ON_DB_DELETE (16)

Note: the value of the constant is shown above in parenthesis.

For trigger to fire, the table event must:

Be a successful table event (no errors at the database level).
Occur using a table buffer which has the trigger registered against it.
Be one of the operations defined when the trigger was registered.

For tables not in the Dynamics.dic, you will need to use cross dictionary triggers using the Trigger_RegisterDatabaseByName() function.

So based on the information above, the following situations could cause a table change to occur without the table trigger firing:

The table change is made by an external (non-Dexterity) application. This can be any external program such as eConnect, Integration Manager, Business Portal, directly at the table level by a SQL Administrator or a third party customisation.
The table change is made from within the Dexterity application by a non-Dexterity method. This could be a call to a SQL stored procedure, use of pass through SQL scripts or even access via customisation written using Visual Studio Tools or Visual Basic for Applications (VBA) and ActiveX Data Objects (ADO). Any method which does not use Dexterity commands with a table buffer.
The Dexterity customisation with the table trigger is not installed on the application instance running.
The table event is using Dexterity commands, but is using a different table buffer to the one against which the trigger is registered.
The table event is using Dexterity commands on the same table buffer, for different operations for which the trigger is registered.
The table event is using a different table definition to the one against which the trigger is registered. In Dexterity it is possible to have duplicated table definitions referring to the same physical table. This could be to facilitate opening the table twice at the same time or could be because a customisation needs access to a table in a 3^rd party product and it was better to duplicate the table rather than use pass through sanScript via the execute() function.

The first two of the reasons are situations where a Dexterity table trigger is not going to work as Dexterity just never "sees" the table change being made. The only method available for these situations is to use a trigger at the SQL Server level.

The third reason is easily solved by installing the customisation chunk file on all workstations. It was only in this list to highlight the importance of all workstations having all the same dictionaries installed.

The fourth reason is important, but can be coded around. Using an unrestricted (no form specified) table trigger is not recommended as it could cause the trigger to fire at unexpected times. (For example: when posting, running table maintenance or history removal.) So most developers use one or more table triggers restricted to specific forms. However, those triggers will only fire if the table event occurs in the specified form's table buffer. If the code on that form uses a function or procedure to perform the table event and the form's table buffer is not passed as a parameter, a separate instance of the table buffer will be created for the scope of the function or procedure. As this separate table buffer is not the same as the form's table buffer, a form restricted table trigger will not fire. In this situation it might require an unrestricted table trigger to be used.

Note: If using an unrestricted table trigger, it is good practice to make sure it will not fire at unexpected times. It is possible to use additional triggers to enable and disable the trigger using the tag value captured when the table trigger was registered. For example, the trigger could be disabled immediately after registration and then enabled just before the function or procedure described above is executed and then disabled again afterwards. This is a similar method to the Three Trigger Technique.

The fifth reason is not so common, but can also be changed in the code. It is most likely to happen when using a read trigger. The get table command does not apply a lock and so is covered by the TRIGGER_ON_DB_READ operation. The change table and edit table commands do apply locks and so are covered by the TRIGGER_ON_DB_READ_LOCK operation. If you wish to capture any read event (with or without a lock) you need to use TRIGGER_ON_DB_READ + TRIGGER_ON_DB_READ_LOCK. The Add, Update and Delete events are self explanatory.

The sixth reason is also rare, but can happen. There are times, let's say for reporting on data from a 3^rd party product where we need to be able to access a table from another dictionary as though it is in our dictionary. In this case the methods using execute() and pass through sanScript are not going to work. So we can create a Combined Dictionary (KB 930350 ) and transfer the table definition (without referenced resources) to our dictionary. This technique works well for accessing the data, but if we make any changes using our duplicate table definition, the trigger on the original table will not see it. You would need to also register a cross dictionary trigger on the duplicate table.

Let me know if this is helpful.

David

04-Feb-2010: Added additional reason (Duplicate table definitions) for table triggers to fail.

Dexterity Training in Orlando (May 10th to 14th 2010)

David Musgrave — Tue, 02 Feb 2010 01:00:00 GMT

Another opportunity to learn the foundations of Developing for Dynamics GP is now available.

Microsoft Dynamics GP's core application user interface is developed using the Dexterity development system. Knowledge of Dexterity and therefore how Dynamics GP's internals work is fundamental to developing customisations and products that work with Dynamics GP.

Even if you don't plan on developing with Dexterity and wish to use Visual Basic for Applications (VBA) or Visual Studio Tools for Microsoft Dynamics GP, this course is well worth attending. Having an understanding of how the GP windows are constructed, how table buffers and ranges work, and how to call functions and procedures are just a few of the things that is useful to all developers regardless of the development tool used.

Leslie Vail (MVP) will be instructing the 5 day Dexterity class to be held in Orlando, Florida, USA during the week starting on the 10^th of May 2010. Leslie is an excellent trainer with awesome application and development knowledge and experience. The course will be fun and extremely educational.

The course is organised through the partner Integrated Business Group (http://www.ibgnet.com/). If you would like more information, contact the training coordinator, Roxanna Alvarez, ralvarez@ibgnet.com or at +1 (407) 677-0370.

This course is a must for anyone wanting to get started in the Dynamics GP development world. See point 3 in my blog posting on How to get started with Dexterity.

For more info see Leslie's blog post: DEXTERITY class May 10th in Orlando

If you enjoyed the troubleshooting session on the Support Debugging Tool for Microsoft Dynamics GP at the Microsoft Dynamics GP Technical Conference 2009, let it be known that Leslie worked with Mariano and myself into the small hours of the morning to make the session as great as it was.

Thanks Leslie.

David

What causes an "All call stacks are in use" error?

David Musgrave — Mon, 01 Feb 2010 01:00:00 GMT

As a Dexterity developer you might have come across the following error:

All call stacks are in use. Cannot start script.

This post will describe what call stacks are (from a Dexterity perspective), how they are used and what causes this error to be generated.

Note: I will start by saying that this topic is covered very well in the Dexterity Programmer's Guide (Volume 2, Part 5, Chapter 24) and also in the Dexterity Help file (search for "Call Stacks", then click on "described"). Thanks to Steve Kubis and the Dexterity documentation team.

A call stack is a mechanism for managing the processing of scripts. In programming terms, a call stack is a Last In First Out (LIFO) data structure that stores the state of a script (variables, next command to execute, etc.). When Script A calls a child Script B, the state of Script A is placed (or pushed) onto the call stack while Script B runs. When Script B is completed, the state is restored (or popped) back from the call stack and Script A continues running from just after the call to Script B.

When Dexterity calls global and form level functions and procedures, all the processing is handled on the single call stack. This can be visualised as a pile of paper sheets and as each new script runs a new sheet is placed onto the pile and then removed when that script is completed.

However, under certain circumstance Dexterity can execute code which requires its own call stack. To support this, the Dexterity system has eight (8) call stacks. One call stack is dedicated to background processing which leaves seven (7) call stacks for foreground use.

There are three types of processes which can start a new call stack being used:

Procedures that are called automatically by Dexterity, such as the global procedures Security and Pathname.
RW Functions called by Report Writer calculated fields as User Defined Functions.
run script commands which executes the script attached to the change event of the window field specified.

The problem with running out of call stacks and generating a call stack error is usually caused when developers over use the run script command. The two examples below will explain how the call stacks are used with the run script command:

Example 1: Script A

run script 'B';
run script 'C';

In example 1: when Script B is executed a second call stack is used. But once Script B is completed the call stack is no longer needed and the execution returns to the original call stack. Then Script C is executed in the second call stack. This sequential calling using the run script command only uses one additional call stack and so does not cause the error condition.

Example 2: Script A

run script 'B';

Example 2: Script B

run script 'C';

In example 2: when Script B is executed a second call stack is used. Script B in turn executes Script C and so uses a third call stack. This nested calling using the run script command uses an additional call stack for each nested call. As there are only seven call stacks available for foreground processing, you can only have six levels of nested run script commands.

The following diagram from the Dexterity manuals shows the Background call stack and the seven Foreground stacks. Note how the seven stacks are all used because of six nested run script commands.

If a 7^th nested run script command is called, an automatically executed procedure is called (by opening a form or table), or a report is run which calls a RW function; the system will have no call stacks available and so produce the error:

All call stacks are in use. Cannot start script.

One example I have seen of this issue was on a maintenance window which had nested run script commands to update fields on the window depending on other fields on the same window (for example: disabling fields depending on a checkbox). When the window used by itself there were no issues. However, when the window was opened by a drill down, there was at least one more run script command and the error occurred. This shows how using too many nested run script commands might not break the code all the time, but could cause issues when called by different methods.

It is recommended that developers don't nest run script commands more than 3 levels. This is should help avoid the issue from occurring. Other methods of avoiding the error include using functions and procedures rather than run script commands and using the run script delayed command. The run script delayed command starts the specified field change script after all foreground processing is complete and so does not use an additional call stack.

For a related post on this topic where this error is caused by Regional and Language settings see Janakiram's post below. The difference in the control panel settings must be altering the behaviour of the code in such a way to make it attempt to use one more call stack:

All Call stacks are in Use. Cannot Start script

Hope this information is useful.

David

Fixed Asset Integration error: "String was not recognized as a valid DateTime"

Dawn Langlie [MSFT] — Fri, 29 Jan 2010 09:00:00 GMT

I recently had a support case, running a Fixed Asset integration with Integration Manager, where we received the following error:

DOC 1 ERROR: System.FormatException: String was not recognized as a valid DateTime.
at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
at System.DateTime.Parse(String s, IFormatProvider provider)
at System.Convert.ToDateTime(String value, IFormatProvider provider)
at System.String.System.IConvertible.ToDateTime(IFormatProvider provider)
at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
at System.Data.SqlClient.SqlParameter.CoerceValue(Object value, MetaType destinationType)

The date format in both the source file and Microsoft Dynamics GP are set to MM/DD/YYYY. We verified that the regional settings are set to English (United States) and the Date format is MM/DD/YYYY. We also verified that the Server Properties in SQL are set to English (United States).

As this integration utilizes eConnect, we then looked at the Identity in the eConnect COM+ Application and this was a different user. eConnect will look at this user’s Regional Settings to find the Date format. We changed the Identity to the user that we verified Regional Settings for and the integration is now working without errors.

I hope this helps save time troubleshooting this error.

Dawn

Microsoft Dynamics GP 2010 Beta Released

David Musgrave — Thu, 28 Jan 2010 01:00:00 GMT

The Microsoft Dynamics GP 2010 Beta code has been released. This release, previously known as GP "11.0", is the largest release in Microsoft Dynamics GP history with a massive amount of development work and time going into it. It can be downloaded from PartnerSource using the link below:

Beta Download for Microsoft Dynamics GP 2010 (PartnerSource)

We are excited to announce the newest version to the Microsoft Dynamics GP platform: Microsoft Dynamics GP 2010. Microsoft Dynamics GP 2010 will focus on increasing depth and reach for core functionality, enriching integrations with the Microsoft Office system, extending external connections through Web Services, and ensuring faster Return on Investment (ROI) for customers. This release is the final data model planned for this release along with all the planned features shipping with Microsoft Dynamics GP 2010.

Here is a sampling of some other posts from around the blogsphere:

It is a GREAT Day! (from Pam @ Inside Dynamics GP)

Feature of the Day series (from Inside Dynamics GP team)
Note: This series will have more posts added over time, so please look in on a regular basis.

Microsoft Dynamics GP 2010 Beta Buzz (from Mariano @ Dynamics GP Blogster)

What's new in Microsoft Dexterity 11.0 (from Mariano @ Dynamics GP Blogster)

Inside Microsoft Dynamics 2010: Arabic Version of Dynamics GP 2010 “11”!!!! (Mohammad Daoud shows us how cool the Dexterity development environment is by translating to Arabic.)

I think you will all agree that we have an exciting year ahead.

David

PS: For information on how to translate Dexterity code, have a look at the Translating Dexterity Applications Series.

Removing Extender Data when deleting Transactions or Lines

David Musgrave — Wed, 27 Jan 2010 01:00:00 GMT

I was recently asked to assist a colleague with an Extender case. The problem was that Extender data was not being removed from the Extender SQL tables when its parent record was deleted.

The issue of Extender data being orphaned when the parent data is deleted is a known issue (KB 906242 see link below) and can be resolved fairly easily:

For Version 10.0 onwards you can use the Table Links feature (when editing an Extender object, from the menus select Options >> Table Links). This allows you to define a parent table so that Extender knows to remove the additional data when the parent record is deleted.
For Version 9.0 and before, your option was to use a SQL Trigger on the parent table's delete event to clean up the data. Examples of the triggers are included in the attached archive at the bottom of this article.

These techniques work well for Master records (Customers, Vendors, Items, etc.) but do not always work as desired for Transaction records.

The reason Transaction records are different is that they move from table to table as the document moves through the workflow. They move from Work to Open when posted and then from Open to History when fully applied or archived. Some transactions move straight from Work to History, but still have the same issue.

So if you place the Table Link or SQL Trigger on the Work table, when the transaction is posted and the record is added to the Open table and deleted from the Work table, the Extender data is deleted at the same time. In summary, this means that the Extender data is lost once the transaction is posted.

This issue is described in KB 967740 (see link below) and provides the solution to add the Table Link or the SQL Trigger to the History table so the data is only removed when the transaction gets removed from History.

This solution prevents the Extender data from being removed prematurely but it does not handle the situation when Transaction Lines or the entire Transaction is deleted by the user while it is still unposted and stored in the Work tables.

So what is needed in addition to the Table Link or SQL Trigger on the History table, is a method to handle when a transaction is deleted by the user from the Work table which will not be fired when the transaction is posted. This means we need to use events at the user interface instead of at the table level.

So we can use any of the customisation tools which work at the user interface. For our example we will use Visual Basic for Applications (VBA).

The concept behind the code is to use VBA to capture the delete line and delete transaction events via the Modal Dialogs and then use ActiveX Data Object (ADO) to open a connection to SQL Server and execute the appropriate Transact-SQL delete statements to remove the data from the appropriate tables.

Below is a list of the tables used to store data for normal Extender Windows:

Dexterity Technical Name	SQL Table	Description
PT_Extender_Window_Key_Values	EXT00100	Stores the Mapping between the parent data's keys and the Extender key
PT_User_Window_Field_Strings	EXT00101	Stores String values based on the Extender key
PT_User_Window_Field_Dates	EXT00102	Stores Date values based on the Extender key
PT_User_Window_Field_Numbers	EXT00103	Stores Numeric (Currency & Integer) values based on the Extender key
PT_User_Window_Field_Times	EXT00104	Stores Time values based on the Extender key

Below is a list of the tables used to store data for Extender Detail Windows:

Dexterity Technical Name	SQL Table	Description
PT_UD_Detail_Window_Lines	EXT00180	Stores the mapping for the line sequence numbers for the Extender key
PT_Detail_Window_Dates	EXT00181	Stores String values based on the Extender key and line sequence
PT_Detail_Window_Dates	EXT00182	Stores Date values based on the Extender key and line sequence
PT_Detail_Window_Numbers	EXT00183	Stores Numeric (Currency & Integer) values based on the Extender key and line sequence
PT_Detail_Window_Times	EXT00184	Stores Time values based on the Extender key and line sequence
PT_Extender_Detail_Window_Key_Values	EXT00185	Stores the Mapping between the parent data's keys and the Extender key

The example code uses the Inventory Transfer Entry (IV_Transfer_Entry) window and includes two different examples. This is so we can demonstrate the code needed for both normal Extender Windows and Extender Detail Windows.

Adding normal Extender Windows against the Transaction Line and Transaction Header

Extender Windows.xml - Contains Extender Settings for the Extender Windows IVTRF_1 & IVTRF_2.
IV_Transfer_Entry (Extender Windows).Package - Contains VBA code to delete Extender data when deleted by the user.
Extender Windows.sql - Contains example SQL Triggers on work tables - For reference only, should not be used for live system.
Adding an Extender Detail Window against the Transaction Lines

Extender Detail Window.xml - Contains Extender Settings for the Extender Detail Window IV TRANSFER FORM.
IV_Transfer_Entry (Extender Detail Window).Package - Contains VBA code to delete Extender data when deleted by the user.
Extender Detail Window.sql - Contains example SQL Trigger on work table - For reference only, should not be used for live system.

NOTE: The SQL scripts provided above are examples to show how SQL triggers can be used to remove Extender data when a record is deleted from a SQL table. They are coded to trigger on the Work tables to demonstrate the issue when posting a transaction removes the data. They should NOT be used in a live system. They can be modified to work with history tables if required for v9.00 systems, but for v10.00 systems we suggest using the Table Links feature with the History table.

Example v10.0 Extender Settings and VBA code for the Inventory Transfer Entry (IV_Transfer_Entry) window is attached to the bottom of this article.

For related information please see the following Knowledge Base (KB) articles:

The associated Extender record is not deleted when you delete a Microsoft Great Plains record (KB 906242)

Extender data is removed from the EXT00100 table when a batch is posted in Microsoft Dynamics GP 10.0 (KB 967740)

The bottom line is that for the system to work 100%, you need both VBA (or equivalent) code to remove the Extender data when the user deletes the transaction from the Work tables AND you need to have a Table Link (or SQL Trigger) on the History table to handle if the transaction is removed from history.

Post a comment if you find this information and sample code useful.

David

01-Feb-2010: Added extra explanations about SQL Trigger Scripts included in attachment.

Announcing Microsoft Dynamics Convergence 2010

David Musgrave — Tue, 26 Jan 2010 01:00:00 GMT

OK, so I am a little late in announcing Microsoft Dynamics Convergence 2010, but I was away for a while. However, this is the first article about the upcoming conference on this blog. So ....

Join us for Convergence 2010 in Atlanta, April 24^th - 27^th. Attending Convergence provides you ample opportunities to network with a targeted group of business professionals and to discover how you can get the most value from your Microsoft Dynamics solutions – and how to increase your business potential. Register today to take advantage of US$300 per person Early Bird savings off the regular registration fee. For more information, click here.

The video below is a overview of Convergence Atlanta 2010:

For more videos about Convergence and other subjects important to the Dynamics, go visit the Microsoft Dynamics Community channel on youtube.

Here are some other posts from around the blogsphere:

Register now for Convergence 2010 in Atlanta (from Mariano Gomez)

Convergence 2010 Atlanta Registration Starts Today! (from Mark Polino)

Volunteering at Convergence 2010 (from Mark Polino)

Make sure you register sooner rather than later.

David

Increasing the Microsoft Dynamics GP 10.0 Homepage Font Size

David Musgrave — Mon, 25 Jan 2010 01:00:00 GMT

I was recently asked if it was possible to change the fonts on the Microsoft Dynamics GP 10.0 Homepage. A customer had asked if they could be made a little bit bigger as they were hard to read at the resolution that the machine was running at.

So I decided to have a quick look to see what was needed. The homepage itself for the current user is stored in the temp folder for that user, for example:

C:\Users\<username>\AppData\Local\Temp\HomePage.xml

This xml file is generated by Dynamics GP depending on the homepage settings in the application. It in turn references the XML Style Sheet (.xsl) file in the Background subfolder of the application installation folder.

C:\Program Files\Microsoft Dynamics\GP\Background\HomePage.xsl

This style sheet file then references the Cascading Style Sheet (.css) file in the same folder.

C:\Program Files\Microsoft Dynamics\GP\Background\HomePage.css

It is this HomePage.css file which contains the definition for the fonts used on the homepage.

Note: Examples of the already altered files for HomePage.css and PreviewPane.xsl are contained in the attachment at the bottom of this post.

If you wish to make the changes yourself rather than use the files provided.... Then make a copy of this original HomePage.css file and call it HomePage Normal.css. This is your backup to restore the default settings if necessary.

You can then make a second copy of the file and call it HomePage Big.css. Then open the HomePage Big.css with Notepad.exe and perform a series of find and replaces to change the font sizes by increasing them by 2 points.

You need to start with the largest font size and work down to the smallest:

Find String Replace String

13pt 15pt

12pt 14pt

11pt 13pt

10pt 12pt

9pt 11pt

8pt 10pt

Find String	Replace String
13pt	15pt
12pt	14pt
11pt	13pt
10pt	12pt
9pt	11pt
8pt	10pt

Once the changes are complete and file saved, you can delete the original HomePage.css file and copy HomePage Big.css and rename it as HomePage.css. To restore, just delete HomePage.css and copy HomePage Normal.css and rename it as HomePage.css.

The AreaPage.xsl file used when displaying the Area Pages also uses the HomePage.css file, so the font changes are applied here as well.

The PreviewPane.xsl has some font definitions and is used for the preview pane when looking at lists. It can be altered in the same way to produce PreviewPane Normal.xsl and PreviewPane Big.xsl files.

Note: Examples of the already altered files for HomePage.css and PreviewPane.xsl are contained in the attachment at the bottom of this post.

For a related post, Mohammad Daoud has an article which shows how the homepage and be "removed" by replacing it with a logo image if desired:

How to change GP 10.0 Homepage??

Hope you find this useful.

David

VBA - Determining the company name selected in the Company Login window

Patrick Roth [MSFT] — Fri, 22 Jan 2010 10:30:00 GMT

A question came up a while back where the user wanted to know what company the user was logging into in order to give them a message depending on the company selected.

The specific issue was that VBA cannot get the name of the company from the DDL (drop down list), it can only give you the position. Also the position in the list doesn't have any bearing on the company id of the company displayed. It is just an ordered list by alphanumeric sorting by the Company Name field.

The question wasn't specific to when exactly the user needed to see this message. When initially I read the question and based on how it was posed, it seems they wanted to know right when the DDL was selected. But it could have been when the OK button was pressed and it also could be just after they log in.

Given that the technique used would be different, I will present both solutions.

Situation 1

For this solution, we will assume that the programmer needs to know the company after the user logs into Dynamics GP in order to give them some information or take a specific action.

The easiest way to do this it to use a Window_AfterClose() event on the Company Login window (Switch_Company form in Dexterity) and use the UserInfoGet object to retrieve the company logged in.

In the VBA code sample below, before the window opens we see what the current company is. We could either being logging into Dynamics GP for the first time or just switching companies. And if switching companies, we might press Cancel or just re-select the same company. So by checking the previous logged in company and comparing we only show our message if the company we are going to really changed.

VBA Code for Company Login window

Option Explicit
Dim oldcompany As String

Private Sub Window_AfterOpen()
    oldcompany = UserInfoGet.CompanyName
End Sub

Private Sub Window_AfterClose()
    If oldcompany <> UserInfoGet.CompanyName Then
        MsgBox "You have just logged into the company " + UserInfoGet.CompanyName
    End If
End Sub

Situation 2

While the solution given for the first situation is OK if we want to let the user log in, it is possible that we might want to give a message before the GP login occurs. Or potentially stop the user from being able to log into the company for some specific reason.

If that is the case, we would then need to know the selected company before the Company Login window was closed. The only way to do that is to know the company name selected in the Company DDL.

Because we cannot directly read the name from the Company DDL field, we have to pull the information directly from SQL in the order that Dynamics is displaying it. Then we'd know the company being selected and could act upon that.

VBA Code for Company Login window 2

Option Explicit

Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim cmd As New ADODB.Command

Dim CurrentUser As String

Private Sub Window_AfterOpen()
    Set cn = UserInfoGet.CreateADOConnection
    'Switch to DYNAMICS db as that is where our query will run and not the current company
    cn.DefaultDatabase = "DYNAMICS"
    CurrentUser = UserInfoGet.UserID
    cmd.ActiveConnection = cn
End Sub

Private Sub Window_AfterClose()
    Set cn = Nothing
    Set rs = Nothing
    Set cmd = Nothing
End Sub

Private Sub Company_AfterUserChanged()
    Dim sql As String
    Dim i As Integer

    sql = sql + "    select a.CMPANYID as CompanyNumber,b.CMPNYNAM as CompanyName from SY60100 a"
    sql = sql + "    join SY01500 b"
    sql = sql + "        on a.CMPANYID = b.CMPANYID"
    sql = sql + "   where a.USERID = '" & CurrentUser & "'"
    sql = sql + "       order by b.CMPNYNAM"

    cmd.CommandText = sql

    Set rs = cmd.Execute
    If Not (rs.EOF And rs.BOF) Then
        'Nice if we could just jump to the current record
        'but looks like we have to loop through them.
        'We start on the first record in the recordset
        'so loop n-1 times to get to the correct one.
        'We don't need to read the entire recordset,
        'just to the one we've selected.  It is Company - 1
        'because we start on the first record
        For i = 1 To Company - 1
            rs.MoveNext
        Next

        MsgBox "You have chosen company: " + Trim(rs(1).Value)
    End If
End Sub

Depending on your exact needs; either one of these solutions might work for you or at least get you started.

Best Regards,

Patrick

Developer Support

Vote for Barbie as a Computer Engineer

David Musgrave — Thu, 21 Jan 2010 01:00:00 GMT

Now is the time for action!!!

We need you.... OK, Mattel does.

It seems that Barbie is looking for a new career and we need your help to vote for her to be a Computer Engineer.

I found out about this career vote by reading my friend's, Catherine Eibner, funny post on the topic: Barbie as a Computer Engineer?. I am surprised that there is no option for Backhoe Operator after reading her article.

So please vote by clicking on the badge above or visiting: http://www.barbie.com/vote/ before the 12^th February when the results will be published.

David