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

[development-axapta] Re: str2map

2004-11-19 Thread byteway_so 






Oh no, just when i thought i got it working...
What I can see is that the first value is not read ok.
So when the string s="1=2, 2=3, 4=5", the first container value will 
be "1".
That's a bummer. I think I will have to track down the global method 
str2con to see why this happens. I saw on you site that you also 
have Delphi experience ;-) Didn't you wish somethimes there was an 
axapta equivalent for the delphi TStringList? 
Ok, but that's for pointing that out to me!

/b

--- In [EMAIL PROTECTED], Max Belugin 
<[EMAIL PROTECTED]> wrote:
> 
> Hello byteway_so,
> 
> ïÿòíèöà, 19 íîÿáðÿ 2004 ã., you wrote:
> 
> 
> b> str s = "key1=value1, key2=value2, key3=value3, key4=value4,
> b> key5=value5";
> b> Container c;
> b> str keypair, key, value;
> b> int i, ipos;
> b> ;
> b> c = str2con(s);
> b> for (i=1; i < conlen(c)+1 ; i++)
> b> {
> b> keypair = strRTrim(strLTrim(ConPeek( c, i )));
> b> ipos  = strScan(keypair, "=", 1, strLen(keypair));
> b> key = substr(keypair, 1, ipos-1);
> b> value = substr(keypair, ipos+1, strLen(keypair));
> b> info(strFmt("Key: %1, Value: %2", key, value));
> b> }
> 
> AFAIR  str2con  is  trying  to convert splitted string parts to 
more special
> types for example, try your code with
> str s = "1=2, 2=3"
> 
> -- 
> Best regards,
>  Max    
> 
> http://belugin.newmail.ru
> ICQ:9406811















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] Field of Dialog invisible

2004-11-19 Thread Preston A. Larimer 





Alfonso, I put the declaration for the dialogGroup in the dialog method in
my exaple, but in reality that declaration has to go in the classDeclaration
of the base class in order to be visible in the sub class.

 

Sorry if it causes confusion.

 

-Preston

 

  _  

