You don't indicate if you want this data transfer/update to occur globally on all qualified orders/invoices (which could be accomplished with a .p file scheduling as a recurring task - say every 10 minutes)
- OR if you if you want it to occur only when using a specific application (like Invoice Entry) via a Customization.
Assuming a specific app is suitable to be the trigger (and since you didn't specify which one - so I can't check to see what tables are natively available) you need to go into developer mode, open the app you plan to use as the trigger point for the update and then do one of the 3 things that follow (1st being the easiest if it is viable, 3rd being the most complex to code as a last resort):
1. open data tools and look to see if the two tables you want to move data from/to are already accessible by the app. If they are, use the one of the wizards to select an appropriate trigger to update the data as you desire. This will create the shell of the subroutine to perform the data update. (The event EpiViewNotification is a good all purpose event trigger as it 'fires off' you subroutine right after the app has loaded all the necessary table records.)
2. Again, via data tools, see if you can bring in the necessary tables by creating Foreign Key Views (possibly several as a chain) through natively app supported table key columns that allow you to add the 'missing' table (and it's adapter) and make it accessible to the app. If you can do this, you will still need to determine a suitable trigger to do the update (just like in 1. above.)
3. If you can't find suitable table links to get your 'missing' table visible to the app via Foreign Key Views (2.), you'll need to write explicit VB code to bring the table view into the app as a dataview entity. Use Object explorer to determine which DLLs need to be set up as Custom Assembly (via the assembly viewer) and to find the vb code example you can then use to establish the needed table as a dataview within the app. The subroutine (or Function?... can't remember at the moment) code will need to include all necessary methods to ID the underlying table name and names of the columns of interest, and also find the appropriate record row (view a search method) that correlates to the existing records loaded into the app. Once this is coded properly and compiles with no errors, again, you will still need to determine a suitable trigger to do the update (just like in 1. above) and add the subroutine code (via one of the wizards, if suitable, to at least rapidly create
the 'shell' code of the Subroutine). You will have to add appropriate event handler code 'manually' to actually perform the data update you desire.
I suggest you spring for the Epicor Tools User Guide as it is far superior to the (pathetically inadequate) Help topics on Customizations. It contains many useful coded examples that will, at some point, save you significant time on a customization.
It is really a shame Epicor doesn't 'get' the true power of .NET: Go on Microsoft's TechNet site to see thousands of examples of why MS clearly DOES 'get it'... They have thousands of custom C, C++, VBscript, VB, etc., code examples for anyone to copy and use freely.
Epicor could easily set up a customization library containing exported xml files that document Epicor's customer's successful customizations. I would bet most Vantage users would be willing to post their customizations to share with others (as they would then have access to other customers shared customizations).
99.9% of customizations are simply tailoring of the standard apps to suit the particular business and user comfort levels (just making them easier to use by removing non-value-added options not required - or by 'relabeling' fields and app controls to conform to the company culture based common terminology in use).
Only rarely are customizations true 'intellectual property' that give the author's company a true startegic advantage over its competition - and truly adds significantly increased functionality non-existant in standard vantage. These rare customizations users might be understandably be hesitant to share.
Sharing the rest (with Epicor providing the support mechanism) is to everyone's advantage.
Rob Brown
Don Kollmann <dkollmann@...> wrote:
________________________________
Hi Gang,
Is it possible to pass a udnumberfield from order.dtl to
invc.dtl.numberfield
I need to pass the data from an order to the invoice and I am not sure
where to begin.
I am testing this on 8.03 403 b
Thank You
Don .
<http://geo.yahoo.com/serv?s=97359714/grpId=20369/grpspId=1705007183/msg
Id=60790/stime=1195568710/nc1=4507179/nc2=3848641/nc3=5008828>
[Non-text portions of this message have been removed]
---------------------------------
Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.
[Non-text portions of this message have been removed]
- OR if you if you want it to occur only when using a specific application (like Invoice Entry) via a Customization.
Assuming a specific app is suitable to be the trigger (and since you didn't specify which one - so I can't check to see what tables are natively available) you need to go into developer mode, open the app you plan to use as the trigger point for the update and then do one of the 3 things that follow (1st being the easiest if it is viable, 3rd being the most complex to code as a last resort):
1. open data tools and look to see if the two tables you want to move data from/to are already accessible by the app. If they are, use the one of the wizards to select an appropriate trigger to update the data as you desire. This will create the shell of the subroutine to perform the data update. (The event EpiViewNotification is a good all purpose event trigger as it 'fires off' you subroutine right after the app has loaded all the necessary table records.)
2. Again, via data tools, see if you can bring in the necessary tables by creating Foreign Key Views (possibly several as a chain) through natively app supported table key columns that allow you to add the 'missing' table (and it's adapter) and make it accessible to the app. If you can do this, you will still need to determine a suitable trigger to do the update (just like in 1. above.)
3. If you can't find suitable table links to get your 'missing' table visible to the app via Foreign Key Views (2.), you'll need to write explicit VB code to bring the table view into the app as a dataview entity. Use Object explorer to determine which DLLs need to be set up as Custom Assembly (via the assembly viewer) and to find the vb code example you can then use to establish the needed table as a dataview within the app. The subroutine (or Function?... can't remember at the moment) code will need to include all necessary methods to ID the underlying table name and names of the columns of interest, and also find the appropriate record row (view a search method) that correlates to the existing records loaded into the app. Once this is coded properly and compiles with no errors, again, you will still need to determine a suitable trigger to do the update (just like in 1. above) and add the subroutine code (via one of the wizards, if suitable, to at least rapidly create
the 'shell' code of the Subroutine). You will have to add appropriate event handler code 'manually' to actually perform the data update you desire.
I suggest you spring for the Epicor Tools User Guide as it is far superior to the (pathetically inadequate) Help topics on Customizations. It contains many useful coded examples that will, at some point, save you significant time on a customization.
It is really a shame Epicor doesn't 'get' the true power of .NET: Go on Microsoft's TechNet site to see thousands of examples of why MS clearly DOES 'get it'... They have thousands of custom C, C++, VBscript, VB, etc., code examples for anyone to copy and use freely.
Epicor could easily set up a customization library containing exported xml files that document Epicor's customer's successful customizations. I would bet most Vantage users would be willing to post their customizations to share with others (as they would then have access to other customers shared customizations).
99.9% of customizations are simply tailoring of the standard apps to suit the particular business and user comfort levels (just making them easier to use by removing non-value-added options not required - or by 'relabeling' fields and app controls to conform to the company culture based common terminology in use).
Only rarely are customizations true 'intellectual property' that give the author's company a true startegic advantage over its competition - and truly adds significantly increased functionality non-existant in standard vantage. These rare customizations users might be understandably be hesitant to share.
Sharing the rest (with Epicor providing the support mechanism) is to everyone's advantage.
Rob Brown
Don Kollmann <dkollmann@...> wrote:
________________________________
Hi Gang,
Is it possible to pass a udnumberfield from order.dtl to
invc.dtl.numberfield
I need to pass the data from an order to the invoice and I am not sure
where to begin.
I am testing this on 8.03 403 b
Thank You
Don .
<http://geo.yahoo.com/serv?s=97359714/grpId=20369/grpspId=1705007183/msg
Id=60790/stime=1195568710/nc1=4507179/nc2=3848641/nc3=5008828>
[Non-text portions of this message have been removed]
---------------------------------
Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.
[Non-text portions of this message have been removed]