[development-axapta] simple report question

2005-01-03 Thread Danny Gaethofs







Dear all,

I want to realize that a control field in a programmable section 
repeats 5 times on the first line of my report.

To test this I created a simple programmable section containing the 
field ItemId.

I send the item record from the fetch() method.

Using a while loop in my fetch method and a counter I want the item 
to be printed 5 times on the first line of my report.

I am not able to succeed, instead the item prints on five lines.

Can someone explain me how I can realize this.

Axapta 3.0 SP3.

Danny
















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.










[development-axapta] Checkbox printShippingLabel

2004-12-21 Thread Danny Gaethofs







Dear all,

I have added a new checkbox to the form SalesEditLines. 

CheckBox is named: printCertitificate, property AutoDeclaration =
yes, AllowEdit = No, Skip = yes


I made sure that several methods on the Class SalesFormLetter are 
modified:
- ClassDeclaration: add printCertificate
- initParameters: set value for printCertificate

I added two new methods on the class:
- posPrintCertificate: set position
- printCertificate: return the value of printCertificate

Made sure that methods on Form SalesEditLines are modified:
- ClassDeclaration: add printCertificateChoice
- closeOk: added parameter printCertificateChoice
- rearrange: added parameter printCertificate.value
- run: retrieve value printCertificateChoice from container

