We use a TON of user defined fields in our apps and I've never found this to be true.
otrans.update(), otrans.refresh() and otrans.clear() all work quite reliably in my experience.
Are you referring to:
(1) checkbox##, character##, number## fields within a tables native to the application, or
(2) FKV, multi-key FKV or Sub table views added to the application (using data tools), or
(3) are you talking about fields in UD## tables brought into the application via a subroutine, or
(4) are you talking about fields in normal data views (but not native to the application) that you brought in within a subroutine?
Only for (3) and (4) can my tired brain envision this not working - particularly if you didn't bring in the necessary support assemblies and correctly define the adapters.
For (3) & (4) once you've verified the assemblies and adapters are correctly defined, verify that each apapter supports the .clear() method.
If it doesn't it will likely support something similarly named.
You might then have to set up a Sub to trap the application's primary adapter otrans.clear() method (after execution) and within it invoke the non-native adapter methods essentially equivalent to .clear() method in order to clear your in-sub-routine defined views (and display of those values in your custom controls).
Without knowing the app customized and being able to read your custom code, it is only a series of educated guesses.
Do you get any execution error messages when running the customized app after hitting clear?
If you hit clear twice does the additional data then clear? (All clues.)
Have you run full tracing while performing the action? If so, what did it say? (Are there NO references to your 'custom fields' during the final BO method clear action?)
Using an 'ipso-facto' approach to sifting through trace logs, what BO method calls UPDATED your 'custom fields'? That might give you a clue to what is missing in the code (or the way you brought in the tables to the app) that is at the root of your problem.
Wouldn't you give your eye-teeth for a REAL code editor (with set point/break point control, step in/out mode, and variable watch box capability) instead of the lame homegrown thing Epicor passes off as a code editor? (...That doesn't match the power of the original, practically FREE MS-Visual Basic editor/compiler of the mid 90's???)
They really blew it not licensing Visual studio for a relative song and including it (optimized) for this purpose.
Rob
otrans.update(), otrans.refresh() and otrans.clear() all work quite reliably in my experience.
Are you referring to:
(1) checkbox##, character##, number## fields within a tables native to the application, or
(2) FKV, multi-key FKV or Sub table views added to the application (using data tools), or
(3) are you talking about fields in UD## tables brought into the application via a subroutine, or
(4) are you talking about fields in normal data views (but not native to the application) that you brought in within a subroutine?
Only for (3) and (4) can my tired brain envision this not working - particularly if you didn't bring in the necessary support assemblies and correctly define the adapters.
For (3) & (4) once you've verified the assemblies and adapters are correctly defined, verify that each apapter supports the .clear() method.
If it doesn't it will likely support something similarly named.
You might then have to set up a Sub to trap the application's primary adapter otrans.clear() method (after execution) and within it invoke the non-native adapter methods essentially equivalent to .clear() method in order to clear your in-sub-routine defined views (and display of those values in your custom controls).
Without knowing the app customized and being able to read your custom code, it is only a series of educated guesses.
Do you get any execution error messages when running the customized app after hitting clear?
If you hit clear twice does the additional data then clear? (All clues.)
Have you run full tracing while performing the action? If so, what did it say? (Are there NO references to your 'custom fields' during the final BO method clear action?)
Using an 'ipso-facto' approach to sifting through trace logs, what BO method calls UPDATED your 'custom fields'? That might give you a clue to what is missing in the code (or the way you brought in the tables to the app) that is at the root of your problem.
Wouldn't you give your eye-teeth for a REAL code editor (with set point/break point control, step in/out mode, and variable watch box capability) instead of the lame homegrown thing Epicor passes off as a code editor? (...That doesn't match the power of the original, practically FREE MS-Visual Basic editor/compiler of the mid 90's???)
They really blew it not licensing Visual studio for a relative song and including it (optimized) for this purpose.
Rob
--- On Wed, 12/10/08, tpaulavicius <tpaulavicius@...> wrote:
From: tpaulavicius <tpaulavicius@...>
Subject: [Vantage] How to clear custom field, when 'clear' button is clicked
To: vantage@yahoogroups.com
Date: Wednesday, December 10, 2008, 4:41 PM
Hi,
When you click 'clear', custom fields are not cleared.
How to make, that on 'clear' they are cleared?
Thanks,
Tom