OK, thanks for the reply. I actually figured my issue out. I was trying
to add checkboxes to an existing grid using the form load method in the
script editor. When I tested it with my administrative login and very
little data, it worked fine. However, the users database has a lot more
data and when they opened up the form, the default buyer had existing
data in the grid so it was erroring out when try to add checkboxes to an
already populated grid. I simply pulled my code out of the form load and
created a new procedure that I called from the Initialize method and
that seemed to work.
Scott
to add checkboxes to an existing grid using the form load method in the
script editor. When I tested it with my administrative login and very
little data, it worked fine. However, the users database has a lot more
data and when they opened up the form, the default buyer had existing
data in the grid so it was erroring out when try to add checkboxes to an
already populated grid. I simply pulled my code out of the form load and
created a new procedure that I called from the Initialize method and
that seemed to work.
Scott
--- In vantage@yahoogroups.com, Karl Dash <dashkarl@...> wrote:
No, I never did and then the reason why it was necessary went away.
-Karl
________________________________
From: altyrocks alty_rocks@...
To: vantage@yahoogroups.com
Sent: Tuesday, March 6, 2012 1:36 PM
Subject: [Vantage] Re: Buyers Workbench Customization
Hello. Did you ever find a resolution to this problem? I'm having the
same issue when I try to deploy my Buyer Workbench. I made the
customization under my administrative login but when the users try to
access it, it throws up the "Unhandled exception has ....." Key not
found. Parameter name: key error.
In vantage@yahoogroups.com, Karl Dash dashkarl@ wrote:
My management has asked me to gray-out the "Generate Purchase Orders"
action within the Buyer's Workbench for the SRM module. Buyer's
Workbench (Epicor.Mfg.UI.App.BuyerWorkbenchEntry.BWForm) in turn uses a
process call to (Epicor.Mfg.UI.POSuggEntry) for new suggestions. The
user can check off the suggestions to be turned into PO's and use the
Actions menu to do so.
This application is now to be made available for viewing purposes to
people other than buyers and I need to disable their ability to
misbehave. I put the following into the script editor for
(Epicor.Mfg.UI.POSuggEntry):
//**************************************************
// Custom VB.NET code for POSuggEntryForm
// Created: 4/6/2007 11:26:10 AM
//**************************************************
Imports System
Imports System.Data
Imports System.Diagnostics
Imports System.Windows.Forms
Imports System.ComponentModel
Imports Microsoft.VisualBasic
Imports Epicor.Mfg.UI
Imports Epicor.Mfg.UI.FrameWork
Imports Epicor.Mfg.UI.ExtendedProps
Imports Epicor.Mfg.UI.FormFunctions
Imports Epicor.Mfg.UI.Customization
Imports Epicor.Mfg.UI.Adapters
Imports Epicor.Mfg.UI.Searches
Imports Epicor.Mfg.BO
// ** Added these two Namespace imports
Imports System.Reflection
Imports Infragistics.Win.UltraWinToolbars
Module Script
// ** Wizard Insert Location - Do Not Remove 'Begin/End Wizard Added
Module Level Variables'
// Begin Wizard Added Module Level Variables **
// End Wizard Added Module Level Variables **
// Add Custom Module Level Variables Here **
// variables for Menu/Tools
Private BaseToolbarsManager As
Infragistics.Win.UltraWinToolbars.UltraToolbarsManager
Sub InitializeCustomCode()
// ** Wizard Insert Location - Do not delete 'Begin/End Wizard Added
Variable Intialization' lines
// Begin Wizard Added Variable Intialization
// End Wizard Added Variable Intialization
// Begin Custom Method Calls
// set up Menu/Tools event handlers
GetBaseToolbarsManagerRef()
// End Custom Method Calls
End Sub
Sub DestroyCustomCode()
// ** Wizard Insert Location - Do not delete 'Begin/End Wizard Added
Object Disposal' lines **
// Begin Wizard Added Object Disposal
// End Wizard Added Object Disposal
// Begin Custom Code Disposal
BaseToolbarsManager = Nothing
// End Custom Code Disposal
End Sub
// Code for capturing Menu/Tool events (Thanks to Nick M.)
Private Sub GetBaseToolbarsManagerRef()
Use reflection to get a reference to the baseToolbarsManager object
Dim objBaseToolbarsManager As Object =
GetType(Epicor.Mfg.UI.App.POSuggEntry.POSuggEntryForm).InvokeMember("bas\
eToolbarsManager",BindingFlags.GetField Or BindingFlags.NonPublic Or
BindingFlags.Instance, Nothing, POSuggEntryForm,Nothing)
BaseToolbarsManager =
CType(objBaseToolbarsManager,Infragistics.Win.UltraWinToolbars.UltraTool\
barsManager)
AddHandler BaseToolbarsManager.BeforeToolDropdown, AddressOf
BaseToolbarsManager_BeforeToolDropdown
End Sub
// Bind to this method to change the name of the "New Parent" and "New
Child" buttons
Private Sub baseToolbarsManager_BeforeToolDropdown(ByVal sender As
Object, ByVal e As
Infragistics.Win.UltraWinToolbars.BeforeToolDropdownEventArgs)
If (e.Tool.Key = "ActionsMenu") Then
BaseToolbarsManager.Tools("Generate Purchase
Orders...").SharedProps.Enabled = False
End If
End Sub
End Module
-----------------------------------------
The error I'm getting when ckicking on the actions menu is "Unhandled
exception has ....." Key not found. Parameter name: Key.
Any help?
Thanks,
-Karl
[Non-text portions of this message have been removed]