RE: [Axapta-Knowledge-Village] Sales Order - Question

Thu, 30 Jun 2005 16:54:39 -0700

hi
 
ValidateWrite may not be the correct way to go for since this method will be called only if the update is being called from the form. This is why a lot tables have validations written on the update method.
 
regards
 
harry

Brandon George <[EMAIL PROTECTED]> wrote:
Well this is great conversation! Thanks for your input, and I believe that I found the Solution:
 
 Override the ValidateWrite and ValidateDelete methods. Adding code that would transfer the information from the SalesLine to our Web Database at this point seems to work every time.
 
@ harry:
    Did you consider ValidateWrite / ValidateDelete methods? After doing some research it seems that these methods are called every time no matter what, when it comes time to actually write a Line in ANY table for that matter.
 
-Brandon

From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Harry (Harshawardhan Deshpande
Sent: Thursday, June 30, 2005 5:35 PM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] Sales Order - Question

hi Brandon
 
this email is just for the sakes of complete discussion.
 
it is not necessary tha the update and insert methods on a table will be executed. The logic may go for doInsert and doUpdate. though I cant think of a scenario where doInsert/Update methods are called for sales table it may be worthwhile to check this out especially the modifications developed by your programmers (I have seen a lot of times that programmers will uncessarily call the doInsert/update methods).
Another problem that you are going to face is ttsabort. If a transaction is inserted into the database and later aborted then there is no easy way to get hold of this abort statement.  You can avoid this problem to a great extent by putting your code after the ttscommit statement (if any) in the insert/update method
 
I have not checked all the code but one place where you will be completely lost will be if a piece of code is creating a sales order and there is a tts loop at the higher level. For e.g. may be creation of inter-company orders etc. Or may be auto creation of sales lines.
 
I would give a serious thought to writing triggers in sql server.  I am aware that sql server is a black box for Axapta and believe me I personally hate doing such triggers but in your case it may be the correct way to go.
 
regards
 
harry
 
 
-----Original Message-----
From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED]On Behalf Of Brandon George
Sent: Thursday, 30 June 2005 8:39 AM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: [Axapta-Knowledge-Village] Sales Order - Question

Hello all,
 
    Ok let me give you some information, that will hopefully help explain what I am trying to do. You see we have a Web Site and Database structure for that website in place. We are currently implementing Axapta, and in order not to change to much at once, we are wanting to replicate data from Axapta to our Web site database.
 
In order to do this, I am wanting to run a piece of code every time a Sales Order is created that would replicate that Sales Order to our web site database.
 
Does anyone have a clue as to the best way to do this? Is there a class that is always called when a new Sales Order is created? I figure SalesAutoCreate, but I am not so sure.
 
Anyway thanks in advance! And please let me know if you don't understand that question and I can give more details!
 
thanks,
Brandon


Sharing the knowledge on Axapta.



Sharing the knowledge on Axapta.



Sharing the knowledge on Axapta.

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

Sharing the knowledge on Axapta.



Sharing the knowledge on Axapta.

Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football

Sharing the knowledge on Axapta.


YAHOO! GROUPS LINKS



Reply via email to