Changing the Hyperspace property for a lookup button added with Modifier

It sounds like some word out of Captain Kirk's vocabulary, but for Dexterity developers Hyperspace is a well known property that allows a Dexterity-based application to run the change script for a push button, i.e., a lookup button, without moving the focus from the currently-selected field. For example, you won't want the 'Customer Number' field on the Customer Maintenance window to execute it's change script before you have selected a customer from the Customer Lookup window as the lookup button is clicked... that's what Hyperspace does, it prevents such situations by keeping the focus on the 'Customer Number' field until a customer ID is returned from the lookup window into the field.

The problem is, this property is locked down for push button controls added with Modifier, and while you cannot edit the push button change script with Modifier, you may still want to trigger off such controls with Dexterity code. This is pretty common for customizations where you don't want to create an alternate versions of a GP form, but require a control placed directly on the GP form in order to call your own Dexterity code (see my article Developing Microsoft Dynamics GP hybrid integrating applications).

So, here is the workaround for changing the Hyperspace property of a push button control added with Modifier:

1. Add the push button control to your Modified window. In my example I will be using the sopCustomerItemMnt form. The following illustrates the changes made:



2. Save your modified window and return to Microsoft Dynamics GP. Open the Customization Maintenance window and locate the sopCustomerItemMnt. Click the Export button to export the modified window to a package file. The following is the content of exported package file:



= Form "sopCustomerItemMnt"
{
 Datatypes
 {
  Datatype "Lookup"  
  {
   Control "PushButton"
   DefaultDown "00000"
   DefaultMouseOver "00000"
   DefaultUp "00000"
   Prompt ""
   PromptDown ""
   PromptMouseOver ""
   StaticType "Mixed"
   ~ItemImages
   {
    PictItem "00001"    
    {
     Item "Field_Lookup_PB_Up"
    }
   }
  }
  Datatype "UPC_Code"  
  {
   AllowOddLength "false"
   Control "String"
   Format ""
   KeyableLength "31"
   StorageLength "32"
  }
 }
 Fields
 {
  Field "Lookup"  
  {
   ArraySize "0"
   Datatype "(L) Lookup"
   LookupForm ""
   PhysicalName ""
  }
  Field "UPC_Code"  
  {
   ArraySize "0"
   Datatype "(L) UPC_Code"
   LookupForm ""
   PhysicalName ""
  }
 }
 Windows
 {
  = Window "sopCustomerItemMnt"
  {
   Fields
   {
    WindowControl "(L) Lookup"    
    {
     Alignment "center"
     Appearance "2D Border"
     BackColor "System - Button Face"
     Border "true"
     ButtonStyle "GraphicOnly"
     Cancel "false"
     ControlType "PushButton"
     Default "false"
     Editable "true"
     EndTransaction "false"
     Field "(L) Lookup"
     Font "System (generic)"
     FontBold "false"
     FontColor "System - Button Text"
     FontItalic "false"
     FontUnderline "false"
     HyperSpace "false"
     LinkedLookup "10002"
     LinkedPrompt "0"
     Pattern "(none)"
     PatternColor "White"
     PositionLeft "567"
     PositionTop "186"
     ResizeHoriz "StayLeft"
     ResizeVert "StayTop"
     SizeHeight "20"
     SizeWidth "18"
     TabStop "true"
     Tag "10003"
     Tooltip ""
     UseUniqueHelp "true"
     Visible "true"
     ZOrder "81"
     Zoom "false"
    }
    WindowControl "(L) UPC_Code"    
    {
     Alignment "left"
     Appearance "2D Border"
     AutoComplete "false"
     AutoCopy "false"
     BackColor "System - Window Background"
     Border "true"
     ControlType "String"
     DisableLookup "false"
     Editable "true"
     Field "(L) UPC_Code"
     Font "System (generic)"
     FontBold "false"
     FontColor "System - Window Text"
     FontItalic "false"
     FontUnderline "false"
     LinkedFormat "0"
     LinkedLookup "0"
     LinkedPrompt "10001"
     Password "false"
     Pattern "(none)"
     PatternColor "White"
     PositionLeft "408"
     PositionTop "186"
     ReadingOrder "LeftToRight"
     Required "false"
     ResizeHoriz "StayLeft"
     ResizeVert "StayTop"
     SavedOnRestart "false"
     SetChangeFlag "true"
     SizeHeight "20"
     SizeWidth "160"
     TabStop "true"
     Tag "10002"
     Tooltip ""
     UseUniqueHelp "true"
     Visible "true"
     ZOrder "80"
     Zoom "false"
    }
    WindowPrompt "10001"    
    {
     Alignment "left"
     Appearance "3D Highlight"
     BackColor "System - Button Face"
     Border "true"
     Font "System (generic)"
     FontBold "false"
     FontColor "System - Button Text"
     FontItalic "false"
     FontUnderline "false"
     Pattern "(none)"
     PatternColor "White"
     PositionLeft "328"
     PositionTop "186"
     ReadingOrder "LeftToRight"
     ResizeHoriz "StayLeft"
     ResizeVert "StayTop"
     SizeHeight "20"
     SizeWidth "80"
     Text "UPC Code"
     Visible "true"
     ZOrder "79"
     Zoom "false"
    }
   }
   LastTag "10003"
  }
 }
}

3.Perform a search for "Hyperspace". Replace the property value from false to true. Save the package file. In the above sample package file content, I have highlighted the Hyperspace property in red.

4. Use the Customization Maintenance window to reimport the package file. This should be all! Now your lookup button's hyperspace property is set to true.

Warning: this method of changing the Hyperspace property of a push button is not supported by Microsoft and must be performed by a developer who understands the implications.

Until next post!

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

Comments

Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

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

Image
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-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more