- active() method on datasource SalesParmTable: added setting of 
checkbox value (printCertificate.value(printCertificateChoice)


Now I notice when I select the checkbox it is deselected immediately 
afterwards. It has something to do with the setting of 
printCertificate from the beginning. When I set it to yes in the 
classFormLetter.dialog the opposite occurs. When I deselect the 
checkbox it is enabled.

Can someone tell me what I am overlooking here?

regards,
Danny
















Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










[development-axapta] Default field from InventTable to Purchase Line

2004-12-16 Thread Danny Gaethofs







Dear all,

I created a new field on the InventTable. This field has to be 
defaulted automatically to the PurchLine. 

It looks like I need to add the defaulting to the method 
initFromInventTable() on the Class PurchLineType. But I am not sure 
this is the correct place. 

I found out there is a modified() method on the datasource PurchLine 
Field ItemId in the form PurchTable, that is calling the method 
purchLine.itemIdChanged(). This method ulitmately calls the 
previously mentioned method.

It is a bit strange to me that it is triggered by a method on a 
field. Why is it not in the node method on the datasource PurchLine?

Can someone ensure this is the right spot to make the modification.

regards,
Danny Gaethofs















Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










RE: [development-axapta] Default field from InventTable to Purchase Line

2004-12-16 Thread Danny Gaethofs






Dear Girish,

What exactly do you mean to say with your last
sentence? 

regards,
Danny
--- Girish Bhatkal [EMAIL PROTECTED] wrote:

 
 When you select the Item the it first calls the
 InitFromInventTable method
 on the PurchLine table. This in turn calls the
 purchLineType.initFromInventTable method. 
 
 
 
 Because of the performance issue this method is
 written on the table. 
 
 
 
 In case if we want to use the same method of
 initializing the values from
 the InventTable, to the purchline table then we
 may not be able to use it
 if we have written on the form.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 _ 
 
 From: Danny Gaethofs [mailto:[EMAIL PROTECTED] 
 Sent: 16 December 2004 12:05
 To: [EMAIL PROTECTED]
 Subject: [development-axapta] Default field from
 InventTable to Purchase
 Line
 
 
 
 
 
 Dear all,
 
 I created a new field on the InventTable. This field
 has to be 
 defaulted automatically to the PurchLine. 
 
 It looks like I need to add the defaulting to the
 method 
 initFromInventTable() on the Class PurchLineType.
 But I am not sure 
 this is the correct place. 
 
 I found out there is a modified() method on the
 datasource PurchLine 
 Field ItemId in the form PurchTable, that is calling
 the method 
 purchLine.itemIdChanged(). This method ulitmately
 calls the 
 previously mentioned method.
 
 It is a bit strange to me that it is triggered by a
 method on a 
 field. Why is it not in the node method on the
 datasource PurchLine?
 
 Can someone ensure this is the right spot to make
 the modification.
 
 regards,
 Danny Gaethofs
 
 
 
 
 
 
 
 
 
 
 
 Yahoo! Groups Sponsor
 
 
 
 ADVERTISEMENT
 

http://us.ard.yahoo.com/SIG=12996o5if/M=294855.5468653.6549235.3001176/D=gr

oups/S=1705006764:HM/EXP=1103288712/A=2455396/R=0/SIG=119u9qmi7/*http:/small
 business.yahoo.com/domains/ click here
 
 
 

http://us.adserver.yahoo.com/l?M=294855.5468653.6549235.3001176/D=groups/S=
 :HM/A=2455396/rand=766468140 
 
 
 
 _ 
 
 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]

mailto:[EMAIL PROTECTED]
 
 
 * Your use of Yahoo! Groups is subject to the Yahoo!
 http://docs.yahoo.com/info/terms/ Terms of
 Service. 
 
 
 
 [Non-text portions of this message have been
 removed]
 
 
 
 
 


__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 












Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










RE: [development-axapta] Default field from InventTable to Purchase Line

2004-12-16 Thread Danny Gaethofs






Thanks Girish,

I understand what you mean. I have made the changes to
the method I stated before. I have tested it for two
cases: create po manually and from sales order.

It works fine. In fact it should because the method
InitFromInventTable is also on the table PurchLine and
there calls the method I just modified.

In a sense it is not quite developed conform best
pratices in the standard but at least the method is on
the PurchLine table.

regards,
Danny
--- Girish Bhatkal [EMAIL PROTECTED] wrote:

 
 Hi Danny,
 
 
 
 Suppose say you writing an job/class to create an
 Purchase order. If that
 method was not on the table then you would have
 ended up writing the same
 thing again in your job. 
 
 This is not the only case, there could be many other
 instances where you
 would like to use that method. So it is very
 important to see where you are
 writing your code. If possible the method should be
 on the Table (which can
 be source for many functions) and if not possible
 then in the class and if
 it's not possible here then form and this depends on
 the situation.
 
 
 
 cheers,
 
 Girish
 
 
 
 
 
 _ 
 
 From: Danny Gaethofs [mailto:[EMAIL PROTECTED] 
 Sent: 16 December 2004 14:55
 To: [EMAIL PROTECTED]
 Subject: RE: [development-axapta] Default field from
 InventTable to Purchase
 Line
 
 
 
 
 Dear Girish,
 
 What exactly do you mean to say with your last
 sentence? 
 
 regards,
 Danny
 --- Girish Bhatkal [EMAIL PROTECTED] wrote:
 
  
  When you select the Item the it first calls the
  InitFromInventTable method
  on the PurchLine table. This in turn calls the
  purchLineType.initFromInventTable method. 
  
  
  
  Because of the performance issue this method is
  written on the table. 
  
  
  
  In case if we want to use the same method of
  initializing the values from
  the InventTable, to the purchline table then we
  may not be able to use it
  if we have written on the form.
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  _ 
  
  From: Danny Gaethofs [mailto:[EMAIL PROTECTED] 
  Sent: 16 December 2004 12:05
  To: [EMAIL PROTECTED]
  Subject: [development-axapta] Default field from
  InventTable to Purchase
  Line
  
  
  
  
  
  Dear all,
  
  I created a new field on the InventTable. This
 field
  has to be 
  defaulted automatically to the PurchLine. 
  
  It looks like I need to add the defaulting to the
  method 
  initFromInventTable() on the Class PurchLineType.
  But I am not sure 
  this is the correct place. 
  
  I found out there is a modified() method on the
  datasource PurchLine 
  Field ItemId in the form PurchTable, that is
 calling
  the method 
  purchLine.itemIdChanged(). This method ulitmately
  calls the 
  previously mentioned method.
  
  It is a bit strange to me that it is triggered by
 a
  method on a 
  field. Why is it not in the node method on the
  datasource PurchLine?
  
  Can someone ensure this is the right spot to make
  the modification.
  
  regards,
  Danny Gaethofs
  
  
  
  
  
  
  
  
  
  
  
  Yahoo! Groups Sponsor
  
  
  
  ADVERTISEMENT
  
 

http://us.ard.yahoo.com/SIG=12996o5if/M=294855.5468653.6549235.3001176/D=gr
 

oups/S=1705006764:HM/EXP=1103288712/A=2455396/R=0/SIG=119u9qmi7/*http:/small
  business.yahoo.com/domains/ click here
  
  
  
 

http://us.adserver.yahoo.com/l?M=294855.5468653.6549235.3001176/D=groups/S=
  :HM/A=2455396/rand=766468140 
  
  
  
  _ 
  
  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]
 

mailto:[EMAIL PROTECTED]
  
  
  * Your use of Yahoo! Groups is subject to the
 Yahoo!
  http://docs.yahoo.com/info/terms/ Terms of
  Service. 
  
  
  
  [Non-text portions of this message have been
  removed]
  
  
  
  
  
 
 
 __
 Do You Yahoo!?
 Tired of spam? Yahoo! Mail has the best spam
 protection around 
 http://mail.yahoo.com 
 
 
 
 
=== message truncated ===



  
__ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 













Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










Re: SV: [development-axapta] data import error

2004-12-08 Thread Danny Gaethofs


Jens,

I am indeed loading definition groups. 
Doing the same on an 3.0SP2 environment is nog giving
this problem. What is the difference between SP3 and
SP2. How can I get this solved?

I managed to get the definition groups loaded using
the import functionality and not the wizard.
Still when I load data using one of the import groups
I am getting the message New tables are available,
which have not been included in your group.

I synchronized all tables again and recompiled the
whole stuff after I noticed it was working well on SP2
and not SP3.

New tables have been added to microsoft axapta and
your group has not been updated. The strange thing
here is that I got the definition group from another
sp3 environment. When I run preview on the definition
group or when I modify the definition group it is not
making any difference.





regards,
Danny


--- Jens Strandberg [EMAIL PROTECTED] wrote:

 
 Hi,
 
 You will experience this if you are trying to import
 tables, that are shared
 in your application. That could be the definition
 group itself.
 
 /Jens
   -Oprindelig meddelelse-
   Fra: Danny Gaethofs [mailto:[EMAIL PROTECTED]
   Sendt: 7. december 2004 22:26
   Til: [EMAIL PROTECTED]
   Emne: [development-axapta] data import error
 
 
 
 
   Dear all,
 
   Running axapta 3.0 sp3.
 
   I have exported data import/export definitions
 from my development
   database.
 
   When importing my data import/export definition
 groups into a test
   database I get an error message. The message says
 not enough rights
   to insert the data or the imported file only
 contains shared tables.
 
   When importing the dat/def-file using the import
 wizard it works
   fine.
 
   The problem I have is that it seems impossible now
 to import other
   data using the definition groups. I get the
 message New table are
   available which have not been included in your
 group XXX.
 
   I seem not be able to solve this. Whatever I try,
 created new
   company, use the admin login, ... It certainly
 will be a small thing
   that I am overlooking.
 
   Anyone aware of this problem and knows how to
 solve it?
 
   regards,
   Danny
 
 
 
 
 
 
 
 
 Yahoo! Groups Sponsor
 
 Get unlimited calls to
 
 U.S./Canada
 
 
 
 


 --
   Yahoo! Groups Links
 
 a.. To visit your group on the web, go to:

 http://groups.yahoo.com/group/development-axapta/
 
 b.. To unsubscribe from this group, send an
 email to:
 [EMAIL PROTECTED]
 
 c.. Your use of Yahoo! Groups is subject to the
 Yahoo! Terms of Service.
 
 
 
 [Non-text portions of this message have been
 removed]
 
 
 
 
 




__ 
Do you Yahoo!? 
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com 





 Yahoo! Groups Sponsor ~-- 
$4.98 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/Q7_YsB/neXJAA/yQLSAA/saFolB/TM
~- 

 
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:
http://docs.yahoo.com/info/terms/
 






[development-axapta] data import error

2004-12-07 Thread Danny Gaethofs






Dear all,

Running axapta 3.0 sp3.

I have exported data import/export definitions from my development 
database. 

When importing my data import/export definition groups into a test 
database I get an error message. The message says not enough rights 
to insert the data or the imported file only contains shared tables.

When importing the dat/def-file using the import wizard it works 
fine.

The problem I have is that it seems impossible now to import other 
data using the definition groups. I get the message New table are 
available which have not been included in your group XXX. 

I seem not be able to solve this. Whatever I try, created new 
company, use the admin login, ... It certainly will be a small thing 
that I am overlooking.

Anyone aware of this problem and knows how to solve it?

regards,
Danny
















Yahoo! Groups Sponsor


  Get unlimited calls to 	U.S./Canada  












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.










Re: [development-axapta] Axapta 2.5 SP2, Win XP SP2 , Office XP / Outlook

2004-12-06 Thread Danny Gaethofs





Hi Pirmin,


Apparently you have swithed on the outlook
synchronization field on the tab outlook of the
employees.

it can also be that you did not have the configuration
key outlook synchronization under CRM Series enabled
before and you did not.


regards,
Danny
--- pbercher [EMAIL PROTECTED] wrote:

 
 
 Helllo,
 
 since we have installed the 1st pc on WinXP / Office
 XP each time we 
 start Axapta (2.5 /Sp2) on that box, outlooks pops
 up and asks 4 
 A programm is trying to access e-mail Allow
 access for ..
 If i say yes, it's ok for the time i have Axapta
 open, but when in 
 re-open Axapta next time, i'm asked again .. very
 boreing.. anygood 
 hints how to avoid this?
 
 Thx
 
 Pirmin
 
 
 
 
 
 
 


__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 












Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










Re: [development-axapta] Re: Axapta 2.5 SP2, Win XP SP2 , Office XP / Outlook

2004-12-06 Thread Danny Gaethofs





I ran out of options, but for what it is worth.

The classes that execute the synchronize are:
smmInit.initFromServer called from class Application
smmInit.initFromClinet called by initFromServer
smmInit.initEMailEventHandler called from
initFromClient.

It is this method that checks for the outlook user.

But if you disabled the Configuration key and no
employee is enabled it should not be called.

regards, 
Danny
--- pbercher [EMAIL PROTECTED] wrote:

 
 
 Hi Danny
 
 
 hmm .. 
 Outlook synchronization is switched off 4 all empl.
 I tried with the admin user, so the CRM security
 shouldn't be the 
 prob.
 
 Any other ideas?
 
 Thx
 
 Pirmin
 --- In [EMAIL PROTECTED], Danny
 Gaethofs 
 [EMAIL PROTECTED] wrote:
  
  Hi Pirmin,
  
  
  Apparently you have swithed on the outlook
  synchronization field on the tab outlook of the
  employees.
  
  it can also be that you did not have the
 configuration
  key outlook synchronization under CRM Series
 enabled
  before and you did not.
  
  
  regards,
  Danny
  --- pbercher [EMAIL PROTECTED] wrote:
  
   
   
   Helllo,
   
   since we have installed the 1st pc on WinXP /
 Office
   XP each time we 
   start Axapta (2.5 /Sp2) on that box, outlooks
 pops
   up and asks 4 
   A programm is trying to access e-mail
 Allow
   access for ..
   If i say yes, it's ok for the time i have Axapta
   open, but when in 
   re-open Axapta next time, i'm asked again ..
 very
   boreing.. anygood 
   hints how to avoid this?
   
   Thx
   
   Pirmin
   
   
   
   
   
   
   
  
  
  __
  Do You Yahoo!?
  Tired of spam? Yahoo! Mail has the best spam
 protection around 
  http://mail.yahoo.com
 
 
 
 
 
 
 



  
__ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com 
 













Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










RE: [development-axapta] Joining two customers into one

2004-11-19 Thread Danny Gaethofs





Thanks Preston, Jens,

I
--- Preston A. Larimer [EMAIL PROTECTED] wrote:

 What Jens said.. :-)
 
 
 
 -Preston
 
 
 
 _ 
 
 From: Danny Gaethofs [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, November 18, 2004 1:19 PM
 To: [EMAIL PROTECTED]
 Subject: RE: [development-axapta] Joining two
 customers into one
 
 
 
 
 Preston,
 
 After reading this discussion I did some test on the
 CustTable. I am working on a generic conversion tool
 in my spare time. The merge method could solve a few
 problems I encountered.
 
 I however have a question, if the merge method
 encounters duplicate records in one of the children
 it
 is trying to merge an error is thrown and the merge
 is
 aborted.
 
 This happens with the table SalesJournalAutoSummary
 in
 which records are created for each customer.
 
 How are you dealing with these duplicate records? 
 I assume you have identified these situations and
 deal
 with them before executing the merge. Is that
 correct?
 
 
 regards,
 Danny Gaethofs
 
 
 --- Preston A. Larimer [EMAIL PROTECTED] wrote:
 
  
  Correct Jens, if you take the job as is and run it
  on the demo data for two
  customers you should see all transactions,
 Invoices,
  picking list, sales
  orders, etc. moved to the destination customer. 
 It
  works well, MBS just
  hasn't had the time to work out the logic for
  cleaning up those tables where
  a decision has to be made on records to discard
 and
  keep in situations like
  I mentioned earlier.
  
  
  
  -Preston
  
  
  
  _ 
  
  From: Jens Strandberg [mailto:[EMAIL PROTECTED]
 
  Sent: Thursday, November 18, 2004 6:37 AM
  To: [EMAIL PROTECTED]
  Subject: RE: [development-axapta] Joining two
  customers into one
  
  
  
  
  Preston,
  
  Thanks.
  
  Let me get this right: The merge method does it
 all,
  i.e. handle CustTrans,
  SalesOrders, CustInvoiceJour etc. etc. ?
  
  If this is the case it would be fairly simple, I
  guess...
  
  /Jens
  -Oprindelig meddelelse-
  Fra: Preston A. Larimer
 [mailto:[EMAIL PROTECTED]
  Sendt: 18. november 2004 09:44
  Til: [EMAIL PROTECTED]
  Emne: RE: [development-axapta] Joining two
  customers into one
  
  
  
  Jens, the merge method takes care of all of the
  related tables for you, I
  have a version of the code on the website in use
  at a client, and they use
  it to merge customers frequently, the manual
  processing only has to be
  done
  on those tables where you would have to choose
 one
  version over another,
  for
  instance if you had an external price set for
 item
  X on both customers,
  which one to keep, we usually choose to delete
 the
  records for the
  customer
  being merged so the external price for the
 merged
  to customer would be the
  one kept.
  
  
  
  -Preston
  
  
  
  _
  
  From: Jens Strandberg
 [mailto:[EMAIL PROTECTED]
  Sent: Thursday, November 18, 2004 3:27 AM
  To: [EMAIL PROTECTED]
  Subject: SV: [development-axapta] Joining two
  customers into one
  
  
  
  
  Preston,
  
  Thanks for the direction. I guess the tricky
 part
  is to include all
  references, when you do this (CustTrans,
  CustInvoiceJour etc...)
  
  If the Rename option was just enhanced a bit,
  this would be the right
  approach.
  
  /Jens
  
  
  -Oprindelig meddelelse-
  Fra: Preston A. Larimer
  [mailto:[EMAIL PROTECTED]
  Sendt: 18. november 2004 02:52
  Til: [EMAIL PROTECTED]
  Emne: RE: [development-axapta] Joining two
  customers into one
  
  
  
  This link is a basic job for doing this, it
 may
  need altered for the
  customer specific use, but should be a good
  starting point for you.
  
  -Preston
  
  
  
  
  http://www.axaptalink.com/index.php?option=content
  
 
 http://www.axaptalink.com/index.php?option=content
  
 
 http://www.axaptalink.com/index.php?option=content
 
 http://www.axaptalink.com/index.php?option=content

http://www.axaptalink.com/index.php?option=contenttask=viewid=52task=v
 task=viewid=52task=v
  task=viewid=52task=v
  
  task=viewid=52task=v
  iewid=52
  
  
 
=== message truncated ===



  
__ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com 
 













Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










RE: [development-axapta] Joining two customers into one

2004-11-19 Thread Danny Gaethofs





Thanks Preston, Jens,

This confirms my thoughts. This way of working looks
quite similar to what I did for another ERP
application. But my approach there was more generic.
Although I also had to deal with those kind of
exceptions. 

My starting point is the EDT. I still see some
problems there because there is not just one EDT if
your converting address codes.

CustAccount extends CusVendAc, which extends
ExternalAccount. And ExternalAccount is the basis for
VendAccount,...

I will keep on going! I am getting there bit by bit.

regards,
Danny

--- Preston A. Larimer [EMAIL PROTECTED] wrote:

 What Jens said.. :-)
 
 
 
 -Preston
 
 
 
 _ 
 
 From: Danny Gaethofs [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, November 18, 2004 1:19 PM
 To: [EMAIL PROTECTED]
 Subject: RE: [development-axapta] Joining two
 customers into one
 
 
 
 
 Preston,
 
 After reading this discussion I did some test on the
 CustTable. I am working on a generic conversion tool
 in my spare time. The merge method could solve a few
 problems I encountered.
 
 I however have a question, if the merge method
 encounters duplicate records in one of the children
 it
 is trying to merge an error is thrown and the merge
 is
 aborted.
 
 This happens with the table SalesJournalAutoSummary
 in
 which records are created for each customer.
 
 How are you dealing with these duplicate records? 
 I assume you have identified these situations and
 deal
 with them before executing the merge. Is that
 correct?
 
 
 regards,
 Danny Gaethofs
 
 
 --- Preston A. Larimer [EMAIL PROTECTED] wrote:
 
  
  Correct Jens, if you take the job as is and run it
  on the demo data for two
  customers you should see all transactions,
 Invoices,
  picking list, sales
  orders, etc. moved to the destination customer. 
 It
  works well, MBS just
  hasn't had the time to work out the logic for
  cleaning up those tables where
  a decision has to be made on records to discard
 and
  keep in situations like
  I mentioned earlier.
  
  
  
  -Preston
  
  
  
  _ 
  
  From: Jens Strandberg [mailto:[EMAIL PROTECTED]
 
  Sent: Thursday, November 18, 2004 6:37 AM
  To: [EMAIL PROTECTED]
  Subject: RE: [development-axapta] Joining two
  customers into one
  
  
  
  
  Preston,
  
  Thanks.
  
  Let me get this right: The merge method does it
 all,
  i.e. handle CustTrans,
  SalesOrders, CustInvoiceJour etc. etc. ?
  
  If this is the case it would be fairly simple, I
  guess...
  
  /Jens
  -Oprindelig meddelelse-
  Fra: Preston A. Larimer
 [mailto:[EMAIL PROTECTED]
  Sendt: 18. november 2004 09:44
  Til: [EMAIL PROTECTED]
  Emne: RE: [development-axapta] Joining two
  customers into one
  
  
  
  Jens, the merge method takes care of all of the
  related tables for you, I
  have a version of the code on the website in use
  at a client, and they use
  it to merge customers frequently, the manual
  processing only has to be
  done
  on those tables where you would have to choose
 one
  version over another,
  for
  instance if you had an external price set for
 item
  X on both customers,
  which one to keep, we usually choose to delete
 the
  records for the
  customer
  being merged so the external price for the
 merged
  to customer would be the
  one kept.
  
  
  
  -Preston
  
  
  
  _
  
  From: Jens Strandberg
 [mailto:[EMAIL PROTECTED]
  Sent: Thursday, November 18, 2004 3:27 AM
  To: [EMAIL PROTECTED]
  Subject: SV: [development-axapta] Joining two
  customers into one
  
  
  
  
  Preston,
  
  Thanks for the direction. I guess the tricky
 part
  is to include all
  references, when you do this (CustTrans,
  CustInvoiceJour etc...)
  
  If the Rename option was just enhanced a bit,
  this would be the right
  approach.
  
  /Jens
  
  
  -Oprindelig meddelelse-
  Fra: Preston A. Larimer
  [mailto:[EMAIL PROTECTED]
  Sendt: 18. november 2004 02:52
  Til: [EMAIL PROTECTED]
  Emne: RE: [development-axapta] Joining two
  customers into one
  
  
  
  This link is a basic job for doing this, it
 may
  need altered for the
  customer specific use, but should be a good
  starting point for you.
  
  -Preston
  
  
  
  
  http://www.axaptalink.com/index.php?option=content
  
 
 http://www.axaptalink.com/index.php?option=content
  
 
 http://www.axaptalink.com/index.php?option=content
 
 http://www.axaptalink.com/index.php?option=content

http://www.axaptalink.com/index.php?option=contenttask=viewid=52task=v
 task=viewid=52task=v
  task=viewid=52task=v
  
  task=viewid=52task=v
  iewid=52
  
  
 
=== message truncated ===



  
__ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com 
 













Yahoo! Groups Sponsor


  Get unlimited calls to 	U.S./Canada  












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

[development-axapta] Support System

2004-11-19 Thread Danny Gaethofs






Dear all,

I have been searching PartnerSource and PartnerGuide to find an 
overview of the latest service requests (ALL Reported and solved 
problems).

I seem not able to find this overview. Can someone help me out and 
tell me where I can find it. 


regards,
Danny















Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










Re: RE : [development-axapta] Document SalesInvoice

2004-11-18 Thread Danny Gaethofs


Steeve,

Thanks for the reply. It works the way you describe
it, but I was trying to get it working with a section
group. 

As part of a trainingsdocument I am writing about
building reports and documents I am trying to
understand the way these elements are used.

Next to it I am modifying some docs at this moment.

If I understand it well the Section Group is triggered
/ enabled for printing when the line
element.send(SalesLine record) is coded into the
fetch() method of the document. 

I assume (but can you confirm this) that when I do so
I do not need to write a display method to get the
value for the new field.

regards,
Danny

--- Steeve Gilbert [EMAIL PROTECTED]
wrote:

 
 The line is not printed because there's no
 element.send() that would trigger your SalesLine
 section.  SectionGroup needs to be related to a
 table to know what record will trigger the section. 
 It's not related to a dataSource of the report but
 to a table.  So if your section group is related to
 SalesLine AND in the fetch there's code like :
 element.send(some_SalesLine_record) then your
 section would trigger.
 
 Here my suggestion:
 
 Section Group: CustInvoiceTrans
Body:BodyCustInvoiceTrans
Body:NewBody - Your new body
YouNewField - Your new field that takes his
 data from a dataMethod.
 
 This way you're going to have a new line with your
 field.
 
 About removing blank lines in address, I think
 you'll have to code it.
 
 Steeve... 
 
 
 -Message d'origine-
 De : Danny Gaethofs [mailto:[EMAIL PROTECTED] 
 Envoyé : 17 novembre 2004 11:24
 À : [EMAIL PROTECTED]
 Objet : [development-axapta] Document SalesInvoice
 
 
 
 
 Dear all,
 
 ==+ I am trying to add an additional line that
 should print in the 
 body of the invoice just below the order line data,
 item, qty, line 
 amount. Where is the best place to add it?
 
 I have tried adding a section group, plus body in
 the 
 body:BodyCustInvoiceTrans and in the
 body:BodyReference. 
 
 When I print the confirmation in none of both cases
 the new fields 
 are printed. 
 
 Just an example of my structure. The field I used
 here is the sales 
 order line status. This of course is not the field
 (fields) I am 
 trying to add but only for simplicity.
 
 I created the following structure:
 Section Group: CustInvoiceTrans
Body:BodyCustInvoiceTrans
   Methods
   Section Group: SalesTable
   ... all standard fields ...
   Section Group: SalesLine //this is my new
 section group
  Body:SalesLine
 Methods
   SalesOrderStatus
 Enum:SalesOrderStatus
 
 
 Now for some reason I seem not be able to capture
 the field is not 
 printing below the line.
 
 Perhaps someone can explain why a section group
 should be related to 
 a table. Can a section group be related to a table
 that is not in 
 the datasource node?
 
 
 
 ==+ Can someone tell me how I can avoid that blank
 lines in an 
 address field are printed on the document. Is there
 a method that 
 enables me to strip blank lines from the field upon
 printing?
 
 Regards,
 Danny Gaethofs
 
 
 
 
 
 
 
 
 
  
 Yahoo! Groups Links
 
 
 
  
 
 
 
 
 
 
 




__ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com 
 






 Yahoo! Groups Sponsor ~-- 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/saFolB/TM
~- 

 
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:
http://docs.yahoo.com/info/terms/
 






RE: [development-axapta] Joining two customers into one

2004-11-18 Thread Danny Gaethofs





Preston,

After reading this discussion I did some test on the
CustTable. I am working on a generic conversion tool
in my spare time. The merge method could solve a few
problems I encountered.

I however have a question, if the merge method
encounters duplicate records in one of the children it
is trying to merge an error is thrown and the merge is
aborted.

This happens with the table SalesJournalAutoSummary in
which records are created for each customer.

How are you dealing with these duplicate records? 
I assume you have identified these situations and deal
with them before executing the merge. Is that correct?


regards,
Danny Gaethofs


--- Preston A. Larimer [EMAIL PROTECTED] wrote:

 
 Correct Jens, if you take the job as is and run it
 on the demo data for two
 customers you should see all transactions, Invoices,
 picking list, sales
 orders, etc. moved to the destination customer. It
 works well, MBS just
 hasn't had the time to work out the logic for
 cleaning up those tables where
 a decision has to be made on records to discard and
 keep in situations like
 I mentioned earlier.
 
 
 
 -Preston
 
 
 
 _ 
 
 From: Jens Strandberg [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, November 18, 2004 6:37 AM
 To: [EMAIL PROTECTED]
 Subject: RE: [development-axapta] Joining two
 customers into one
 
 
 
 
 Preston,
 
 Thanks.
 
 Let me get this right: The merge method does it all,
 i.e. handle CustTrans,
 SalesOrders, CustInvoiceJour etc. etc. ?
 
 If this is the case it would be fairly simple, I
 guess...
 
 /Jens
 -Oprindelig meddelelse-
 Fra: Preston A. Larimer [mailto:[EMAIL PROTECTED]
 Sendt: 18. november 2004 09:44
 Til: [EMAIL PROTECTED]
 Emne: RE: [development-axapta] Joining two
 customers into one
 
 
 
 Jens, the merge method takes care of all of the
 related tables for you, I
 have a version of the code on the website in use
 at a client, and they use
 it to merge customers frequently, the manual
 processing only has to be
 done
 on those tables where you would have to choose one
 version over another,
 for
 instance if you had an external price set for item
 X on both customers,
 which one to keep, we usually choose to delete the
 records for the
 customer
 being merged so the external price for the merged
 to customer would be the
 one kept.
 
 
 
 -Preston
 
 
 
 _
 
 From: Jens Strandberg [mailto:[EMAIL PROTECTED]
 Sent: Thursday, November 18, 2004 3:27 AM
 To: [EMAIL PROTECTED]
 Subject: SV: [development-axapta] Joining two
 customers into one
 
 
 
 
 Preston,
 
 Thanks for the direction. I guess the tricky part
 is to include all
 references, when you do this (CustTrans,
 CustInvoiceJour etc...)
 
 If the Rename option was just enhanced a bit,
 this would be the right
 approach.
 
 /Jens
 
 
 -Oprindelig meddelelse-
 Fra: Preston A. Larimer
 [mailto:[EMAIL PROTECTED]
 Sendt: 18. november 2004 02:52
 Til: [EMAIL PROTECTED]
 Emne: RE: [development-axapta] Joining two
 customers into one
 
 
 
 This link is a basic job for doing this, it may
 need altered for the
 customer specific use, but should be a good
 starting point for you.
 
 -Preston
 
 
 
 
 http://www.axaptalink.com/index.php?option=content
 
 http://www.axaptalink.com/index.php?option=content
 
 http://www.axaptalink.com/index.php?option=content

http://www.axaptalink.com/index.php?option=contenttask=viewid=52task=v
 task=viewid=52task=v
 
 task=viewid=52task=v
 iewid=52
 
 
 
 
 
 _
 
 From: Jens Strandberg
 [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, November 17, 2004 3:18 PM
 To: [EMAIL PROTECTED] Com (E-mail)
 Subject: [development-axapta] Joining two
 customers into one
 
 
 
 
 
 As you probably know standard Axapta does not
 allow you to join two
 customer
 (or supplier) records; i.e. if you have added
 customer A and later on by
 mistake added the same information as customer
 P, you cannot combine
 these
 two - moving all related records from customer P
 to customer A.
 
 The only option you have is to change the
 primary key for a given
 customer,
 which is not very useful in this case.
 
 As I see it, the only way to join two customers
 into one is to develop
 some
 piece of code that would do the trick for you.
 
 Now, it would be easy to create such a script,
 if we could just see how
 the
 changing of the primary key is done. However,
 this is hidden well inside
 Axapta.
 
 I was wondering if any of you guys would have
 some ideas and pointers to
 this issue. Also, if you happen to know a
 solution to solve this, this
 would
 be very interesting piece of information.
 
 Thanks in advance.
 
 /Jens
 
 
 
 
 
 
 
 
 
 Yahoo! Groups Sponsor
 
 
 
 ADVERTISEMENT
 
=== message truncated ===


__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 












Yahoo! Groups Sponsor


  ADVERTISEMENT 












Yahoo! Groups Links

To visit your group on the web, go to:http

RE: [development-axapta] Joining two customers into one

2004-11-18 Thread Danny Gaethofs





Preston,

Reading the discussion I did some tests using the
merge method.

W


--- Preston A. Larimer [EMAIL PROTECTED] wrote:

 
 Correct Jens, if you take the job as is and run it
 on the demo data for two
 customers you should see all transactions, Invoices,
 picking list, sales
 orders, etc. moved to the destination customer. It
 works well, MBS just
 hasn't had the time to work out the logic for
 cleaning up those tables where
 a decision has to be made on records to discard and
 keep in situations like
 I mentioned earlier.
 
 
 
 -Preston
 
 
 
 _ 
 
 From: Jens Strandberg [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, November 18, 2004 6:37 AM
 To: [EMAIL PROTECTED]
 Subject: RE: [development-axapta] Joining two
 customers into one
 
 
 
 
 Preston,
 
 Thanks.
 
 Let me get this right: The merge method does it all,
 i.e. handle CustTrans,
 SalesOrders, CustInvoiceJour etc. etc. ?
 
 If this is the case it would be fairly simple, I
 guess...
 
 /Jens
 -Oprindelig meddelelse-
 Fra: Preston A. Larimer [mailto:[EMAIL PROTECTED]
 Sendt: 18. november 2004 09:44
 Til: [EMAIL PROTECTED]
 Emne: RE: [development-axapta] Joining two
 customers into one
 
 
 
 Jens, the merge method takes care of all of the
 related tables for you, I
 have a version of the code on the website in use
 at a client, and they use
 it to merge customers frequently, the manual
 processing only has to be
 done
 on those tables where you would have to choose one
 version over another,
 for
 instance if you had an external price set for item
 X on both customers,
 which one to keep, we usually choose to delete the
 records for the
 customer
 being merged so the external price for the merged
 to customer would be the
 one kept.
 
 
 
 -Preston
 
 
 
 _
 
 From: Jens Strandberg [mailto:[EMAIL PROTECTED]
 Sent: Thursday, November 18, 2004 3:27 AM
 To: [EMAIL PROTECTED]
 Subject: SV: [development-axapta] Joining two
 customers into one
 
 
 
 
 Preston,
 
 Thanks for the direction. I guess the tricky part
 is to include all
 references, when you do this (CustTrans,
 CustInvoiceJour etc...)
 
 If the Rename option was just enhanced a bit,
 this would be the right
 approach.
 
 /Jens
 
 
 -Oprindelig meddelelse-
 Fra: Preston A. Larimer
 [mailto:[EMAIL PROTECTED]
 Sendt: 18. november 2004 02:52
 Til: [EMAIL PROTECTED]
 Emne: RE: [development-axapta] Joining two
 customers into one
 
 
 
 This link is a basic job for doing this, it may
 need altered for the
 customer specific use, but should be a good
 starting point for you.
 
 -Preston
 
 
 
 
 http://www.axaptalink.com/index.php?option=content
 
 http://www.axaptalink.com/index.php?option=content
 
 http://www.axaptalink.com/index.php?option=content

http://www.axaptalink.com/index.php?option=contenttask=viewid=52task=v
 task=viewid=52task=v
 
 task=viewid=52task=v
 iewid=52
 
 
 
 
 
 _
 
 From: Jens Strandberg
 [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, November 17, 2004 3:18 PM
 To: [EMAIL PROTECTED] Com (E-mail)
 Subject: [development-axapta] Joining two
 customers into one
 
 
 
 
 
 As you probably know standard Axapta does not
 allow you to join two
 customer
 (or supplier) records; i.e. if you have added
 customer A and later on by
 mistake added the same information as customer
 P, you cannot combine
 these
 two - moving all related records from customer P
 to customer A.
 
 The only option you have is to change the
 primary key for a given
 customer,
 which is not very useful in this case.
 
 As I see it, the only way to join two customers
 into one is to develop
 some
 piece of code that would do the trick for you.
 
 Now, it would be easy to create such a script,
 if we could just see how
 the
 changing of the primary key is done. However,
 this is hidden well inside
 Axapta.
 
 I was wondering if any of you guys would have
 some ideas and pointers to
 this issue. Also, if you happen to know a
 solution to solve this, this
 would
 be very interesting piece of information.
 
 Thanks in advance.
 
 /Jens
 
 
 
 
 
 
 
 
 
 Yahoo! Groups Sponsor
 
 
 
 ADVERTISEMENT
 
=== message truncated ===



  
__ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com 
 













Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










[development-axapta] Document SalesInvoice

2004-11-17 Thread Danny Gaethofs






Dear all,

==+ I am trying to add an additional line that should print in the 
body of the invoice just below the order line data, item, qty, line 
amount. Where is the best place to add it?

I have tried adding a section group, plus body in the 
body:BodyCustInvoiceTrans and in the body:BodyReference. 

When I print the confirmation in none of both cases the new fields 
are printed. 

Just an example of my structure. The field I used here is the sales 
order line status. This of course is not the field (fields) I am 
trying to add but only for simplicity.

I created the following structure:
Section Group: CustInvoiceTrans
 Body:BodyCustInvoiceTrans
 Methods
 Section Group: SalesTable
 ... all standard fields ...
 Section Group: SalesLine //this is my new section group
 Body:SalesLine
 Methods
 SalesOrderStatus
 Enum:SalesOrderStatus


Now for some reason I seem not be able to capture the field is not 
printing below the line.

Perhaps someone can explain why a section group should be related to 
a table. Can a section group be related to a table that is not in 
the datasource node?



==+ Can someone tell me how I can avoid that blank lines in an 
address field are printed on the document. Is there a method that 
enables me to strip blank lines from the field upon printing?

Regards,
Danny Gaethofs















Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










[development-axapta] CustInvoiceTrans.lineNum versus SalesLine.lineNum

2004-11-16 Thread Danny Gaethofs






Dear all,

I am trying to print some additional information on the invoice 
line. The information is not stored in the table CustInvoiceTrans 
but remains in the table SalesLine, at least for now.

I created a display method that looks up the value.
Example:

The method contains the following
select salesLine where salesLine.LineNum == custInvoiceTrans.LineNum
 salesLine.SalesId == custInvoiceTrans.SalesId;

return salesLine.SalesStatus;

To my surprise the display method is not finding the sales line. 
I figured out that the custInvoiceTrans record is populated in the 
method initFromSalesLine() on the table. This method sets the 
lineNum correctly. This method was called by initJournalLine().

But afterwards the method initJournalLine() on the class 
SalesFormLetter_Invoice calls the method setLinenum(sumByLineNum)
where sumByLineNum starts with value 0 and is raised by one 
(sumByLineNum++) .

Why is this done that way? How can I ensure that the correct record 
on the table SalesLine is retrieved in the display method.

regards,
Danny















Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










Re: AW: [development-axapta] CustInvoiceTrans.lineNum versus SalesLin e.lineNum

2004-11-16 Thread Danny Gaethofs


Steve, Palle, Otto,

Thanks a lot for your help. This is indeed working and
I understand the reasoning. As such partial shipments
happens a lot.

regards,
Danny
--- [EMAIL PROTECTED] wrote:

 
 Hi Danny,
  
 use the field InventTransId . You can have partial
 invoices or one invoice per customer for several
 sales orders and if someone prints the linenum on
 the invoice it would be funny...
  
 
 /Otto
  
 
  -Ursprüngliche Nachricht-
 Von: Danny Gaethofs [mailto:[EMAIL PROTECTED]
 Gesendet: Dienstag, 16. November 2004 14:47
 An: [EMAIL PROTECTED]
 Betreff: [development-axapta]
 CustInvoiceTrans.lineNum versus SalesLine.lineNum
 
 
 
 
 Dear all,
 
 I am trying to print some additional information on
 the invoice 
 line. The information is not stored in the table
 CustInvoiceTrans 
 but remains in the table SalesLine, at least for
 now.
 
 I created a display method that looks up the value.
 Example:
 
 The method contains the following
 select salesLine where salesLine.LineNum ==
 custInvoiceTrans.LineNum
  salesLine.SalesId == custInvoiceTrans.SalesId;
 
 return salesLine.SalesStatus;
 
 To my surprise the display method is not finding the
 sales line. 
 I figured out that the custInvoiceTrans record is
 populated in the 
 method initFromSalesLine() on the table. This method
 sets the 
 lineNum correctly. This method was called by
 initJournalLine().
 
 But afterwards the method initJournalLine() on the
 class 
 SalesFormLetter_Invoice calls the method
 setLinenum(sumByLineNum)
 where sumByLineNum starts with value 0 and is raised
 by one 
 (sumByLineNum++) .
 
 Why is this done that way? How can I ensure that the
 correct record 
 on the table SalesLine is retrieved in the display
 method.
 
 regards,
 Danny
 
 
 
 
 
 
 
 
 Yahoo! Groups Sponsor 
 
 ADVERTISEMENT
 

http://us.ard.yahoo.com/SIG=129strqev/M=298184.5584357.6650215.3001176/D=groups/S=1705006764:HM/EXP=1100699440/A=2426682/R=0/SIG=11edksnhv/*http://www.netflix.com/Default?mqso=60185402
 click here
  

http://us.adserver.yahoo.com/l?M=298184.5584357.6650215.3001176/D=groups/S=:HM/A=2426682/rand=240536163
   
 
 
   _  
 
 Yahoo! Groups Links
 
 
 * To visit your group on the web, go to:
 http://groups.yahoo.com/group/development-axapta/
 http://groups.yahoo.com/group/development-axapta/ 
   
 
 * To unsubscribe from this group, send an email to:
 [EMAIL PROTECTED]

mailto:[EMAIL PROTECTED]
 
   
 
 * Your use of Yahoo! Groups is subject to the Yahoo!
 Terms of Service http://docs.yahoo.com/info/terms/
 . 
 
 
 
 
 [Non-text portions of this message have been
 removed]
 
 
 
 
 




__ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com 
 






 Yahoo! Groups Sponsor ~-- 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/saFolB/TM
~- 

 
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:
http://docs.yahoo.com/info/terms/
 






Re: AW: [development-axapta] CustInvoiceTrans.lineNum versus SalesLine.lineNum

2004-11-16 Thread Danny Gaethofs


Denis,

I realize that but for now some people wanted to have
it this way. 

In time I will add the code to the methods on the
table CustInvoiceTrans and CustInvoiceJour.

Thanks anyway for the reminder.

regards,
Danny

--- Unger, Denis [EMAIL PROTECTED] wrote:

 
 Please note that anyone can delete a sales order. So
 you don't have any infos to print.
 Better way is to store your info in
 CustInvoiceTrans.
 
 Denis
 
 
 -Ursprüngliche Nachricht-
 Von: Danny Gaethofs [mailto:[EMAIL PROTECTED] 
 Gesendet: Dienstag, 16. November 2004 14:47
 An: [EMAIL PROTECTED]
 Betreff: [development-axapta]
 CustInvoiceTrans.lineNum versus SalesLine.lineNum
 
 
 
 
 
 Dear all,
 
 I am trying to print some additional information on
 the invoice 
 line. The information is not stored in the table
 CustInvoiceTrans 
 but remains in the table SalesLine, at least for
 now.
 
 I created a display method that looks up the value.
 Example:
 
 The method contains the following
 select salesLine where salesLine.LineNum ==
 custInvoiceTrans.LineNum  salesLine.SalesId ==
 custInvoiceTrans.SalesId;
 
 return salesLine.SalesStatus;
 
 To my surprise the display method is not finding the
 sales line. 
 I figured out that the custInvoiceTrans record is
 populated in the 
 method initFromSalesLine() on the table. This method
 sets the 
 lineNum correctly. This method was called by
 initJournalLine().
 
 But afterwards the method initJournalLine() on the
 class 
 SalesFormLetter_Invoice calls the method
 setLinenum(sumByLineNum) where sumByLineNum starts
 with value 0 and is raised by one 
 (sumByLineNum++) .
 
 Why is this done that way? How can I ensure that the
 correct record 
 on the table SalesLine is retrieved in the display
 method.
 
 regards,
 Danny
 
 
 
 
 
 
 
 
 
  
 Yahoo! Groups Links
 
 
 
  
 
 
 
 
 Diese E-Mail enthält vertrauliche und/oder rechtlich
 geschützte Informationen. Wenn Sie nicht der
 richtige Adressat sind oder diese E-Mail irrtümlich
 erhalten haben, informieren Sie bitte sofort den
 Absender und vernichten Sie diese Mail. Das
 unerlaubte Kopieren sowie die unbefugte Weitergabe
 dieser Mail ist nicht gestattet.
 
 This e-mail may contain confidential and/or
 privileged information. If you are not the intended
 recipient (or have received this e-mail in error)
 please notify the sender immediately and destroy
 this e-mail. Any unauthorized copying, disclosure or
 distribution of the material in this e-mail is
 strictly forbidden.
 
 
 
 
 
 
 




__ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com 
 






 Yahoo! Groups Sponsor ~-- 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/saFolB/TM
~- 

 
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:
http://docs.yahoo.com/info/terms/
 






Re: [development-axapta] SalesTable

2004-10-29 Thread Danny Gaethofs





Thanks Aji,

Thanks for the extensive reply. This completes my
analysis and enables me to perform the update and add
a my new document.

regards,
Danny

--- Aji Sarosa [EMAIL PROTECTED] wrote:

 
 Hi Danny,
 
 Container fed by checkIfUpdate is actually built in
 method checkIfUpdate() in CLASS salesTableType,
 where it calls method can...BeUpdated() (and
 subsequently, method may...beUpdated()) to get
 enable status. Method checkIfUpdate() in salesTable
 simply calls method checkIfUpdate() in class
 SalesTableType. Try to set a breakpoint on this
 method, you'll get the idea.
 
 Now I try to explain how you can enable the button
 for your new (additional) document. From this
 explanation you may grasp the mechanism applied in
 standard Axapta.
 if you want to attach a new (additional) document
 update, there are things you have to prepare. Let's
 say you want to add another document called pasca
 invoice (whatever it is) to be posted, you'd
 probably follow these steps:
 
 1. Add a new element PascaInvoice in base enum
 DocumentStatus
 
 2. Duplicate menu item action
 SalesFormLetter_Invoice then change the properties:
 Name : SalesFormLetter_PascaInvoice
 Label: Pasca invoice
 EnumParameter: pascaInvoice
 
 3. In the design form SalesTable, add menuItemButton
 under MenuButton ButtonHeaderUpdate:
 Name : buttonUpdatePascaInvoice
 AutoDeclaration: Yes
 MenuItemType: Action
 MenuItemName: SalesFormLetter_PascaInvoice
 DataSource: SalesTable
 
 Up to this point, you might test it and find error
 when you click menu 'Pasca Invoice'.
 It's because your new DocumentStatus::PascaInvoice
 has not been recognized by class
 salesFormLetter. You must create a new class called
 SalesFormLetter_PascaInvoice which extends
 SalesFormLetter. The objective of this new class is
 to process your document. Inside the static method
 construct(...) of class SalesFormLetter, add a line
 of code for your new class instantiation inside the
 switch:
 
 case DocumentStatus::PascaInvoice: return new
 SalesFormLetter_PascaInvoice (getParmId);
 
 I don't discuss the implementation inside your new
 class, since it depends on your requirements and
 time consuming as well. There are also some related
 classes, tables, and other objects to consider. But
 you can try to figure out the process by examining
 similar classes such as SalesFormLetter_Invoice,
 SalesFormLetter_PackingSlip, etc. Don't forget also
 to look at the form SalesEditLine which is the
 intermediate form opened before the document is
 actually posted.
 
 4. Now, modify class SalesTableType, add these new
 methods:
 
 boolean mayPascaInvoiceBeUpdated()
 {
 // let's say, it may only be updated if the
 sales order status is invoiced
 return (salesTable.salesStatus ==
 SalesStatus::Invoiced);
 }
 
 boolean canPascaInvoiceBeUpdated()
 {
 boolean ok;
 ;
 ok = this.mayPascaInvoiceBeUpdated();
 if (ok)
 {
 // if it may be updated, what make it can't
 // ... add your own validation here,
 }
 
 return ok;
 }
 
 client server static int posPascaInvoice()
 {
 return 8; // the highest index in standard is 7,
 so just make it 8
 } 
 
 // modify checkIfUpdate. remember this method is a
 member of class SalesTableType
 container checkIfUpdate()
 {
 container c;
 .
 .
 .
 // add this line
 c = conIns(c, SalesTableType::posPascaInvoice(),
 this.canPascaInvoiceBeUpdated());
 return c;
 }
 
 5. Modify class SalesTableForm
 void enableUpdateJournalButtons(SalesTable 
 _salesTable,
 
 FormFunctionButtonControl buttonUpdateQuotation,
 
 FormFunctionButtonControl 
 buttonUpdateConfirmation,
 
 FormFunctionButtonControl buttonUpdatePickingList,
 
 FormFunctionButtonControl 
 buttonUpdatePickingListRegistrate,
 
 FormFunctionButtonControl buttonUpdatePackingSlip,
 
 FormFunctionButtonControl buttonUpdateInvoice,
 
 FormFunctionButtonControl 
 buttonUpdateProjectPackingSlip,
 // add this
 parameter
 
 FormFunctionButtonControl buttonUpdatePascaInvoice
 )
 {
 FormDataSource salesTable_ds;
 SalesTable localSalesTable;
 SalesTableType salesTableType;
 container checkIfupdate;
 .
 .
 // add this
 boolean enablePascaInvoiceButton =
 buttonUpdatePascaInvoice? false : true;
 ;
 salesTable_ds = _salesTable.dataSource();
 localSalesTable = salesTable_ds.getFirst(true);
 if (localSalesTable)
 {
 while(localSalesTable)
 {
 if ((enableQuotationButton ==
 true)  
 (enableConfirmationButton 
 == true) 
 (enablePickingListButton ==
 true)  
 (enablePickingListRegistrateButton
 == true) 
 (enablePackingSlipButton ==
 true)  
 (enableInvoiceButton 
 == true) 
 (enableProjectPackingSlipButton ==
 true)  
 (enablePascaInvoiceButton 
 == true))
 {
 break;
 }
 .
 .
 .
 if (!enablePascaInvoiceButton)
 enablePascaInvoiceButton =
 salesTableType.mayPascaInvoiceBeUpdated();
 localSalesTable =
 salesTable_ds.getNext();
 }
 }
 else
 {
 // you might find that
 _salesTable.checkIfUpdate() will actually call
 method 
 // chekIfUpdate() in class salesTableType ...
 // no wonder method may...BeUpdated() is called
 as well
 

Re: [development-axapta] SalesTable

2004-10-27 Thread Danny Gaethofs





Thanks a lot Aji,

Before I saw your answer I spent a lot of time on
figuring all of this out. You confirm what I learned
meanwhile. 

Nevertheless the thing I still do not catch is where
the container checkIfupdate gets its values. During my
analysis I did find the method checkIfUpdate() on the
SalesTable but I do not understand how the container
is build. 

The main reasons why I am asking this is because I
want to add an extra document to it.
I saw the whole stuff with the posQuotation method and
the mayQuotationBeUpdated method.

I noticed that when the method
enableUpdateJournalButtons is run the else loop is
executed. Whereas normally the method
mayQuotationBeUpdated is called within the if loop I
noticed that the statement checkIfupdate =
_salesTable.checkIfUpdate() calls the
mayQuotationBeUpdated also.

That is where I am lost! How can this method build the
container and how can it call the
mayQuotationBeUpdated method.

I would appreciate it if you could tell me how it is
done.

I have temporarily solved it by assigning the enable
value for my new document hardcoded, setting it to
true. But this is not the longterm solution.

regards,
Danny

--- Aji Sarosa [EMAIL PROTECTED] wrote:

 Hi Danny,
 
 As you may see in salesTable form, there is a menu
 button labeled Posting to post sales order into:
 - quotation
 - confirmation
 - picking list
 - picking list registration
 - packing slip
 - invoice
 
 Method enableUpdateJournalButtons(...) is called to
 enable/disable those menu buttons
 (quotation, confirmation, etc) according to some
 criteria. For example, when you have a sales order
 with status 'delivered', the confirmation button
 will be disabled. Table method checkIfUpdate() is
 called inside the method to compose the list of
 enable status of each menu button. The
 implementation to build the container is actually
 done in method checkIfUpdate() of class
 SalesTableType.
 
 The enable status, which is a boolean value, is
 arranged in a structured order inside the container.
 There are 7 elements inside the container, that's
 why you get the value 7 which means 7 elements.
 Each element, in this case, consists of a boolean
 value with value 1 for enabled and 0 for
 disabled. 
 
 element 1 for the activation status of quotation
 button
 element 2 for the activation status of confirmation
 button
 element 3 for the activation status of picking list
 button
 element 4 for the activation status of picking list
 registration button
 element 5 for the activation status of packing slip
 button
 element 6 for the activation status of invoice
 button
 element 7 for the activation status of project
 packing slip button
 
 To avoid hardcoding, the index of each element is
 accessed via static methods. For example
 SalesType::posQuotation() is used to get the index
 of quotation button status inside the container,
 which returns 1. SalesType::posConfirmation()
 returns 2, and so on. The following code show how
 one element of the container is constructed in
 method checkIfUpdate() of class SalesTableType:
 
 // method canQuotationBeUpdated() is used to
 determine whether the quotation button 
 // can be enabled or not. the returned value is then
 inserted as the 1st element inside 
 // container c.
 // imagine the code as: c = insert_into_container(c,
 1, determine_and_get_status())
 
 c = conIns(c, SalesTableType::posQuotation(),
 this.canQuotationBeUpdated());
 
 // ... and so on
 
 If you debug the returned container of
 checkIfUpdate() method, you can see the values
 inside. For example:
 
 7
 0
 0
 1
 1
 1
 1
 0
 
 It means, (in top-down order):
 
 quotation button: to be disabled
 confirmation button: to be disabled
 picking list button: to be enabled
 picking list registration button: to be enabled
 packing list button: to be enabled
 invoice button: to be enabled
 project packing slip button: to be disabled
 
 The following code is used to get the status of a
 button from the returned container:
 
 // get the status of quotation button from the 1st
 element of the container
 // imagine the code as: 
 // enableQuotationButton =
 get_container_element(enable_status_container, 1);
 
 enableQuotationButton = conPeek(checkIfupdate,
 SalesTableType::posQuotation());
 
 // and so on ...
 
 After the status is captured, then the button will
 be enabled/disabled by the following code:
 
 // if enableQuotationButton == 1, enable quotation
 button; otherwise disable
 

buttonUpdateQuotation.enabled(enableQuotationButton);
 
 Hope this helps.
 
 -Aji Sarosa-
 
 
 dgaethofs [EMAIL PROTECTED] wrote:
 
 
 Hello,
 
 Can somebody tell me what exactly the method
 checkIfUpdate is doing 
 on the tables SalesTable.
 
 The method is called from the method
 enableUpdateJournalButtons on 
 the class SalesTableForm. CheckIfUpdate is a
 container in the method 
 enableUpdateJournalButtons. It is assigned a value
 retrieved via the 
 method checkIfUpdate() on the SalesTable. In my case
 the value 7 
 is returned by 

Re: SV: [development-axapta] index file axapd.aoi

2004-10-08 Thread Danny Gaethofs





Pieter,

Where can I find them in the database ?
Cause almost all objects in the data dictionary keep
their id number even when a modification is made to
them in a higher layer. Nevertheless the system knows
that is has been modified and in which layer.

What logic is used to ensure that a modified object is
first taken from the highest layer and not from the
kernel. Apparently if I read the developer's manual
this should be the unique id number. However since it
looks that this is not valid for objects in the data
dictionary how is it done?

regards,
Danny

--- Pieter Wijnen [EMAIL PROTECTED] wrote:

 
 They are sequential to their layer
 
 I don't have the sequenques handy right now, so I
 can't elaborate, but
 it does make life hell when you want to move objects
 (read tables) to a
 different layer..
 
 
 
 Pieter
 
 
 
 -Opprinnelig melding-
 Fra: dgaethofs [mailto:[EMAIL PROTECTED] 
 Sendt: 6. oktober 2004 08:24
 Til: [EMAIL PROTECTED]
 Emne: [development-axapta] index file axapd.aoi
 
 
 
 
 Dear all,
 
 The index file axapd.aoi contains all application
 object id's based
 on the unique id number assigned upon creation or
 modification of an
 object in a higher layer.
 
 Which unique id numbers are used in the index file?
 
 regards,
 Danny
 
 
 
 
 
 
 
 
 Yahoo! Groups Sponsor
 
 ADVERTISEMENT
 click here

http://us.ard.yahoo.com/SIG=129kaq2vn/M=295196.4901138.6071305.3001176/

D=groups/S=1705006764:HM/EXP=1097130376/A=2128215/R=0/SIG=10se96mf6/*htt
 p:/companion.yahoo.com 
 
 

http://us.adserver.yahoo.com/l?M=295196.4901138.6071305.3001176/D=group
 s/S=:HM/A=2128215/rand=275891093 
 
 
 
 _ 
 
 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]

mailto:[EMAIL PROTECTED]
 be 
 
 
 * Your use of Yahoo! Groups is subject to
 the Yahoo! Terms of
 Service http://docs.yahoo.com/info/terms/ . 
 
 
 
 [Non-text portions of this message have been
 removed]
 
 
 
 
 



  
__
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 












Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










Re: [development-axapta] Override versus Overload

2004-07-26 Thread Danny Gaethofs




Jens,
 
Apparently overloading is not working, but the error message I get is questionable.
 
I Just created the following classes:
 
animal()
{
 void talk()
 {
 print animal talk;
 }
 
}
 
dog() extends animal
{
 void talk(int z)
 {
 print dog talk;
 }
}

Now I get the error message an overloaded function has an incorrect number of parameters. 
 
It is because I added the parameter the method became overloaded. 
 
So I think overloading is not possible. Maybe someone out there has an example that shows the opposite.
 
regards,
Danny
 

Jens Fudge [EMAIL PROTECTED] wrote:





Normally in OOP there are these definitions

override a method:
In an inherited class, you can override a method with the same number of
parameters, where the parameters must be of the same type as the ancestor.
Hence when you call the method, you don't see any difference in the method
calls. In Axapta you may call Super() as to also have the ancestors code
run.
I think Axapta even calls it overwrite

overload a method:
This is done in either one level or more levels of inheritance. It simply
means that you can have two or more methods with the same name. The methods
must then differ in the parameterlist. Either by number or by type.
I do not think that its possible to overload in Axapta.

Jens Fudge



 
 dgaethofs 
 [EMAIL PROTECTED] 
 com To 
 [EMAIL PROTECTED] 
 26-07-2004 15:23 cc 
 
 Subject 
 Please respond to [development-axapta] Override 
 development-axapt versus Overload 
 [EMAIL PROTECTED] 
 
 
 
 
 




Dear all,

I have a question about the difference between override and
overload. In the developers guide one talks about the two as if they
are the same. But they are not.

Can we overload methods in Axapta ?
What exactly is meant with overloading in Axapta?

Regards,
Danny

 
 Yahoo! Groups Sponsor 
 
 
 
 ADVERTISEMENT 
 click here 
 
 
 
 



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.


Yahoo! Groups SponsorADVERTISEMENT


-
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. 


  
-
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!

[Non-text portions of this message have been removed]











Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










Re: [development-axapta] Hardware sizing

2004-07-25 Thread Danny Gaethofs




Dear Arkadiusz,
 
Check out: http://www.fujitsu-siemens.com/solutions/strategic_partners/microsoft/axapta.html
 
regards,
Danny


Arkadiusz Zimniak [EMAIL PROTECTED] wrote:
HAllo,

I have to prepare list of hardware for Axapta installation. Where 
can I find guidelines for this ? (I know that it was hardware
sizing tool from HP and Compaq - are they still exist - if Yes what
is the address?)

Best regards
Arkadiusz Zimniak 






Yahoo! Groups Links






  
-
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!

[Non-text portions of this message have been removed]











Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










Re: [development-axapta] User modifications.

2004-06-24 Thread Danny Gaethofs




Jens,
 
I guess these are stored in the axusr.aod.

regards,
Danny

Jens Strandberg [EMAIL PROTECTED] wrote:
Hello there,

In which files are user modifications stored in Axapta ?

I am thinking of modifications of forms (adding new fields, hiding existing
ones, moving fields etc.)

Thanks in advance..

Best Regards,
Jens



Yahoo! Groups SponsorADVERTISEMENT


-
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. 


  
-
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!

[Non-text portions of this message have been removed]











Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










Re: [development-axapta] Turn on 'Tips of the day'

2004-06-11 Thread Danny Gaethofs




Harish,
 
Go to Tools, Options, select button toolbar .
there you can find show tool tips
 
regards,
Danny

Harish Mohanbabu [EMAIL PROTECTED] wrote:
Hi

Some time back I turned off 'Tips of the day' for couple of users. 
Now I want to turn it on for them. How can I do this? Please let 
me know.

Many thanks in advance

Harish Mohanbabu




Yahoo! Groups SponsorADVERTISEMENT


-
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. 


  
-
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger

[Non-text portions of this message have been removed]










Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










RE: [development-axapta] BOM Line Item Name

2004-05-18 Thread Danny Gaethofs




Oliver,
 
Thanks I had noticed the DataMethod was there on the property sheet of the grid, but I was not able to find the method. 
 
I found it now, but still have a question about it.
the method itemNameGrid activates the method itemName on the table BOM.
 
This method returns the item name as follows:
return InventTable::find(this.itemID).itemName(this.inventDim());
 
What I do not understand is how the name is assembled if a record entry exists in the inventDim table. Am I overlooking something here.
 
regards,
Danny

Oliver Mestdagh [EMAIL PROTECTED] wrote:
Check out the DataMethod property of the StringEdit:ItemName field.
This is set to itemNameGrid which is a method on the BOM table.



-Original Message-
From: dgaethofs [mailto:[EMAIL PROTECTED]
Sent: Monday, 17 May 2004 9:37 PM
To: [EMAIL PROTECTED]
Subject: [development-axapta] BOM Line Item Name


dear all,

Maybe someone can help me in finding how the item name on the bom 
line is constructed.

The form is BOMConsistOf. If I look into the form designs I find a 
StringEdit called ItemName. On the property of that field the 
DataSource is BOM and the DataField is indicate as a box with a 1 in 
it. 

I am trying to figure out where the name comes from. Can someone 
help me out.

regards,
Danny




Yahoo! Groups Sponsor 

ADVERTISEMENT

/S=1705006764:HM/EXP=1084904797/A=2128215/R=0/SIG=10se96mf6/*http://companio
n.yahoo.com click here 

:HM/A=2128215/rand=507184059 


_ 

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
. 




[Non-text portions of this message have been removed]






Yahoo! Groups Links





  
-
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.

[Non-text portions of this message have been removed]











Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










RE: [development-axapta] BOM Line Item Name

2004-05-18 Thread Danny Gaethofs




Dear all,
 
The name in the bom lines is created by looking at the inventdim table, I do not know yet how, but afaik, the other problem I am having is the following:
 
The records in the inventdim table are created the moment an item is added to the bom line having one of the inventory dimensions color, size or configuration activated.
Under the condition that you can enter a dimension on the bom line.
 
If you look into the inventdim table there is also a record that contains the value axapta and of which all the dimensions are blank, I noticed this record is used when bom lines do not have an item dimension. Am I correct? Yes I think so, at least some test show it.
 
Now I noticed something is going wrong with the item name on the bom line under the following conditions. 
 
Suppose you create an item call it bike-bel and you give it a standard dimension group, no dimensions activated. Now you add this item to the bom of a bike. A record will be created into the inventdim table whereas the inventDimId is axapta, if it did not already exist. In the BOM a record for the bike-bel will be created and assigned the inventdimid axapta.
 
Now get out of the bom and change the dimension group of the bike-bel into a color dimension group and add the colors.
 
Now get into the bom of the bike again, and you will notice you have to add a color to the line bike-bell. When this happens an inventdim record is created, if it did not yet exist, and the inventdimid in the BOM table for the bike-bel line will be assigned the value of the inventdim table.
 
But what I see is that the item name is not updated in the bom line.
 
Next curiosity is that the inventdim table is not cleaned up the moment I delete the bike-bel line with a certain color. I believe this is because the inventdim table is used for several boms. But anyway it means that if you ever used a color value that you are no longer using a record will remain available in the inventdim table. Whether this is good or bad I can not judge now.
 
 
This is on .Axapta Release 3.0 SP3.
 
 
regards,
Danny

Oliver Mestdagh [EMAIL PROTECTED] wrote:
Check out the DataMethod property of the StringEdit:ItemName field.
This is set to itemNameGrid which is a method on the BOM table.



-Original Message-
From: dgaethofs [mailto:[EMAIL PROTECTED]
Sent: Monday, 17 May 2004 9:37 PM
To: [EMAIL PROTECTED]
Subject: [development-axapta] BOM Line Item Name


dear all,

Maybe someone can help me in finding how the item name on the bom 
line is constructed.

The form is BOMConsistOf. If I look into the form designs I find a 
StringEdit called ItemName. On the property of that field the 
DataSource is BOM and the DataField is indicate as a box with a 1 in 
it. 

I am trying to figure out where the name comes from. Can someone 
help me out.

regards,
Danny




Yahoo! Groups Sponsor 

ADVERTISEMENT

/S=1705006764:HM/EXP=1084904797/A=2128215/R=0/SIG=10se96mf6/*http://companio
n.yahoo.com click here 

:HM/A=2128215/rand=507184059 


_ 

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
. 




[Non-text portions of this message have been removed]






Yahoo! Groups Links





  
-
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.

[Non-text portions of this message have been removed]











Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










Re: [development-axapta] Auto creation of a Quotation line

2004-05-10 Thread Danny Gaethofs




Akash,
 
I will give you one way you can accomplish this. Of course there will possibly be more alternatives.
 
Override the run() method In the form's methods node (in other words create a run method) and add the following line after super()
DATASOURCENAME_ds.create()
 
Datasourcename is the name of the quotation table as you can find in the Data Sources node of the form. The letters _ds have to follow the data source name. 
This indicates the create() method will act on the data source.
 
regards,
Danny
 


akash malohatra [EMAIL PROTECTED] wrote:
Hi All,
I am a little newbie in Axapta.Please guide me in
right direction.
I want one line should create in the
quotation Form as soon as the Quotation Form Opens
( no need to use the CTRL+N) from the CRM business
Relation Form -- create
Quotation , having the relation to Busrel Account and
Project id.

I am just not getting in which Class/Form , method i
will put some code , so that it will work. 

Thanks in Advance

Regards
Akash







Yahoo! Messenger - Communicate instantly...Ping 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html




Yahoo! Groups Links





  
-
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs 

[Non-text portions of this message have been removed]











Yahoo! Groups Sponsor


  ADVERTISEMENT 












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.










RE: [development-axapta] Members can not be added to EMail Groups

2004-04-01 Thread Danny Gaethofs



Carsten,

Can you give me a hint where I can find the description of the request id. I have been looking on partnersource,partnerguide and techknowledge, but I seem not able to find it.

regards,
Danny"Carsten M. Horlacher" [EMAIL PROTECTED] wrote:
Hi, I don´t know if it helps you with your current installation but your problem is a know bug. The request id is "DE-679-132-5E43". So you are right that you need the Sales Management license code. The problem is fixed with SP3 that its available since yesterdayRegards,Carsten-Original Message-From: dgaethofs [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 11:29 AMTo: [EMAIL PROTECTED]Subject: [development-axapta] Members can not be added to EMail GroupsDear all,A user of Axapta lately raised the question/issue that they could not add members to email groups created in CRM.The organization has only the license key for sales force automation. The license code sales force automation is connected to the configuration key SmmCRM.What I have noticed is that the following
 elements have assigned this configuration key:- menu item smmEmailGroup- menu item smmEmailMembers- table smmEmailMembers- table smmEmailGroupsI also noticed that the button OpenEmailMembersForm on the form smmEmailGroups has no configuration key assigned.The form smmEmailMembers contains 4 data sources:- smmEmailMembers- ContactPerson- EmplTable- smmSalesUnitMembersNow the last table has been assigned the configuration key SmmSM (which relates to the license code Sales Management).Since you can not open the form smmEmailMembers standalone, requires a buffer to be initialized, I have been trying to find out whether there are besides the form smmEmailGroups, other forms that call it.Because this would perhaps explain how to add members from out of other areas in CRM.I have not found another form!My main questions - remarks now are: Is this a design error? Or was it
 meant to be this way?If it needs to be excluded for those not having the license code sales management, why is there no configuration key on the button.On the other hand if it should work when you do not have the license code sales management, why is the data source smmSalesUnitMembers part of the form or why does it have the license code sales management. Is there a way to have tables assigned different license codes and still use them as datasources on one form without causing problems?regards,Danny Gaethofs Yahoo! Groups Links***This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your
 system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, received late or incomplete, or could contain viruses. The sender therefore does not accept liability for any error or omission in the contents of this message, which arises as a result of e-mail transmission.***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:http://docs.yahoo.com/info/terms/Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway - Enter today







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.










[development-axapta] Query Configuration

2004-03-24 Thread Danny Gaethofs



Dear all,

I am trying to generate an overview of the configuration keys and their parents in the system. I am targetting at displaying which of the keys are enable and which are not. 
I want to have the output exported to a fle or else printed.

I have 4 main questions:

1.Can someoneexplain me how Ican export the output or indicate whereI can find an example.

2. How can I print it?

3. The most difficult question I have is related to the Job I created.I have defined an Object parConfigurationKey based on the DictConfigurationKey. See below in the Job.
When I compile the job there are no errors. When I run the Job I get the error :
Error.
Error executing code: DictConfigurationKey object not initalized.

Stack trace:
\Classes\DictConfigurationKey\name
\Jobs\. line 39

What I am trying to accomplish is printing the name of the parentConfigurationKey for each ConfigurationKey.

4. I also need to built in somekind of a loop that prints the parents until it arrives at parent id 0. How can I does so, considering the above mentioned problems.

Regards,
Danny



static void QryConfigurationKeys(Args _args){Dictionary dictionary = new Dictionary();ConfigurationKeySet configurationKeySet = new ConfigurationKeySet();DictConfigurationKey dictConfigurationKey;DictConfigurationKey parConfigurationKey;int cntCfgKey, cntCfgKeySet;print "number of configuration keys: "+int2str(dictionary.configurationKeyCnt());for (cntCfgKey=1; cntCfgKey= dictionary.configurationKeyCnt();cntCfgKey++){dictConfigurationKey = new DictConfigurationKey(dictionary.configurationKeyCnt2Id(cntCfgKey));if (dictConfigurationKey.name() like "*BOM*"){print Int2Str(dictionary.configurationKeyCnt2Id(cntCfgKey))+ " "+ dictConfigurationKey.name()+ " "+ Enum2Str(dictConfigurationKey.enabled())+ " "+ dictConfigurationKey.label()+ " "+ Int2Str(dictConfigurationKey.parentConfigurationKeyId());
/*parConfigurationKey = new DictConfigurationKey(dictConfigurationKey.parentConfigurationKeyId());print parConfigurationKey.name();*/}}}Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.







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.










