Brief overview...
We have two forms. First form has five tabs and hits a total of three tables
(primary is CustTable). Second form has two tabs and hits one table
(CustTableAux). Both forms have a button linking them to the other form
(CustTableAux uses CustAccount from CustTable as a key). Both forms have a
button that invokes the same X++ code with a parameter of CustAccount.
If I modify data on the CustTableAux form, click the button that sends me to
the CustTable form, modify data and then invoke my X++ functionality life is
good. The lookups into the database within the X++ code all return the
desired values. However...
If I modify data on the CustTable form, click the button that sends me to
CustTableAux form, modify data and invoke my X++ code life is not so good.
The data modifications that have been made on the CustTable form are not
persisted to the database and the X++ code does not pick up the changes.
Note that the process is the same for both forms - after modifying a field
value we tab off of the field before invoking any other functionality in
order to allow the data to be persisted.
When going through the Axapta Developer Documentation there's a section on
caching that indicates there can be mis-matches if a table is cached and
there is X++ code that is running selects on that table.
My CustTable's caching is set to NotInTTS and the CustTableAux is *not*
cached.
My current working assumption, not yet tested, is that by turning off
caching on CustTable it will all magically work.
Am I missing something that will be obvious to people who have been doing
this longer than I have?
rjsjr
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