From: Alfonso Collados Arroyo [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 19, 2004 10:12 AM
To: 'Development-Axapta ([EMAIL PROTECTED])
Subject: [development-axapta] Field of Dialog invisible

 


Hi all,

I

I have a class that throws a report. This class extends from
InventReport_DimParm. The dialog of this class shows me all the fields to
choose in the InventDimParm Table.

I want to do invisibles some of these dialog fields , but only when I throw
my class, I don't want modified the parent class.

Regards,

Alfonso





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









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. 



[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] Field of Dialog invisible

2004-11-19 Thread Preston A. Larimer 




Alfonso, correct me if I'm wrong, but I expect this is what you are dealing
with, the class InventReport_dimparm dialog is this

 

public Object dialog()

{

;

    dialog = super();

 

    dialogDimGroup =
inventDimParm.addFieldsToDialog(dialog,"@SYS53654",true);

 

    return dialog;

}

 

And your sub class you have done something like this

public Object dialog()

{

;

    dialog = super();

 

    dialogDimGroup.visible(false);

 

    return dialog;

}

 

But it is failing to hide the DimGroup..I've gotten around this by adding a
dialog group to the base dialog like this

 

public Object dialog()

{

    dialogGroup dlgGroup;//Added

;

    dialog = super();

 

    dlgGroup = dialog.addGroup();//Added

    dlgGroup.frameType(formFrameType::None);//Added

    dialogDimGroup =
inventDimParm.addFieldsToDialog(dialog,"@SYS53654",true);

 

    return dialog;

}

 

An addition of a group like this should cause no visible changes in the base
class or any of the other derived classes, the one exception would be a name
collision, that is if you chose a name for the group that was already being
used in one of the other sub classes, do a compile forward after making the
change to ensure you haven't caused this), now in the sub class you can do
this

 

public Object dialog()

{

;

    dialog = super();

 

    dlgGroup.visible(false);

 

    return dialog;

}

 

Hiding the group will hide everything in it .

 

G'luck 

 

-Preston

 

 

  _  

From: Alfonso Collados Arroyo [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 19, 2004 10:12 AM
To: 'Development-Axapta ([EMAIL PROTECTED])
Subject: [development-axapta] Field of Dialog invisible

 


Hi all,

I

I have a class that throws a report. This class extends from
InventReport_DimParm. The dialog of this class shows me all the fields to
choose in the InventDimParm Table.

I want to do invisibles some of these dialog fields , but only when I throw
my class, I don't want modified the parent class.

Regards,

Alfonso





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









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. 



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










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] On-hand stock setup

2004-11-19 Thread Matt Benic 




Thanks Karina.

Regards,

Matt Benic
Axapta Developer
UTi Sun Couriers Division

"The universal aptitude for ineptitude
makes any human accomplishment an incredible miracle."
- Col. John P. Stapp


-Original Message-
From: Karina Normann Jakobsen (MICROSOFT BUSINESS SOLUTIONS)
[mailto:[EMAIL PROTECTED]
Sent: 19 November 2004 04:33 PM
To: [EMAIL PROTECTED]
Subject: RE: [development-axapta] On-hand stock setup




You enable the Multi-transaction system by pressing the button enable
transaction system on tab-page General. Then you can select between 2
methods pessimistic or optimistic. I don't remember the exact difference,
but if you are working with service items only and you don't care if you
have a negative on-hand, then all you should do is to enable the
transactions system and select optimistic.



Med venlig hilsen/Best regards/Mit freundlichen Grüßen

Karina Normann Jakobsen
Program Manager



From: Matt Benic [mailto:[EMAIL PROTECTED]
Sent: 19. november 2004 08:09
To: Axapta Dev
Subject: [development-axapta] On-hand stock setup




Hi all,
Under 'Administration->Setup->System', there is a form 'Stock
multi-transaction system'. Now we only use service items, so it is safe for
us to use the multi-transaction system, however the setting does not specify
'enable multi-transaction' and 'disable multi-transaction', it simply offers
the choice between 'pessimistic' and 'optimistic' access. My colleague and I
cannot determine from the description:
'If you choose the 'Optimistic' principle, the on-hand check will reflect
these concurrent changes. On the other hand, if you choose the 'Pessimistic'
principle, the on-hand check will not be influenced by concurrent changes.'

Whether 'optimistic' or 'pessimistic' represent enabling the
multi-transaction system. My call was 'Optimistic', which one is it?

Regards,

Matt Benic
Axapta Developer
UTi Sun Couriers Division

"The universal aptitude for ineptitude
makes any human accomplishment an incredible miracle."
- Col. John P. Stapp








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
 .



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








Yahoo! Groups Links

















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] disable fields depending upon the inventory Dimension

2004-11-19 Thread Girish Bhatkal 





Hi All,

 

 

I am trying to create a new journal posting (similar to the Inventory
journal posting (profit/loss)).

 

In the journals lines we see that when and ItemId is selected, depending
upon the dimension group settings for this Item, the warehouse dimensions
are activated and disable.

 

Can any one tell me how it is done. One way I know is check for the
dimension settings and then enable/disable the fields by writing code to do
the same. I want to understand, is there any class or method which can be
used to enable/disable depending upon the Dimension group.

 

 

Regards,

Girish



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

[development-axapta] Field of Dialog invisible

2004-11-19 Thread Alfonso Collados Arroyo 





Hi all,

I

I have a class that throws a report. This class extends from
InventReport_DimParm. The dialog of this class shows me all the fields to
choose in the InventDimParm Table.

I want to do invisibles some of these dialog fields , but only when I throw
my class, I don't want modified the parent class.

Regards,

Alfonso

 



[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] On-hand stock setup

2004-11-19 Thread Karina Normann Jakobsen (MICROSOFT BUSINESS SOLUTIONS) 





You enable the Multi-transaction system by pressing the button enable transaction system on tab-page General. Then you can select between 2 methods pessimistic or optimistic. I don't remember the exact difference, but if you are working with service items only and you don't care if you have a negative on-hand, then all you should do is to enable the transactions system and select optimistic.

 

Med venlig hilsen/Best regards/Mit freundlichen Grüßen 

Karina Normann Jakobsen 
Program Manager



From: Matt Benic [mailto:[EMAIL PROTECTED] 
Sent: 19. november 2004 08:09
To: Axapta Dev
Subject: [development-axapta] On-hand stock setup

 


Hi all,
Under 'Administration->Setup->System', there is a form 'Stock
multi-transaction system'. Now we only use service items, so it is safe for
us to use the multi-transaction system, however the setting does not specify
'enable multi-transaction' and 'disable multi-transaction', it simply offers
the choice between 'pessimistic' and 'optimistic' access. My colleague and I
cannot determine from the description:
'If you choose the 'Optimistic' principle, the on-hand check will reflect
these concurrent changes. On the other hand, if you choose the 'Pessimistic'
principle, the on-hand check will not be influenced by concurrent changes.'

Whether 'optimistic' or 'pessimistic' represent enabling the
multi-transaction system. My call was 'Optimistic', which one is it?

Regards,

Matt Benic
Axapta Developer
UTi Sun Couriers Division

"The universal aptitude for ineptitude
makes any human accomplishment an incredible miracle."
- Col. John P. Stapp








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  . 



[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] 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
> >    
> >
>  >  
> >
>  >
> 

> &task=view&id=52&task=v>
> > &task=view&id=52&task=v
> > >
> >   &task=view&id=52&task=v
> >   i

Re: [development-axapta] str2map

2004-11-19 Thread Max Belugin 





Hello byteway_so,

ïÿòíèöà, 19 íîÿáðÿ 2004 ã., you wrote:


b> str s = "key1=value1, key2=value2, key3=value3, key4=value4,
b> key5=value5";
b> Container c;
b> str keypair, key, value;
b> int i, ipos;
b> ;
b> c = str2con(s);
b> for (i=1; i < conlen(c)+1 ; i++)
b> {
b> keypair = strRTrim(strLTrim(ConPeek( c, i )));
b> ipos  = strScan(keypair, "=", 1, strLen(keypair));
b> key = substr(keypair, 1, ipos-1);
b> value = substr(keypair, ipos+1, strLen(keypair));
b> info(strFmt("Key: %1, Value: %2", key, value));
b> }

AFAIR  str2con  is  trying  to convert splitted string parts to more special
types for example, try your code with
str s = "1=2, 2=3"

-- 
Best regards,
 Max    

http://belugin.newmail.ru
ICQ:9406811













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] str2map

2004-11-19 Thread byteway_so 





Hi all,

I was looking for a method like: "str2map". But there is no such 
method available in Axapta. The only alternative to assign 
a "key=value" pair to a map object is to itterate through the string 
yourself. Because I always forget this, I post this information 
here. If someone has a better sollution, please tell me so. 

Thanks,

str s = "key1=value1, key2=value2, key3=value3, key4=value4, 
key5=value5";
Container c;
str keypair, key, value;
int i, ipos;
;
c = str2con(s);
for (i=1; i < conlen(c)+1 ; i++)
{
keypair = strRTrim(strLTrim(ConPeek( c, i )));
ipos  = strScan(keypair, "=", 1, strLen(keypair));
key = substr(keypair, 1, ipos-1);
value = substr(keypair, ipos+1, strLen(keypair));
info(strFmt("Key: %1, Value: %2", key, value));
}













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] Axapta 3.0 SP3 and Oracle 10

2004-11-19 Thread Tomasz Dudek 


Hello All!
Have anybody installed Axapta 3.0 SP3 with Oracle 10 database? We have some
problems with Oracle 9 on customer's machine and we going to instal Oracle
10. Unfortunately we have no experience in connecting this version of Oracle
and Axapta, so we finding any advices.

Please help
Any suggestions will be appreciated.

Tomasz Dudek






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

> &task=view&id=52&task=v>
> > &task=view&id=52&task=v
> > >
> >   &task=view&id=52&task=v
> >   iew&id=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 Preston A. Larimer 




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

&task=view&id=52&task=v>
> &task=view&id=52&task=v
> >
>   &task=view&id=52&task=v
>   iew&id=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 i

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

2004-11-19 Thread Jens Strandberg 





Danny,

I did some testing too, and it actually works just fine. All you have to do
is to customize the script, so that it will delete duplicate records.

This script worked for me:

static void mergeCustomers(Args _args)
{
    custAccount AccountRemove;
    custAccount AccountMerged;
    custTable   custSource;
    custTable   custMerged;
    SalesJournalAutoSummary SJAS;
    GatewayOrgRef   GOR;
    smmBusRelTable  SBRT;
    SalesPrintCopies    SPC;    // Added

    AccountRemove   = "AccountSource";
    AccountMerged   = "AccountDestination";

    ttsbegin;

    delete_from SJAS
    where SJAS.CustAccount == AccountRemove;

    delete_from GOR
    where GOR.RefType == SysActionRefTypes::Cust &&
  GOR.RefId   == AccountRemove;

    delete_from SBRT
    where SBRT.CustAccount == AccountRemove;

    delete_from SPC
    where SPC.CustAccount == AccountRemove;

    custSource  = CustTable::find(AccountRemove,true);
    custMerged = CustTable::find(AccountMerged,true);

    custSource.merge(custMerged);

    ttscommit;

}

/Jens
  -Oprindelig meddelelse-
  Fra: Danny Gaethofs [mailto:[EMAIL PROTECTED]
  Sendt: 18. november 2004 19:19
  Til: [EMAIL PROTECTED]
  Emne: 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.