Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1040639
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T15:14:57+00:00 2026-05-16T15:14:57+00:00

and once again an axapta-question ( running on ax 2009 and sql-server 2008 r2

  • 0

and once again an axapta-question ( running on ax 2009 and sql-server 2008 r2 ):
which is exactly the point of time, when inserted or updated datasets are stored in the regarding database?

the aim is to call a stored procedure on the sql-server which transfers data from the ax-tables ( eg inventtable ) to another ( not generated with axapta ) table. executing the stored procedure via odbc from axapta on one of the table-methods ( even after super() call ) triggers the stored procedure, but the data which was just added or modified in ax isn’t found while selecting via smss ( select * from dbo.inventtable ).

the only place i know yet where the data is already stored in db is on the methods on the datasource on the regarding form, but this would be quiet ugly, since the data could be edited via n forms from ax.

so is there a way to put the call on the table instead on the forms’ datasources?

thanks for hints in advance!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T15:14:57+00:00Added an answer on May 16, 2026 at 3:14 pm

    The AX data is “stored” in the database at the point of doInsert()/doUpdate() or super() calls in insert()/update() methods.

    However, as Jay mentioned, the records will not be visible to other transactions (unless you explicitly allow dirty/uncommitted selects). So it may not be visible to your stored procedure.

    I would not recommend calling stored procedures in insert()/update() anyway as this has performance implications, and you are now depending on yet another database being alive!

    The way to go:

    1. log insert/update in a separate table for that purpose (consider using standard database logging).
    2. From the other database regularly monitor the log for new records (say every 15 seconds).
    3. Do your insert/update in the other database based on a join of the log and the AX table.

    Log table layout (one of millions):

    • LogType – 1=insert, 2=update, 3=delete
    • LogStatus – 0=not transferred, 1=under transfer, 2=transferred, 3=error???
    • RefRecId – RecId of AX record
    • RefTableId – TableId of AX table (if you need to log more than one table)
    • RefCompanyId – Company of AX record (maybe the table is shared virtually)

    Recommendations:

    1. Use RecId as the join key and remember to enable RecId index on the AX table.
    2. Remember to select on DATAAREAID (must be spelled this way) as well.
    3. Update the LogStatus to 1 before the join and to 2 after the join and update.
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Having once again been bitten by SQL Server not updating all views properly when
Once again a question about the garbage collector in actionscript-3: If I have a
Once again I need your Help, am thanking you as every time you helped
Once again a question about extjs. I use EXT 4.0.2 and have a couple
Once again working on Project Euler, this time my script just hangs there. I'm
Once again I have a problem which I can't find the solution to. A
My apologies once again for asking another very junior question. For one reason or
Once again, I have my form_for for my Order model, which has_many :services, :through
I'm looking once again for help from the collective. I created a site which
I am once again writing an external debugger visualizer, and am running into a

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.