RE: [development-axapta] Mutli-Country Implementation - Single Database

2004-03-04 Thread Danny Gaethofs



Mai-Britt,

To make sure I have understoodit correctly I 

1. When a new service pack is released are the DIS layers merged into the SYS layers?

2. When a new release is issued I understand that most of the DIS layer functionality will be merged into the SYS layer, but some functionality will have to be issued in a DIS layer by the respective country. That means there is some kind of a selection process of what will be merged into the SYS layer and what not. 

3. Ifan error has been detected in a DIS layer, like thecontactpersonname example, should a country release a new DIS layer or issue a DIP layer. 
The question is also related to what should we install when we find a DIS, DIP SP1 and DIP SP2 layer. For example in case of the Dutch localizations. Do we have to install all of them or can we just sustain with the latest DIP layer.

Last question I have is about the Russian DIS layer. If you look into a standard Axapta 3.0 version you do not see Russia below the country configuration keys. Nor is it available in the license information as one of the languages. Am I correct when I assume that the moment I have installed the Russian DIS layer these keys become available.

Regards,
Danny Gaethofs"Mai-Britt Winther (MICROSOFT BUSINESS SOLUTIONS)" [EMAIL PROTECTED] wrote:









Hi Danny

For version 4.0 you will expect to find the vast majority of the DIS layers merged into the SYS layer. And as a new thing we are actually striving to deliver all layers at the same time – that means there will not be a 3 months interval between the SYS release and the DIS layers release. I cannot promise you that this will happen for Service pack 3 as well, but I know that all our country offices are actually also trying to meet the service pack 3 release date as well. They are now in the development loop together with the rest of the development team.

