Page 1 of 212

Tech Tuesday: Lookup Templates within Node Builder

This week our Senior Technical Consultant, Chris Hanson, has provided us with a Tech Tuesday video highlighting the lookup templates within Node Builder.

There are some pre-built templates inside of Node Builder
that allow you to streamline your work when adding in the needed logic to any
node you are creating. The video below shows how to make use of one of those templates
on a partially

Continued here:
Tech Tuesday: Lookup Templates within Node Builder

June 3, 2014 · Frank Hamelly MCP-GP MCT MVP · No Comments
Tags: , , , , , , ,  · Posted in: Blogs I Follow Total Views: 83

Support Debugging Tool Customization #11 – Restricting Salesperson ID for Existing Customers

Recently there was a support request in the forum,

http://social.microsoft.com/Forums/en-US/partnerdynamicsgp/thread/139b760a-5c63-4b16-b480-79f0a569075c

where the requirement was as below.

We want to modify the Customer Maintenance window to make the Salesperson ID field uneditable for existing records only.  I went into Modifier and made this field uneditable but that makes it uneditable each time the window opens.  We want the field to be available when creating a new customer – we just don’t want users to be able to change that field for existing customers.

In this article, I am going to post the details of how this customization can be achieved using Support Debugging Tool.

Version Information

Dynamics GP : 11.0.1914 (SP2)

Support Debugging Tool : 11.00.0016

Screenshots of the Configuration

Trigger #1 – Resource Tab

image

This is a trigger on the Display Existing Record Change – After Original on the Customer Maintenance window. This trigger will check if both the Customer Number and the Salesperson ID fields are populated with data, and if these fields are populated with values, we will lock the Salesperson ID field and disable the corresponding lookup button for the Salesperson ID field.

Trigger #1 – Customization Script

in string IN_OldValue;
in string IN_NewValue;
out boolean OUT_Condition;
 
OUT_Condition = false;
 
if isopen(form RM_Customer_Maintenance) then
	if not empty('Customer Number' of window 'RM_Customer_Maintenance' of form 'RM_Customer_Maintenance') and 
		not empty('Salesperson ID' of window 'RM_Customer_Maintenance' of form 'RM_Customer_Maintenance') then
		lock field 'Salesperson ID' of window 'RM_Customer_Maintenance' of form 'RM_Customer_Maintenance';
		disable field 'Lookup Button 6' of window 'RM_Customer_Maintenance' of form 'RM_Customer_Maintenance';
		OUT_Condition = true;
	else
		unlock field 'Salesperson ID' of window 'RM_Customer_Maintenance' of form 'RM_Customer_Maintenance';
		enable field 'Lookup Button 6' of window 'RM_Customer_Maintenance' of form 'RM_Customer_Maintenance';
		OUT_Condition = true;
	end if;
end if;

Trigger #2 – Resource Tab

image

This is a trigger on the Display Existing Record Change – After Original on the Customer Address Maintenance window. This trigger will check if the Customer Number, Address Code and the Salesperson ID fields are populated with data, and if these fields are populated with values, we will lock the Salesperson ID field and disable the corresponding lookup button for the Salesperson ID field.

Trigger #2 – Customization Script

in string IN_OldValue;
in string IN_NewValue;
out boolean OUT_Condition;
 
OUT_Condition = false;
 
if isopen(form RM_Customer_Address) then
	if not empty('Customer Number' of window 'RM_Customer_Address' of form 'RM_Customer_Address') and 
		not empty('Address Code' of window 'RM_Customer_Address' of form 'RM_Customer_Address') and
		not empty('Salesperson ID' of window 'RM_Customer_Address' of form 'RM_Customer_Address') then
		lock field 'Salesperson ID' of window 'RM_Customer_Address' of form 'RM_Customer_Address';
		disable field 'Lookup Button 8' of window 'RM_Customer_Address' of form 'RM_Customer_Address';
		OUT_Condition = true;
	else
		unlock field 'Salesperson ID' of window 'RM_Customer_Address' of form 'RM_Customer_Address';
		enable field 'Lookup Button 8' of window 'RM_Customer_Address' of form 'RM_Customer_Address';
		OUT_Condition = true;
	end if;
end if;

Configuration File Location

You can download the configuration for this requirement here.

Reference

Take a look at the article below which summarizes the usage of Support Debugging Tool with some real life examples. Great compilation by David! http://blogs.msdn.com/b/developingfordynamicsgp/archive/2011/08/05/using-the-support-debugging-tool-with-real-life-examples.aspx

You can get more details about the Support Debugging Tool at http://aka.ms/SDT

Hope this helps the community…

Until next post!

March 13, 2012 · veeyeskay · One Comment
Tags: , , , , , ,  · Posted in: Accounts Receivables, Customizations, Dynamics, Great Plains, Support Debugging Tool Total Views: 2,221

Dynamics GP 2010 R2 Feature of the Day: Ability to Copy Email Messages

Why this feature is cool! Our latest release will allow the end-user to create dynamic email messages that automatically pull in information from the document that is being emailed based on the substitute fields inserted into accompany email message. When creating the email message using substitute fields an end-user will need to assign a Document Type. An end-user may want to copy the same email message to other Document types (for example, an email message might be created for the Document type Sales Quote and they may want to use same message along with fields for Sales Order).

Read the rest here:
Dynamics GP 2010 R2 Feature of the Day: Ability to Copy Email Messages

March 18, 2011 ·  · No Comments
Tags: , , , , , , ,  · Posted in: Blogs I Follow Total Views: 262

Item Lookup – Display Item Description Instead of Item Short Description

I got several requests to replace Item Short Description in Items Lookup with Item Description, below is the package: Item Lookup Package Item Lookup Package Regards, — Mohammad R. Daoud MVP – MCT MCP, MCBMSP, MCTS, MCBMSS +962 – 79 – 999 65 85 me@mohdaoud.com www.mohdaoud.com

See more here:
Item Lookup – Display Item Description Instead of Item Short Description

January 31, 2011 ·  · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 869

Do I have to use those "Z-" currency IDs in GP?

I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the “Z-“.

See the original post here:
Do I have to use those "Z-" currency IDs in GP?

December 13, 2010 · Mariano Gomez · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 249

Enabling a Report Writer document as a Word Template

Ok, this is directly or indirectly a Report Writer subject, but nonetheless a topic related to Report Writer. In this example, I take the General Posting Journal transaction document and enable it under Word Templates

Read the rest here:
Enabling a Report Writer document as a Word Template

December 7, 2010 · Mariano Gomez · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 323

Quick Tip: Solving "Do you want to Save?" dialog appearing after VBA customization

Have you ever used Modifier and Visual Basic for Applications (VBA) to add an additional field to a window?

October 18, 2010 · David Musgrave · No Comments
Tags: , , , , , , ,  · Posted in: Blogs I Follow Total Views: 241