Ok then, thanks for you help Harry. I've stopped working on that 'cause I couldn't find any solution that was suitable. We've forward this modification to our Axapta consultant and we'll see what they can come up with.

A trip to India! Nice! Enjoy the sun! Take it easy!

Bye!

Steeve...

-----Message d'origine-----
De : Harry [mailto:[EMAIL PROTECTED] Envoyé : 7 octobre, 2003 15:27
À : [EMAIL PROTECTED]
Objet : RE: RE : RE : [development-axapta] Adding new dataSource to Form


hi Steeve,

I am in new zealand.

going on 2 weeks leave to India and looking forward to sunshine.

I have got no idea why Axapta people dont do it manually on InventTableForm.
But thats not a surprise, there are a lot of issues like this (different
problems) in Axapta especially in manufacturing and planning.

regards

harry deshpande

-----Original Message-----
From: Steeve Gilbert [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 8 October 2003 1:51 a.m.
To: [EMAIL PROTECTED]
Subject: RE : RE : [development-axapta] Adding new dataSource to Form


Btw, Thanks for all the help Harry!


About the InnerJoin/OuterJoin issues in the InventTable form.  Why didn't
they just manually edit the XPO (as you said) to put InventItemLocation (the
wanna be outerJoin) before all the other InnerJoin?  That way, they could
set InventItemLocation as an OuterJoin instead of an InnerJoin and skip the
dirt work of adding a dump record in InventItemLocation.

I'll continue to work on that with the clues you gave me.  I'll give you
news if there's any progress.

Have nice day! (or night, where ever you are)

Steeve...

-----Message d'origine-----
De : Harry [mailto:[EMAIL PROTECTED]
Envoyé : 6 octobre, 2003 18:04
À : [EMAIL PROTECTED]
Objet : RE: RE : [development-axapta] Adding new dataSource to Form

hi Steeve!

This is a bug in Axapta. Outer join has to be before inner join. Which means
the new joined table on 'InventTransOrder' will have to be between
inventTrans and inventDim. Now you cannot do this unless you export the form
and change the seqeuence of the datasource manuall by editing the xpo file.

Incidentally if you look at form inventTable, the table 'InventItemLocation'
has an inner join on InventTable, logically (and practically) there is no
need for records to be in 'InventItemLocation for each and every item. But
because of the above limitation of outer join they had to make it an inner
join. So the functionality is modified so that whenever you insert a record
in item table, corresponding blank record is inserted into
'inventItemLocation'. (which is why the when one imports  data in
inventTable and forgets about InventItemLocation, the items in inventTable
go bin-laden and you have play George Bush for a long time to find out what
has happened)*s*

The reason why item name is not displayed on inventOnHandItem is different.
If you put a debug on the form, you will see that the recId for the
inventSum table is 0 (since this form shows records in a roundabout way).
Since there is no record in inventOnHandTable (i think) the inner join on
inventTable does not work, which is why the item name is not displayed.

You are correct, its not the newQuery() on inventSum table. The related
method seems to be modifyQuery() on class InvnetDimCtrl_FrmOnHand.

regards

harry




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/








Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/




Yahoo! Groups Sponsor ADVERTISEMENT
Click Here!


Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Reply via email to