No better in .4xx than in .3xx unfortunately.
Â
Definitely read the user guide. It has no index but has a wealth of code examples as you flip through it.
Â
For SetExtendedProperties:
Â
Set this up in the Script Editor:
Â
 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
Â
  '// End Custom Method CallsÂ
          SetExtendedProps()
Â
End Sub
Â
The create the SetExtendedProperties Subroutine: (This one allows you to mark an OP complete in Job Entry after adding the appropriately table.field link ustom checkbox control.)
Â
Private Sub SetExtendedProps()
   Dim edvJO As EpiDataView = CType(oTrans.EpiDataViews("JobOper"), EpiDataView)
     Â
   If edvJO.dataView.Table.Columns.Contains("OpComplete") Then
  Â
       edvJO.dataView.Table.Columns("OpComplete").ExtendedProperties("ReadOnly") = False
  Â
   End If
End Sub
Â
It creates the mechanism for a non-public epidataview into the JobOper table, tests to be sure it is there (by making sure the field "OpComplete" is there), and then uses the .ExtendedProperties("ReadOnly") attribute definer to set read only to false for OP Complete.
Â
If you have imposed db level table security or user role based security on any Business Objects (adapters) they may get in the way. (Most people don't do that however.)
Â
VB.net is actually quite powerful. The weakness is that it puts all the processing load in the client application - so if you go crazy (doing things better done on the server using BPMs) you can really slow down application performance.
Â
It is an excellent tool however for simply cleaning up each form to show only what is needed in you process (or adding things not natively shown).
Â
You can also pull in data via odbc from non-Vantage data sources and use it in Vantage apps.
Â
customButton controls can be set up to launch non-vantage apps... (We use a lot of web based applications that were developed for our old system... Once we repointed them at Vantage data, we added buttons to appropriate apps and pass a url with say the part number on the Vantage form - or job number, PO number etc., - and up pops our web apps already loaded with the proper context. You can also reuse alreay loaded apps by getting their processID name from the O/S and simply passing it a new variable to load - much like Vantage allows righ click menu launched 'chained' apps that stay in contect as you select a new record in a list view out of the originating app.
Â
Like anything else... Use a nutcracker to munch on a nut and sledgehammer to knock down a wall. No single tool is the 'right' tool for all needs.
Â
...I give you a week at the extraordinary pace you learn and you'll be a .NET junkie for life! :)
Â
RobÂ
Â
Â
Definitely read the user guide. It has no index but has a wealth of code examples as you flip through it.
Â
For SetExtendedProperties:
Â
Set this up in the Script Editor:
Â
 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
Â
  '// End Custom Method CallsÂ
          SetExtendedProps()
Â
End Sub
Â
The create the SetExtendedProperties Subroutine: (This one allows you to mark an OP complete in Job Entry after adding the appropriately table.field link ustom checkbox control.)
Â
Private Sub SetExtendedProps()
   Dim edvJO As EpiDataView = CType(oTrans.EpiDataViews("JobOper"), EpiDataView)
     Â
   If edvJO.dataView.Table.Columns.Contains("OpComplete") Then
  Â
       edvJO.dataView.Table.Columns("OpComplete").ExtendedProperties("ReadOnly") = False
  Â
   End If
End Sub
Â
It creates the mechanism for a non-public epidataview into the JobOper table, tests to be sure it is there (by making sure the field "OpComplete" is there), and then uses the .ExtendedProperties("ReadOnly") attribute definer to set read only to false for OP Complete.
Â
If you have imposed db level table security or user role based security on any Business Objects (adapters) they may get in the way. (Most people don't do that however.)
Â
VB.net is actually quite powerful. The weakness is that it puts all the processing load in the client application - so if you go crazy (doing things better done on the server using BPMs) you can really slow down application performance.
Â
It is an excellent tool however for simply cleaning up each form to show only what is needed in you process (or adding things not natively shown).
Â
You can also pull in data via odbc from non-Vantage data sources and use it in Vantage apps.
Â
customButton controls can be set up to launch non-vantage apps... (We use a lot of web based applications that were developed for our old system... Once we repointed them at Vantage data, we added buttons to appropriate apps and pass a url with say the part number on the Vantage form - or job number, PO number etc., - and up pops our web apps already loaded with the proper context. You can also reuse alreay loaded apps by getting their processID name from the O/S and simply passing it a new variable to load - much like Vantage allows righ click menu launched 'chained' apps that stay in contect as you select a new record in a list view out of the originating app.
Â
Like anything else... Use a nutcracker to munch on a nut and sledgehammer to knock down a wall. No single tool is the 'right' tool for all needs.
Â
...I give you a week at the extraordinary pace you learn and you'll be a .NET junkie for life! :)
Â
RobÂ
Â
--- On Thu, 11/20/08, nmtaylor1969 <n.taylor@...> wrote:
From: nmtaylor1969 <n.taylor@...>
Subject: [Vantage] Re: Removal Of Job Parts In 8.03.305K
To: vantage@yahoogroups.com
Date: Thursday, November 20, 2008, 3:43 PM
I hope the customisation environment in 8.03.4xx is better than it is
in 8.03.305. It is truly terrible in my version. :o(
I have only done a few simple customisations before, but I understand
what you have done here. However, where do I find out about the
SetExtendedProperti es routine ? Is this a standard method defined in
the object browser ?
I do have the Epicor tools book ( which is actually very good ), so I
guess I should probably go and read this, right...!?
Nick
--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
wrote:
>
> Nick,
>
> Yes: Job Entry form: Job Details/Materials/ Details tab.
>
> In customization mode, open your Tools menu and add a checkbox
control to the form (somewhere near the native qty required control).
Link this checkbox to the 'JobMtl' table - 'IssuedComplete' field.
>
> Make sure the control is enabled and add some appropriate screen
label using the tools menu (so the user knows what the checkbox is
for).
>
> As I'm typing this, I'm pretty sure the field is natively
read/write so you likely don't have to mess with a
SetExtendedProperti es subroutine.
>
> (If I'm worng about that, let me know & I'll shoot you the code...
It should only be a few lines long.)
>
> You can also pull the same trick on the Op Detail tab if you want
to force an OP to be complete. With that one, I think you'll have to
add a FKV's and or subtable views into JobOpr & JobOpDtl. I think
almost assuredly you will also require a SetExtendedProperti es
subroutine up (as I think it is natively read only).
>
> Happy .NETing {;o
>
> Rob
>
>
> --- On Thu, 11/20/08, nmtaylor1969 <n.taylor@.. .> wrote:
>
> From: nmtaylor1969 <n.taylor@.. .>
> Subject: [Vantage] Re: Removal Of Job Parts In 8.03.305K
> To: vantage@yahoogroups .com
> Date: Thursday, November 20, 2008, 2:01 AM
>
>
>
>
>
>
> Thanks Rob...
>
> I think I will have a go at the first option although my
> customisation skills are limited...! :o(
>
> Should I modify the job entry form for this...?
>
> Thanks,
>
> Nick
>
> --- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
> wrote:
> >
> > Nick,
> >
> > With a .Net customization you can enable the the control to mark
> the job material detail as either open or issued complete (a
> checkbox) using a SetExtendedProperti es subroutine.
> >
> > This allows you to manually mark the requirement as fulfilled
(even
> though it wasn't) - but it won't clean up PartDtl, or PartWhse &
> PartBin allocation records (since you've thwarted the normal
process
> the business object methods expecting to be followed).
> >
> > If that is unpalletable, make sure you Part (job material
> detail/requirement part) isn't set to 'use whole units'. Then you
can
> at least enter some exceedingly small qty per amount (0.000001) and
> it will only minimally throw things off until you formally close
the
> job.
> >
> > Rob
> >
> > --- On Wed, 11/19/08, nmtaylor1969 <n.taylor@ .> wrote:
> > From: nmtaylor1969 <n.taylor@ .>
> > Subject: [Vantage] Removal Of Job Parts In 8.03.305K
> > To: vantage@yahoogroups .com
> > Date: Wednesday, November 19, 2008, 10:29 AM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Can anyone assist with the following little problem
> please...?
> >
> >
> >
> > We have a part on a job method that has transactions already
logged
> >
> > against it. In fact, there were a number of issues and a number
of
> >
> > returns from the line now leaving a zero balance. We want to
remove
> the
> >
> > line from the job due to an engineering change but we seem to be
> unable
> >
> > to do this.
> >
> >
> >
> > I had hoped that we could just close the line, or set its
quantity
> to
> >
> > zero but this is not possible. I have also tried deleting the
line
> but
> >
> > I cannot do this because of the associated transactions.
> >
> >
> >
> > Can anybody tell me how I stop the line creating demand ??
> >
> >
> >
> > Many thanks,
> >
> >
> >
> > Nick
> >
>
[Non-text portions of this message have been removed]