In the case of the contact person name field – please check the fix list for service pack 2, because the change was actually made for CRM, as far as I remember.

That case is unfortunately a classical example of unfortunate events – because normally corrections like that should not be made in a service pack. However there were some problems that needed to be fixed. Normally all country offices do a walk through of the corrections for the service pack and test with their respective DIS layers in order to ensure that these things do not conflict with other DIS corrections – that happens before fx. the service pack is critical test completed. If the country office finds some issues they release a newer DIS layer that will take care of the problems.

When building a major release the development circle is long and very tedious. And there are many rules to apply by, however we need to build the whole version, and run a side track for the DIS layers, because some of the DIS layers functionality will have to either be changed or singled out as we develop along. As you all know Axapta strives towards generic design, meaning if a new taxation rule suddenly comes up in fx. Germany and the German office creates a temp. solution in a DIS layer to comply with the legal demand (of course they will try to provide the correct solution from the beginning allowing us just to ‘plug’ it in later in the release), we will have to investigate what it takes to
 build it in with the standard taxation engine – only separating it with a configuration key.

You may probably not expect that all DIS layers will be merged to the SYS layer in 4.0 – especially the Russian DIS layer is so huge that it actually has a size more or less the same as the standard application. It takes a very long time to investigate such a layer and split it apart in order to just ‘plug’ it in. But all the other official DIS layers will be part of the 4.0 development circle. We have a separate team in development only focusing on global development localization.

