Cool Mellisa. You're on the right track.
I'm still pathetically weak in BPMs relative to VB client customizations.
I don't think to add such a customization would noticably impact client application performance (many do if you're not careful - as I've learned the hard way!)
If you do want to try it via customization, it sounds pretty straightforward.
Add a textbox control to the appropriate form & link it to the sub part relationship table - specifically to whatever they call the sub part field (PartNum I would guess).
Name the textbox control txtSubPart & if you don't want it displayed (just want to trigger your messagebox) given it a hidden property. (Also a good idea is to give it a -X,-Y location coordinate as sometimes even hidden controls 'bleed through'!)
The code is then pretty straighforward:
Private Sub txtSubPart_TextChanged(ByVal Sender As Object, ByVal Args As
System.EventArgs) Handles txtSubPart.TextChanged
'// ** Place Event Handling Code Here **
If len(txtSubPart.text)<> 0 then
MessageBox.Show("Possible subsitute part exists")
End If
End Sub
As long as at least one sub part exists for the PartDtl just entered, textbox txtSubPart will be populated with the 1st (row 0) possibility and the subroutine will detect the value change in txtSubPart.
The len(txtSubPart.text) <> 0 test serves to purposes:
1. If no subPart exists, you won't get a row(-1) triggered application error.
2. If the user switches to a new PartDtl record with no potential subPart, the change in the textbox value (from a non-null to null string) won't trigger the messagebox to pop up inappropriately.
That should work. You can make it fancier (perhaps add the newly selected or entered PartDtl.PartNum to your displayed message and even add the row(0) first valid subPartNum if you'd like).
I'd start simple though. Less likely to blow up later after an upgrade (or degrade client app performance).
Hope that helps.
Rob
I'm still pathetically weak in BPMs relative to VB client customizations.
I don't think to add such a customization would noticably impact client application performance (many do if you're not careful - as I've learned the hard way!)
If you do want to try it via customization, it sounds pretty straightforward.
Add a textbox control to the appropriate form & link it to the sub part relationship table - specifically to whatever they call the sub part field (PartNum I would guess).
Name the textbox control txtSubPart & if you don't want it displayed (just want to trigger your messagebox) given it a hidden property. (Also a good idea is to give it a -X,-Y location coordinate as sometimes even hidden controls 'bleed through'!)
The code is then pretty straighforward:
Private Sub txtSubPart_TextChanged(ByVal Sender As Object, ByVal Args As
System.EventArgs) Handles txtSubPart.TextChanged
'// ** Place Event Handling Code Here **
If len(txtSubPart.text)<> 0 then
MessageBox.Show("Possible subsitute part exists")
End If
End Sub
As long as at least one sub part exists for the PartDtl just entered, textbox txtSubPart will be populated with the 1st (row 0) possibility and the subroutine will detect the value change in txtSubPart.
The len(txtSubPart.text) <> 0 test serves to purposes:
1. If no subPart exists, you won't get a row(-1) triggered application error.
2. If the user switches to a new PartDtl record with no potential subPart, the change in the textbox value (from a non-null to null string) won't trigger the messagebox to pop up inappropriately.
That should work. You can make it fancier (perhaps add the newly selected or entered PartDtl.PartNum to your displayed message and even add the row(0) first valid subPartNum if you'd like).
I'd start simple though. Less likely to blow up later after an upgrade (or degrade client app performance).
Hope that helps.
Rob
--- On Wed, 11/26/08, melissa hietala <kevmel822@...> wrote:
From: melissa hietala <kevmel822@...>
Subject: Re: [Vantage] 8.03.4XX BPM Question
To: vantage@yahoogroups.com
Date: Wednesday, November 26, 2008, 9:21 AM
Thanks for the response Rob. I have actually already created a FK view which displays the subparts if there are any. I am basically trying to add on to this with a popup message as an initial alert to notify the user that there is indeed a substitute part. Any ideas?
Thanks!
 Dustin Biniek
UMC, Inc.
DustinB@ultramc. com
____________ _________ _________ __
From: Robert Brown <robertb_versa@ yahoo.com>
To: vantage@yahoogroups .com
Sent: Wednesday, November 26, 2008 12:03:22 AM
Subject: Re: [Vantage] 8.03.4XX BPM Question
Melissa,
I can't remember what table sub part relationships are stored in, but I'd be surprised if it isn't already natively accessible in Eng WB - or at worst, VERY easy to add as an Foreign Key View.
If it is sufficient, just add a text box control to the form and display the sub part.
Rob
--- On Tue, 11/25/08, melissa hietala <kevmel822@yahoo. com> wrote:
From: melissa hietala <kevmel822@yahoo. com>
Subject: [Vantage] 8.03.4XX BPM Question
To: vantage@yahoogroups .com
Date: Tuesday, November 25, 2008, 6:25 PM
I would like to setup a scenario in the Engineering Workbenc h and I am thinking it needs to be accomplished by utilizing a BPM. What I would like to do is when a user enters a material line in the Engineering Workbench, and there is a "substitute" part from part maintenance for the material that they select, I would like a messagebox to popup notifying the user that there is a substitute for the selected part.  Has anybody tried to do something like this? Is using a BPM the way to accomplish this?
Thanks in advance!
 Dustin Biniek
UMC, Inc.
DustinB@ultramc. com
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]