If you for any matter experience problems like the one you described please let the country office know in order for them to pass on that knowledge to the localization team and allowing us to fix it. Contrary of what people may think, we actually try to fix as much as we can – but anyone working in developing a standard ERP solution will know that at some point in time the window for correcting and developing will be closed for a release in order to enter into stabilization and test. 

Best regards

Mai-Britt





From: Danny Gaethofs [mailto:[EMAIL PROTECTED] Sent: 2. marts 2004 19:01To: [EMAIL PROTECTED]Subject: RE: [development-axapta] Mutli-Country Implementation - Single Database


Gert,



Thanks for sharing your experience.



It seems there are a lot of problems to overcome before one can easily execute a global roll-out over several countries.





Mai-Britt,



When can we expect the new release AND will all the current DIS layers be integrated?



What kind of development rules exist for the country localizations? 

For example I am trying 

RE: [development-axapta] Mutli-Country Implementation - Single Database

2004-03-02 Thread Danny Gaethofs



Gert,

Thanks for sharing your experience.

It seems there are a lot of problems to overcome before one can easily execute a global roll-out over several countries.


Mai-Britt,

When can we expect the new release AND will all the current DIS layers be integrated?

What kind of development rules exist for the country localizations? 
For example I am trying to install the Belgian DIS layer on top of SP2 and I am getting errors on the field contactpersonname. Apparently a new field has been added to the CompanyInfo table. What happens if other countries implement the same field but for other purposes? Or do you have rules that prevent these kind of things.


Regards,
Danny



"Gert Neetesonne (Hotmail)" [EMAIL PROTECTED] wrote:
Unfortunately, MBS is promising our customers that Axapta is an applicationwhich is proven for multiple countries, and leaving us partners with thetrouble. Partners have to merge DIS-layers themselves (for which customersdo not want to pay), and MBS refuses to import these merged layers in a"customized" DIS-layer. Good strategy, because that way, they can sell an extra BUS-license on theback of the customer. If the customer does not want to buy it, the mergedlocal version mixes up with the tailor made software in the VAR-layer(making upgrades crazy)Moreover, when a new release or major comes out, it takes up to 3 monthsbefore all new DIS-layers are released.Now MBS is also merging DIS-layers, but they aren't usable if you have aninstallation with companies from more than country. The country
 specificfunctionality is linked to a configuration key. A configuration key can beswitched on or off for the whole application (i.e. for all companies). So,you should switch on all keys for all countries you have. In the code, theycheck if a configuration key is enabled to execute code. This implies thatin an installation with Belgian and Dutch functionality the functionalityfor both countries will be executed, and not one of them. Of course, this implies that modifications are still necessary, even iflayers have been integrated.Seems we still have a long way to go.Gert NeetesonneEDAN Business Software _ From: Mai-Britt Winther (MICROSOFT BUSINESS SOLUTIONS)[mailto:[EMAIL PROTECTED] Sent: zaterdag 28 februari 2004 13:51To: [EMAIL PROTECTED]Subject: SV: [development-axapta] Mutli-Country Implementation -
 SingleDatabaseHi DannyMBS developement is for every major version merging existing DIS layers -however you will find that for example the Russian DIS layer is a trickylayer to merge, since that layer i huge.All other layers will try to keep their pieces of country specificfunctionality to a bare minimum thereby enabling us to easier merge thesepieces into a new version.Having written this - we have a team at MBS who is concentrating on mergingthese DIS layers into the next major release - in this case 4.0. However inthe meantime, partners would have to merge the DIS layers themselves, ifthey require and choose to run with more than one DIS layer on the sameinstallation.Best regardsMai-Britt _ Fra: origaet [mailto:[EMAIL PROTECTED]Sendt: lø 28-02-2004 13:35Til: [EMAIL PROTECTED]Emne:
 [development-axapta] Mutli-Country Implementation - Single DatabaseDear all,I am investigating how a world-wide roll-out of Axapta can be established using one central database.The biggest problem I see at current is related to the Country Specific layers, whereas these are developed by each MBS Country Team.Possibly, whithout having it investigated, these country layers can have contradictionary approaches. Most likely, there are country layers that have upgraded the database with new fields and even tables.In previous topics I read suggestions that the different country layers (DIS, DIP) should be merged. If however the database schemes are different between country layers merging the layers will results in greater inconsistencies. Having to investigate all the different layers to find out what is matching and what not, and thereafter perhaps applying all the differences to one base country
 layer becomes unfeasible.I recognize two possible situations.Situation 1If database schemes are identical, one could consider installing an application for each layer.Situation 2If database schemes are different, one will have to patch all the country layers into one big layer. Apply the database changes made by every country to the central database, validate all the country application layers, and hope all of it works.I have a few questions about the subject:1. Is there some kind of standardized development rule to avoid two or more countries apply similar - but not precise the same - database changes. Maybe by giving each country seperate ranges for naming tables, fields, etc... 2. What experiences do we have with inconsistencies between different country layers - especially database schemes.3. In case of situation 1 is there a way to use one central application. I am
 thinking about determing the country layer to