Navision TechNet

Seite 1 von 2

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: Mar 14 2000 (Read by 1232 users)

Troubleshooting guide to Axapta WebApps This article guides you through solutions to the most common problems that are encountered when working with Damgaard Axapta WebApps. When working with the Damgaard Axapta WebApp framework, it is important that all the used technologies are set up correctly. The WebApp framework uses the following technologies:
Damgaard Axapta (2-tier or 3-tier).
The Axapta COM Connector.
Microsoft Transaction Server.
Microsoft Internet Information Server (or MS Personal Web Server).

My browser displays an empty page after I have deployed a WebApp using the Web Application Wizard. All WebApps uses a number of predefined files that are copied to the IIS upon completion of the Web Application Wizard. The right path to these files has to be specified. By default, this path is defined relatively to the directory where Axapta is installed. You can specify the path to the Web Application files in the Web Applications dialog that is found under Tools > Development > Web Development in the top menu. Make sure that the path can be accessed from the Axapta client from which you are running the Web Application wizard. The COM Connector uses the AxConfig to determine what Axapta application to log on to. Make sure that AxConfig is installed on the same server as where you have set up the COM Connector in MTS, and that the right system directory is specified. Further, you must specify a user in AxConfig, since the COM Connector logs on to Axapta using this setting. The user that you specify must of course have the proper access rights to the functionality that you are using in your WebApp. It is highly recommended that you run the COM Test to ensure that the COM Connector is set up correctly. To do this, launch the Axapta client from the Server where you have set up the COM Connector. Open the Parameters dialog under Internet > Setup. On the COM status tab, click Test. The COM Test performs a test that logs on to the COM Connector and checks if it is possible to run X++ code in Axapta. It may be that the Web site that you have created in IIS is not started. The changes that I make in MorphX does not show in my WebApp. This is most likely because you are running in a 2-tier mode. To see the changes you must shut down the COM Connector in MTS.

Article posted under: Navision Axapta, WebApp Framework, WebApps.

Discussion based on this article: Help

View: All Disc:#123 Subj: (Multiple) Art: Troubleshooting guide to Axapta WebApps

123.1 Problems accessing a Webapp (erik.larsen, 19 Sep 2000 07:41:28 CET) , 19 Sep 2000 08:46:48 CET) 123.2 Accessing a webapp (Palle Agermark [MSFT]

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 2

123.3 Com licenses? (abj, 20 Sep 2000 00:46:10 CET) 123.4 It's probably the way you write the web server name (kiha, 20 Sep 2000 13:42:29 CET) 123.5 Check out thread # 108.2 (ksc, 20 Sep 2000 16:29:38 CET) 123.6 Elaboration (erik.larsen, 25 Sep 2000 10:01:15 CET) 123.7 yes and no. (bda, 27 Sep 2000 13:47:45 CET) 123.8 Hi ! ! Eric (sbhatt, 27 Sep 2000 17:26:47 CET) 123.9 Problems accessing a Webapp (mah, 01 Oct 2000 00:12:26 CET) 123.10 After creation of Web Forms (sbhatt, 03 Oct 2000 13:43:55 CET) 123.11 Saving Data (christen, 04 Oct 2000 16:50:30 CET) 123.12 Hyperlinks in CSS (sbhatt, 04 Oct 2000 18:15:46 CET) 123.13 Calling another webform programmatically (christen, 05 Oct 2000 09:06:29 CET) 123.14 Without Coding (sbhatt, 05 Oct 2000 11:49:05 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 2

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: Mar 09 2000 (Read by 700 users)

Executing SQL directly from X++ The X++ language supports a number of ways to execute native SQL against any SQL data source. Below are two samples for retrieving data as well as manipulating data. Please be aware, that SQL can be really powerful, and it should be used as such.

Example #1: Retrieve data: Since this example uses a void Sample_1(void) { Connection Con = new Connection(); Statement Stmt = Con.createStatement(); ResultSet R = Stmt.executeQuery('SELECT VALUE FROM SQLSYSTEMVARIABLES'); while ( R.next() ) { print R.getString(1); } }

Example #2: Manipulating data (deletion): Since this example uses an void Sample_2(void) { OdbcConnection C; Statement S; LoginProperty LP = new LoginProperty(); LP.setDatabase("SampleDb"); LP.setDSN("MSAccess97"); LP.setUsername("dba"); LP.setPassword("secret"); LP.setOther("MODE=1;PATCH=32"); C = new OdbcConnection(LP); S = C.createStatement(); S.executeUpdate("DELETE FROM DummyTable"); }

Article posted under: Databases (Ax).

Discussion based on this article: Help

View: All Disc:#12009 Subj: (Multiple) Art: Executing SQL directly from X++

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 2

12009.1 Partial result after executing SQL procedure (isoftsa, 15 Feb 2005 11:46:04 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back | Start a discussion based on this article The information in this article applies to: Damgaard Axapta v2.1 Published: Mar 09 2000 (Read by 43 users)

Monocase in Axapta Since Damgaard Axapta is case insensitive, it will have to make a case-sensitive database act as if it does support case-insensitive searches monocased.
Article posted under: Databases (Ax).

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 2

Back The information in this article applies to: (None) Published: Mar 09 2000 (Read by 649 users)

Performance check list for Axapta installations This checklist is intended to be a guide on how to determine the causes of perceived data access performance problems in Axapta. It is not a guide on how to tune an Oracle or SQL server installation. 1. You will need to populate your application tables with a realistic amount of data to make any evaluation of the applications performance. This is due to the fact that with sufficiently small amounts of data, it will not matter whether the access is via indexes or via a table scan. 2. If you are running Oracle, be sure to run the “calculate statistics” found in the administrator database menu’s before evaluating performance. 3. Run your Axapta application with querytimeLimit: 2000, this will list all SQL that runs for more than 2 seconds in the sql.log file. This will give a first indication of which statements to investigate further. It will not however reveal faulty logic, like performing a well performing SQL statement so many times that it becomes critical for performance. The latter type of problem can be found incorporating homegrown timing logic. 4.

For each of the long-running select SQL statements think about :

—

Does the accessed table have an index that matches the where clause used. See Axapta and Indexes

— Have you given the optimiser all available information, that is, does the where clause include all known information. Specifying FirstFast is also information to the optimiser telling it to favour retrieval of the first row over the total retrieval time. — Does the statement include an order by that is not essential? An order by forces either access via an index that matches the order by, or a sort. A sort of a large result-set will degrade the performance because all records have to be retrieved and sorted before the first record can be presented. 5.

For each long-running insert SQL statement, think about:

—

Are there many “long” indexes on the table? See Axapta and indexes

—

Is the table index organised on a key that is continually ascending? See Axapta and Indexes

—

Does it have unnecessary containers?

6.

For each long-running update SQL statements, think about:

—

Are there many “long” indexes on the table, which include the updated column?

—

Does it have a clustering index, which includes the updated column?

Article posted under: Databases (Ax).

Discussion based on this article: Help

View: All Disc:#88 Subj: (Multiple) Art: Performance check list for Axapta installations

88.1 QueryTimeLimit in Axapta 2.0 (Trasbo, 31 Aug 2000 16:01:49 CET) 88.2 querytimelimit in Axapta 2.0 (ebb, 31 Aug 2000 21:58:11 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 2

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 2

Back | Start a discussion based on this article The information in this article applies to: (None) Published: Mar 09 2000 (Read by 52 users)

Database Connections in Axapta Describes the concept of SQL database connections in Axapta, including connection pooling, command line parameters, and performance monitor features. What is a database connection? A database connection comprises a driver and a data source. A connection handle identifies each connection. The connection handle, referred to simply as the “connection” in this document, defines not only which driver to use, but also which data source to use with that driver. Each connection holds a number of various information: Transaction state, inactive SQL statements for re-use, fetch-ahead buffered rows, etc. Multible standard connections Axapta internally uses a number of different flavors of connections: One is used primarily for sequencenumber generation, and other system management tasks. This connection is referred to as the system connection. The second kind of connection is an application connection, which generally is used for running the business logic of the application. In special cases, however, the kernel uses a read-only connection, which is similar to the application connection, but it expects no data manipulation operations, e.g. updates. From a database point of view, any of these connections are handled as separate user logins. All standard connections inherit the login properties of the system connection. Optional user-connections The X++ language provides a number of ways to have “user defined” connections. This is accomplished by instantiating classes of type Connection, UserConnection, or OdbcConnection (refer to the “Axapta Developer’s Guide” for details). The Connection class provides a hook into the currently open connection, typically the application connection, meaning that it runs in the same transaction space as the application connection. The UserConnection, however, provides a new database connection with the same properties as the application connection running in its own transaction space. This is used in the standard Axapta application to handle number series. The third kind of user defined connections is the OdbcConnection, which let the programmer/user access any ODBC data source by providing data source name (DSN), user name, and password. Connection pooling Logging in and out of a database is sometimes fairly time consuming. Therefore Axapta will try to minimize on-the-fly login/logout. On the other hand, keeping in-active database connections open will hold resources on the database server, as well internally in Axapta. Therefore Axapta will try to keep connections open just as long as clients requests connections. To accomplish these two tasks, Axapta maintains a pool of open, unused connections. That is, whenever the business logic requires a connection, the kernel will check for any usable connections in the connection pool, and supply one from the pool, if possible. If not, a new connection is opened transparently for the user. Whenever the application has completed its task, the connection is moved to the connection pool. That means, that an inactive Axapta client (e.g. end-user out for lunch), will hold no open database connection. Another consequence of this approach is, that when the client logs off, the database connection is kept open (two-tier eventually disconnects instantaneously) to be used by other clients. But when is disconnection to the database done? Well, two situations will cause a database logout: First, when Axapta Object Server terminates, the connections obviously have to be closed. Second, a time-out mechanism is provided, so connections, which have not been in use for the last 60 seconds, will be closed transparently for the users. This time-out threshold is configurable, of course. Active connections per client The number of open connections per client is very much depending on the type of work done by each client/user. All clients will always shared the system connection, which is kept open all the time. Clients browsing data in Forms will typically a read-only connection open (actually data may have been retrieved and buffered, and the connection can be returned to the connection pool ). Whenever updates, deletes, or inserts are made (from Forms or tasks in the application), the read-only connection is either replaced by an application connection, or, if the read-only connection is still in use, by a new application connection. This will potentially require two database connections, excluding the shared system connection, for the client. On top of that, the application code may itself invoke user connection (such as the Axapta number series system does) as needed. ODBC connection pooling

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 2

The ODBC Driver Manager has its own generic connection pooling feature, but since the built-in Axapta connection pooling is tailored to satisfy the needs of the Axapta kernel and application, it is recommended not to enable the ODBC connection pooling on the driver used by Axapta. Performance monitor In the Performance Monitor you can, among other interesting things, follow the number of connection in use, “SQL connection – active”, as well the number of inactive, cached connections, “SQL connection – inactive”. Please notice that this is an Axapta Object Server only feature. Command line parameters A command line parameter can set the threshold timeout period for the connection pool to any duration: -INTERNAL=CONNECTIONPOOL:nSeconds where ‘nSeconds’ is a positive number of seconds to wait, before unused connections are flushed. This parameter will in future versions be incorporated in the Axapta configuration utilities. Two-tier vs. three-tier Most of the issues described in this document apply for Axapta three-tier clients, as well as two-tier clients. Exceptions does exist, however, as the performance monitor feature mentioned above.

Article posted under: Databases (Ax), Databases (XAL). © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 2

Back | Start a discussion based on this article The information in this article applies to: (None) Published: Mar 14 2000 (Read by 515 users)

WAP with Axapta 2.1 Learn how you can use the Axapta COM, and Internet Connector to create Axapta-integrated WAP solutions with Axapta 2.1. The article also contains links to WAP information sources.

Introduction
As such there is NO direct WAP support in Axapta 2.1.
We are in the process of researching and developing WAP interfaces and applications, but does not have

any timeframe for release of these features yet.
It IS possible to implement WAP applications with Axapta integration in Axapta 2.1, and I will try to

describe the steps you need to take here.

Learn about WAP and WML First of all, to get a good understanding of what WAP and WML is, and how these technologies relate to the Internet and HTML - I suggest you take a look at these resources: http://www.nokia.com/corporate/wap Nokia is one of the co-founders of the WAP Forum, and makes mobile phones that support the WAP protocol, and has a WAP browser integrated. At their WAP site, you will find whitepapers describing WAP, WML, The Nokia 7110 features and limitations (there are many). Nokia also makes a WAP server wich is available in a free beta. The WAP server is only neccesary if you want to make your own WAP gateway to access servers inhouse for example. http://www.wapforum.org Wapforum is the original forum for all companies and individuals developing hardware and software solutions that use the WAP specification. Whitepapers and technical information is available, and it's free to join. http://www.ericsson.com/letswap Ericssons WAP-site. http://www.microsoft.com/WIRELESS Microsoft's site about wireless solutions - with sections on WAP.

Axapta WAP Integration To integrate Axapta in a WAP solution you use the same technology as for building Internet solutions: The Axapta COM Connector. You can even use the Axapta Internet Connector if you create your WAP solution on Internet Information Server. An important step in being able so make WAP solutions on IIS is to create mappings for the WML MIME types. Download the Nokia WAP toolkit from the Nokia site mentioned above, and read the "Getting started" manual that explains this, and lists the MIME types in question. When you have done this, you can create an X++ class that writes WML back to IIS, and create a testwap.asp page that calls this class. From there on it should be straightforward to enhance this into a working sample application. One caveat is that the session object is NOT supported in some/most of the available WAP browsers at the moment, so don't rely on the IIS session object for storing state information. You will have to pass parameters on the URLs when you switch between pages in your application.

Axapta 2.1 WAP Sample Here is a small sample of a WAP page calling an X++ class. Make sure that you have IIS running, The Axapta COM Connector working with the Web TestApp, and that you have registered at least the .wml MIME type on IIS (select properties on the Webserver node in IIS Manager - click MIME Types, and create the wml type mapping to "text/vnd.wap.wml" as described in the Nokia "Getting Started" document Next copy the two ASP files shown below to a directory on your webserver, f.ex. c:inetpubwwwrootwapsample. Import the .xpo file into Axapta, creating the WapSample class. Now you should be able to start a wap-browser (for instance the one in the Nokia Toolkit) and browse to http://yourserver/WapSample (if you placed the ASP files in the suggested directory, and your IIS is installed with default options). If you are using the Nokia toolkit, the easiest way to do this is to create a Bookmark, on

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 2

the Bookmarks tab, and typing the URL. Now click GO and the phone-emulator should show the output from Axapta. If you have any problems, please check that the COM-Connector is working properly. To show passing of parameters to Axapta, try changing the URL to http://yourserver/WapSample?user=Stofa and press go again. You should be able to see Axapta reading the User parameter, and writing it back to the Phone. Please note that Damgaard does not provide support on WAP, WML, WAP Server, Gateway and Emulators. We do of course provide support on the COM and Internet Connector through normal channels. Good luck with your Wap-Applications. Axapta Internet & Business Integration.

Download files: wapsample.zip [1K]

Article posted under: Navision Axapta, Technology (Ax), Axapta COM Connector, WebApp Framework. © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 2

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: Mar 16 2000 (Read by 689 users)

Securing Axapta WebApps When dealing with ERP systems and the Internet, security is a sensitive issue. And rightfully so, since it involves exposure of sensitive data. However, with the right infrastructure it is possible to secure your Axapta WebApps to a satisfactory level. This article describe how to set up Axapta WebApplications with the best possible security. Overview This article is divided into two sections. The first section provides a description of the technologies used to secure Axapta Webapps. The second provides guidelines on how to do the actual implementation of the security infrastructure. Firewalls A firewall is used to protect access to resources on a private network from another network. Whether Axapta WebApps are used on an intranet or the Internet, a firewall is the foundation of a secure infrastructure. Secure Sockets Layer (SSL) SSL is the industry standard used to encryp the information that is sent to and from a Web server. In this way all the information that is extracted from the Axapta database such as sales prices, costumer information, passwords, etc., is encrypted before it is sent to an Internet browser, and so is the information that e.g. a customer using the Customer Self-Service WebApp is sending the other way. Implementation The figure below gives an overview of the technologies that take part in the security setup.

Axapta is installed on a local area network (LAN) where a firewall is used to protect the access from the IIS. By using Windows NT domain security it is possible to limit access to Axapta via IIS to users that are registered in a domain on the LAN. When dealing with Intranet WebApps this is useful since users of such a solution are most likely to be members of a coherent domain. By utilizing the Axapta Object Server technology, the communication between the Axapta processes running on the IIS and the middle tier (Axapta Object Server) will be based on the Axapta Object Communication Protocol (AOCP). AOCP is build on basic TCP/IP services and designed to allow simple handling of firewall configuration. On the outside of the LAN another firewall protects access through the HTTP protocol. On the IIS you can define what protocols you want to open to the outside world. Often people are concerned when submitting passwords and other sensible information over the Internet. The SSL protocol is a way to encrypt such information, and is supported by IIS. All that is needed is key that can be acquired from Verisign. More information on security Microsoft has a lot of valuable information about security on their TechNet site.

Article posted under: Implementation, WebApp Framework, WebApps.

Discussion based on this article:

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 2

Help

View: All Disc:#8660 Subj: (Multiple) Art: Securing Axapta WebApps

8660.1 Correct image URL (InnocentBystander, 26 Nov 2003 14:21:06 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 2

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: Apr 26 2000 (Read by 519 users)

Upgrading Damgaard Axapta Brief summary on preferred method of upgrading Damgaard Axapta.

Upgrading This chapter explains briefly the recommended procedure for upgrading between service packs as well as between major versions. There are two things that needs to be considered when upgrading from one version/service pack to another.
Data
Modification

Data Normally data upgrade is handled by the upgrade wizard within Axapta. All changes done in the data dictionary and related data that needs to be converted is initiated from the wizard. Data conversion will likewise be initiated if you use the data export/import to import data from a previous version. However if you have created new tables and/or fields that depends on data that is removed or moved you may have to update this data.

Modifications If you have done modifications you need to verify these and eventually make changes according to the changes made in standard Axapta. The below is the recommended procedure, Upgrading between service packs After finishing applying the service pack and completing the upgrade wizard Axapta is now running on the new service pack with your modifications still based on the previous SP. When applying a service pack the old application files are stored (in the applold folder). This enables comparison between the old and current elements. When doing service pack upgrades this is the recommended procedure,
Apply the new service pack and complete all steps in the upgrade wizard
During the upgrade wizard you can choose to create an upgrade project. Otherwise you may

manually create a new project and apply a filter that brings all elements in the VAR and USR layer into the project
Consider the following (make sure that tools/options/development/sow all layers is checked)

- elements that only exists in the USR/VAR and SYS layer will in most cases work because the service pack have not introduced any changes to the element - elements that exists in the SYS, SYP and/or VAR/USR will have to be examined. Start by comparing the SYP with the OLD SYP. If they are the same the element will in most cases work because the service pack have not introduced any changes compared to the previous SP. If the SYP and OLD SYP are NOT the same you will have to compare the SYP with the VAR and /or USR and recreate modifications. Version upgrade In general version upgrades are done very similar to upgrading between service packs. However one important thing to remember is, that you can NEVER SKIP a version. For instance, it is NOT POSSIBLE to upgrade directly from version 1.5 to version 2.1. You always need to go from 1.5 to 2.0 and then to 2.1. The reason for this is, that data needs to be upgraded and that fields in special cases can be deleted between versions. However, you only have to upgrade you own modifications once.

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 2

The preferred method to upgrade from 1.5 to 2.1 would be,
Apply the first consecutive version (2.0) and complete all steps in the upgrade wizard. This will

update data from 1.5 to the version 2.0 level. You do not need to upgrade your own modifications yet.
Depending on whether or not there a service pack has been released for the new version, you

should do the following: If no service pack is released yet on the new version you should apply the base version (2.1) and complete all steps in the upgrade wizard. This will update data from 2.0 to the base version 2.1 level. If a service pack has been released you should first apply the base version (2.1) WITHOUT starting Axapta. You should then continue directly with applying the latest service pack and make sure to check the option "part of a upgrade" when doing so. Next, you start Axapta and complete all the steps in the upgrade wizard. The data will now have been updated to the newest version (2.1) and newest service pack (E.g. SP 2). Then continue with:
If you have not chosen to let the wizard create an upgrade project you may do it manually and

then apply a filter that brings all elements in the VAR and USR layer into the project
Consider the following (make sure that tools/options/development/sow all layers is checked)

- elements that only exists in the USR/VAR and SYS layer will in most cases work because the service pack have not introduced any changes to the element - elements that exists in the SYS, SYP and/or VAR/USR will have to be examined. Start by comparing the SYP with the OLD SYP. If they are the same the element will in most cases work because the service pack have not introduced any changes compared to the previous SP. If the SYP and OLD SYP are NOT the same you will have to compare the SYP with the VAR and /or USR and recreate modifications.

Article posted under: Implementation.

Discussion based on this article: Help

View: All Disc:#22 Subj: (Multiple) Art: Upgrading Damgaard Axapta

22.1 Upgrade project? (Tadorna, 24 Jul 2000 10:38:54 CET) , 07 Aug 2000 20:19:53 CET) 22.2 Agree (flr

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: May 04 2000 (Read by 545 users)

AOS printing reports to local client printer The Axapta 2.11 technology release will offer AOS clients to print to local printers not known to the server. When printing in the AOS environment, prior versions has been bound to printing to printers known by the machine generating the report. This implied that a report running on the server could only be directed to a printer available for the server (ie. network print queue or printer connected directly to the server). With Axapta 2.11 client printers will be accessible to the server without any installation (direct or hidden) of printerdriver etc. on the server. This will greatly enhance the flexibility of server generated reports without adding administrative overhead to the server environment caused by registering all the client printer drivers on server.

Article posted under: Axapta Object Server.

Discussion based on this article: Help

View: All Disc:#5329 Subj: (Multiple) Art: AOS printing reports to local client printer

5329.1 Printing Picking list from production (me, 31 Oct 2002 18:19:41 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 2

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: May 04 2000 (Read by 816 users)

Quick&Dirty: Access AOS through a network firewall For security reasons an AOS will sometimes be shielded from the clients by a firewall. This will work if firewall is configured properly for Axapta Object Communication Protocol (AOCP). Information applies to Axapta Version 2.1 The scenario when client connects and runs is described below with notes on what to allow passing through the firewall: 1.

To allow client to create the connection to the given AOS it must first know which port the AOS is running at. To establish this it contacts the Server Manager by use of an udp package to the servers port 2712/udp. This package must pass through to the server (firewall must be open for incoming udp trafic from * to port 2712 of the server).

2.

The server replies to this with a specification of where requested instance is running. This is in the form of a udp package to the clients source port of original udp package. Source will be port 2712 so firewall must allow udp trafic from server port 2712 to any destination.

3.

The AOS instance will run its listener at a given tcp port which can be specified in the server settings of the instance. Clients must be able to establish connection to this port (eg. 3000). This applies that the firewall must allow tcp trafic from any client, any port to the servers port 3000 (or what ever port choosen).

4.

For the server to communicate back to the client, trafic must be allowed through the firewall for tcp from servers port 3000/tcp (or what ever port choosen in server instance configuration) to what ever port on the client.

This means that firewall rules should allow (for server instance running at port 3000): 1.

udp trafic to and from servers port 2712/udp - this is to allow the client to locate the port to contact for a given AOS instance. Version 2.11 will support connect syntax specifying AOS instance port which will remove the requirement for passing udp through the firewall.

2.

tcp trafic to and from servers port 3000 (or what ever port choosen) to and from any client and port.

If client when starting responds with message No Axapta Object Server found it will in most cases be one of these two causes: 1.

The specified AOS instance (by name in client configs server mask) is in fact not running at the given network node. Solution is to get the server instance running.

2.

The udp sequence establishing location of the AOS instance is blocked on in or outgoing trafic. Revise rules in firewall and if needed use sniffer or other network monitor to ensure that packages (one in and one out) passes through.

It is very important that the firewall exposes the real ip address of the AOS network node (Windows NT Server). The udp reply to the client contains a connect point reference containing both ip address and port number as advertised by AOS so this must be the same as the client needs to connect to. Otherwise it will not presently work. This means that address remapping should not be performed for the AOS servers.

Article posted under: Axapta Object Server, Axapta COM Connector.

Discussion based on this article: Help

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 2

View: All Disc:#38 Subj: (Multiple) Art: Quick&Dirty: Access AOS through a network firewall

38.1 Address remapping should not be performed for the AOS servers (evz, 10 Aug 2000 09:00:47 CET)

38.2 Re: Address remapping should not be performed for the AOS servers (jsh, 10 Aug 2000 23:26:50 CET)

38.3 website in 2.5 (kiha, 04 Apr 2001 12:02:39 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back | Start a discussion based on this article The information in this article applies to: (None) Published: May 04 2000 (Read by 401 users)

My Axapta will not start due to errors in the startup sequence! Admitted - sometimes even an experienced X++ programmer makes mistakes. When dealing with system startup code making mistakes often results in a completely useless system. Modifying the code run when starting Axapta (the sequence spawned from Application.Startup()) can sometimes result in introducing a fatal error situation preventing Axapta to start. In such situation use following to get system running again. 1.

Try to startup in real 2-tier mode. If this succedes locate and remove/rewrite the code causing the problem.

2.

If 2-tier won't start either, put the option -noauto in the Advanced field in the configuration for the 2-tier client, logon and remove/rewrite the code preventing startup.

When running 3-tier with the Axapta Object Server, situations can be reached where the AOS will not startup. This can be caused by startup code accessing objects bound to the Axapta client which will not be available for the initial AOS session. Use above solution for these problems also or if 2-tier client is not available, apply the -noauto to the servers configuration and start it and logon thin client to cure problem. Final note: Always remember to remove the -noauto again to return to normal operation.

Article posted under: Technology (Ax). © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back | Start a discussion based on this article The information in this article applies to: (None) Published: May 08 2000 (Read by 415 users)

Damgaard Axapta Foundation Classes teaser This new document describes the new Axapta Foundation Classes. These classes are high performance container classes (lists, sets, maps, arrays and structures) that may easily be used from both the application and the kernel.

Download files: AFC.doc [1277K]

Article posted under: Navision Axapta, MorphX. © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: May 25 2000 (Read by 917 users)

COM in Axapta 2.1 Axapta version 2.1 offers a lot of possiblities in making use of COM technologies. This technical whitepaper discusses using the Axapta COM Connector, Using DCOM, using COM object in Axapta, and using ActiveX Controls in Axapta forms.

Download files: Axapta COM Connector.doc [211K]

Article posted under: Axapta COM Connector, WebApp Framework.

Discussion based on this article: Help

View: All Disc:#162 Subj: (Multiple) Art: COM in Axapta 2.1

162.1 Clarifycation of COM versus DCOM (cho, 06 Oct 2000 09:43:51 CET) 162.2 COM - DCOM (Alex, 06 Oct 2000 15:55:40 CET) 162.3 RE: Clarifycation of COM versus DCOM (bgk, 07 Oct 2000 01:41:07 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back | Start a discussion based on this article The information in this article applies to: (None) Published: May 30 2000 (Read by 585 users)

Queries understand general expressions Learn a few usable tips about queries. Sometimes the expressive power of the dot notation in queries (e.g 1 .. 10) is not powerful enough. Typically, you need to find records where either either one or the other subexpression hold true. Another need that may arise is the need to express a relationship between datasources that do not have a direct father/son relationship. Both these needs may be addressed by using expressions in lieu of the dot notation strings. This is done by supplying an arithmetic expression in parenthesis in the range value. It is crucial that parenthesis are used, because this is the way that queries determine what kind of expression it is dealing with. The expressions may contain the usual arithmetic operators and the usual logical (boolean) operators. Use plenty of parenthesis to properly group subexpressions. Example: You wish to select only records where the amount in currency is less than 100 or greater than 2000. Create a query containing a datasource assigned to the CustTrans table. Create a range and enter the expression ((amountCur > 2000.0) || (amountCur < 100.0)) Note the use of the parenthesis. It makes no difference what datasource the range containing the expression is attached to. Records from differnt datasources may be fetched by using the datasourcename . fieldname notation. If no datasource name is supplied, the datasource to which the range belongs is used. Please note carefully, that the DATASOURCE name is used, not the name of the table attached to the datasource. The mechanism described above is not very forgiving in terms of syntax errors (misplaced operators etc) or semantic errors (references to nonexistent fields, type conflicts etc). In fact, errors are simply ignored.

Article posted under: MorphX. © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back | Start a discussion based on this article The information in this article applies to: (None) Published: May 31 2000 (Read by 153 users)

Triangulation What happens when the primary currency is triangulated ? Please note that if you have marked the triangulation field on the primary currency under General ledger/Currency/Exchange rates all other currencies will be triangulated. This can be seen when entering the exchange rates on the other currencies, then the rates will be shown against the triangulation currency no matter whether the triangulation field is marked or not.

Article posted under: Financial Series. © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back The information in this article applies to: (None) Published: Jul 13 2000 (Read by 541 users)

Damgaard Axapta - Web Deployment The Axapta Web Deployment Client is a tool that allows easy deployment of Damgaard Axapta through the Internet or an intranet. The user does not have to deal with installation CDs, answering scores of questions during installation etc.; the installation options are set up centrally, once and for all. The user simply clicks on a button on a Web page and all the installation details are dealt with automatically. The attached document describes how to set up the Damgaard Axapta Web Deployment Client that eases the implementation process. Open the document (Word format) by clicking the link on the right.

Download files: Axapta Web Deployment Client.doc [658K]

Article posted under: Implementation.

Discussion based on this article: Help

View: All Disc:#1717 Subj: (Multiple) Art: Damgaard Axapta - Web Deployment

1717.1 ServerServicePack and CommandLineServicePack parameters (dschwantes, 03 Jul 2001 17:44:16 CET)

1717.2 Can you send me SP1 (hoffmanc, 18 Jul 2001 17:28:18 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 2

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: Jun 08 2000 (Read by 483 users)

Cleaning up a sick AOD file Tips on how to clean up an AOD file with "false" compile problems especially during upgrade If you have tried to upgrade a 1.5 or 2.0 to a 2.1 version or if you have tried to bring together a number of AOD files (for instance install option packs, local soution layers, USR layer etc.) you probably have experienced compile problems that should not occur. You may for instance get a compilation error on the parameters in a method call - even though the parameters are completely correct according to the method definition. The reason is most likely that the AOD file contains some internal old information (headers) that do not match the truth. These old internal table and class headers can mean that the compiler gets confused and reports compile errors when there really are none. The solution is to run the following job, which deletes all internal headers followed by a complete re-compile (which rebuilds them again), static void deleteHeaders(Args _args) { UtilElements utilElements; while select utilElements where utilElements.recordType ==UtilElementType::ClassInternalHeader { utilElements.delete(); } while select utilElements where utilElements.recordType ==UtilElementType::TableInternalHeader { utilElements.delete(); } } Best regards, Flemming (solution courtesy by Christian Madsen, who have promised to include this in the standard version)

Article posted under: Navision Axapta, Technology (Ax).

Discussion based on this article: Help

View: All Disc:#2613 Subj: (Multiple) Art: Cleaning up a sick AOD file

2613.1 Contents of AOD file (dritter, 06 Nov 2001 17:18:41 CET) 2613.2 Contents of AOD (SvenJoc, 13 Nov 2001 18:29:56 CET) 2613.3 I'm also interested (arjones, 14 Nov 2001 02:56:39 CET) 2613.4 Version control (vcs) in Axapta (erda, 02 Jun 2003 14:32:51 CET) 2613.5 yes yes (byteway, 02 Apr 2004 20:12:10 CET) , 03 Apr 2004 11:08:17 CET) 2613.6 Standard in 4.0 (Kim Moerup [MSFT]

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 2

2613.7 downgrade (erik.larsen, 07 Dec 2004 15:33:21 CET) , 08 Dec 2004 16:42:28 CET) 2613.8 Don't think so (Kim Moerup [MSFT] 2613.9 Microsoft Axapta VSS integration (dilipn, 11 Dec 2004 05:02:52 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: Jun 15 2000 (Read by 557 users)

WebApps and the Oracle database Contrary to common belief, Axapta WebApps DO run on the Oracle database! When the Customer Self-Service WebApp was released in Axapta v2.1, it did not work with the Oracle database since the multi-threading features of the COM Connector did not work with the drivers provided by Oracle. However, in Service Pack 2 for Axapta v2.1 this problem has been solved and a working driver is now availabe.

Article posted under: WebApp Framework, Databases (Ax), Oracle, WebApps.

Discussion based on this article: Help

View: All Disc:#68 Subj: (Multiple) Art: WebApps and the Oracle database

68.1 Working driver is now avilable (npa, 24 Aug 2000 08:33:50 CET) 68.2 Appropriate Oracle ODBC driver and client sw is distributed with Axapta (JEF, 24 Aug 2000 13:50:07 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 4

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: Damgaard Axapta v2.5 Published: Jun 19 2000 (Read by 959 users)

Security For Damgaard Axapta Setting up the security system in a system as complex as Axapta is bound to take several weeks and several test runs before you get it right. Or so you might think! The truth is that with some basic understanding of the concepts and some rules of thumb, you can quickly get very close to the desired result. Only relevant for Axapta 2.5 - not version 3.0

Turning off unwanted features First turn off all unwanted feature keys for the entire system. Then you do not have to set up the feature key for each user profile. This is easier said than done. You have to open the Feature key setup form. Read the description for each feature key and turn off the unwanted feature keys. If you have any doubt about the use of a feature key, then leave it turned on. You can always return later and turn it off. (Below is described a way to automatically figure out which feature keys are used. This method can only be applied after system use for a certain period of time)

Creating users Create all the users in the system in the User form under User Management. You create a new user by pressing ctrl-n. By default a new user has no password. If you want to specify a password for the user click the User Options button, which will bring you to the user's personal set-up. Here you can specify a password among other things. Remember to inform the user about the password, or she will not be able to log in. If you want the operating system (Microsoft Windows) to control the identification of a user (and thus get rid of the Axapta logon dialog), you must specify a network account name for the user. This network account name is how the user is recognized on the network - the name he uses to logon to Microsoft Windows. If you cannot get this to work, you are probably specifying a user Id as a command line switch when starting Axapta. Notice the Admin user. This user is automatically generated and cannot be deleted. The user will always have access to everything in the standard application, including the security system setup.

Creating user groups Create all the user groups you need in the system. You will need one user group per role in your company. This is done in the User group form under User Management. You create a new user group by pressing ctrl-n. When the user groups are created you have to assign users to the user groups. This is done on the next tab in the user group form. Notice that a user can be a member of several user group and thus gaining the accumulated rights. In other words, you can create a “Book keeper” and a “Controller” user group, assign Lisa and Jeff to one each and assign John to both. You do not have to create (and maintain) a “Book keeper/Controller” user group. Notice the Admin user group, it is automatically generated and will always contain the Admin user. Other users might be added to this user group and gain the same rights as the Admin user.

Creating companies Create all the legal entities, known as companies in Axapta. Open the form Companies under Company. Use ctrl-n to create a new company. Notice that two (or more) companies can share data, like customers, vendors or zip codes. This is extremely useful if several companies have the same customer base. Virtual companies are used to

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 4

control and maintain this functionality. Please refer to Developer's Guide for details. Notice the DAT company. It is automatically generated during installation. You can choose either to use this as a company or create a new. It is recommended to create a new company. If you have installed a demo version with demo data, you will have a company with the name DMO, which contains the demo data.

Creating domains If you are using domains, which will allow your users to have a set of rights in each company, you have to create the needed domains. A domain is just a group of companies. You create domains by pressing ctrl-n in the Domains form under Company. You must create a domain for each group of companies that users should have different access to. A company can be a member of several domains. Users will gain the accumulated access to the company. E.g. The company “Denmark” can be a member of both the domain “Scandinavia” and the domain “Europe”. In the company “Denmark” A user “John” will have rights to perform whatever, he is entitled to in “Scandinavia” and in “Europe”. Notice the Admin domain. It contains all companies in the system. If you create a new company, it will automatically be a member of the Admin domain. This domain is used for the Administrator user to gain access to all features in all companies.

Setting up the permissions Go to the Permissions menu under User management. Open the User group permission form. In here you can either see a list of user groups, or if you are using domains a list of user group per domain. Select the one you want to set up permission for. It could be the “Book keeper” or the “Book keeper” in “Scandinavia”. On tab page 2, Feature Key Permissions, you can specify the security level for each user group. This is done using the radio buttons to the right called: Access and Indirect Access. To the left you have a description of the feature key you have selected. To the right you have a tree showing the main menu. This tree will have bold-faced items, for each menu item in the main menu that the security profile has access to. This is extremely useful for fast figuring out how the resulting main menu will be. You can also select a menu item in the Main Menu Tree. This will allow you to set the security for the feature key on the menu item. All menu items have a Needed Access Level, which is the access level required by the user to have access to the menu item. The Needed Access Level is also displayed. If the access level exceeds the Needed Access Level, the menu item will be bolded, to indicate that it will be available in the main menu. The different levels of security means:
No Access. The user will not be able to view.
Read: The user will be able to see the contents, but not to modify it.
Edit: The user will be able to modify the contents.
Add: The user will be able to create new records. (E.g. customers)
Full Access: The user will be able to delete existing records. (E.g. customers)

The indirect access is indeed very important. The use and purpose is easiest described using an example. Martin is an Order Taker. This means that he should have access to the Order module. (Both direct and indirect). He is not working with the Inventory, so he should have no access to the Inventory module. This is of course a paradox, because Martin will not be able to take orders, if he doesn’t know what is on stock. To solve this Martin’s indirect access to the Inventory module is set to full access. This will give him look-up in the inventory table from the sales order form - but he will not have access to the inventory module from the main menu. If the indirect access only was set to view, Martin would be able to see which inventory items was on existing orders. He would not be able to modify them (or add new). A rule of thumb: You can not be too generous with indirect access. As a starting point, you should give full indirect access to all modules to all security profiles. (This may come as default in a future version). This way everybody will be able to perform their tasks - you can always limit it later.

Table restrictions As a supplement to the flexible feature keys a more static functionality has been implemented. This will allow you to limit access to tables for all users - this is a way of overruling the feature key set up, and should only be used for tables with confidential information.

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 3 von 4

There is a wizard to help you set the restrictions. It is started from Permissions under User Management. It is called Table- and Field permissions. With this wizard you specify which tables and fields should be restricted and what the default access should be for all users to this specific table or field. In the User Group Permissions form on tab page 3, Table Restrictions, you can set the access for each security profile. Use this functionality with caution, as you set the ordinary security rules out of play.

Viewing a users permissions It is possible without logging out to see the resulting permissions for each user. Open the form User Permissions under Permissions in User Management. Here you can see each users feature key set up, their main menu with all the accessible menu items bolded, and the table permissions. You can not edit a user's permissions, as the lowest entity you can modify is the security profile.

Security on form control level As another supplement to feature keys you can set up security on a very detailed level in forms. Actually you can restrict the user further by hiding or not allowing the user to modify each field/control in a form. All you have to do is open the desired form, right click on the unwanted fields and choose hide. When all unwanted fields are hidden, right click and choose setup. Now you can restrict the rest of the fields by not allowing the contents to be editable. When the form has the design you want, you can apply it to a security profile. Click the button and select which user group and domain (if needed). All users using this security profile will now have the design you just created. To get your own original design back, click Reset. To get an overview of all designs created for security profiles select User Groups’ Forms Setup under User Management/Permissions. Here you can also delete unwanted designs.

Passwords options It is possible to enable a set of password options. Just turn on the feature key Extended Password Validation. It is located under Admin/User log. Now you (as an Administrator) have access to Password Parameters under User Management. You can set the minimum length and force the contents to contain numbers and letters. The users can be forced to change password regularly by setting the Valid Days parameter. Notice that if you limit the Valid days parameter (setting a lower number than before), some users will not be able to log in, as they are caught in the suddenly invalid period. You can solve this problem by clicking the Reset password log button, which will make all passwords valid from today.

Automatic feature key setup Setting up feature keys can be a very time consuming process. It is recommended that you do it roughly when the system is installed and wait with the fine-tuning, as it can be done automatically. When the system has been used for a couple of month, you can run the Database Optimizing Wizard. It is located under Feature keys/Periodic. This wizard will examine the system and find all empty tables. If a table is empty it is indicating that the feature is unused in the entire system. If all tables used by a feature are empty, the feature can be turned off for the entire system. A table is empty, if it does not contain any records in all companies, except DMO. DMO is excluded as it is used for demo data, and will contain data in most tables, thus would prevent this functionality to work as intended. This wizard will find all the feature keys, that can safely be turned off and present them in a list. You can select to keep certain features, if you know they are about to be used. The wizard also generates a list of all the empty tables, and again you can select to keep a table (and the feature behind it). When you finish the wizard all the appropriate feature keys will be turned off for the entire system resulting in a faster database and a simpler user interface for each user. This functionality is not as great as it sounds. It has a safety limit: Only feature keys, which govern tables, are analyzed. This means that a feature key only used on the user interface can not be disabled. Since feature keys are structured in trees, it also means that a feature key not can be disabled, if one of its children is enabled. So if a “table”-feature key is father to a “user interface”feature key, it will not be disabled. In other words: Only feature keys that safely can be turned off will be turned off - and there might still be room for fine-tuning after this wizard has been used.

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 4 von 4

Notice that every third month this wizard will automatically start up, when an Administrator logs on. This can be disabled in the last step of the wizard.

The final words To wholly meet the needs of every customer, the security system is indeed very complex. It has been continously improved since the first version of Axapta, to make it as easy to use and understand as possible. This is an ongoing process, which will continue in the Load’n Go scope of version 3.0. The outlines have been given in this brief walkthrough. Developer's Guide contains more in depth details about the security system.

Article posted under: Implementation, MorphX.

Discussion based on this article: Help

View: All Disc:#47 Subj: (Multiple) Art: Security For Damgaard Axapta

47.1 Expanding security possibilities (carl bergman, 17 Aug 2000 11:23:17 CET) 47.2 User setup of forms differs from setup being applied to a user group (Michael Fruergaard [MBS]

, 17 Aug 2000 13:38:45 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 2

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: Jun 22 2000 (Read by 625 users)

Posting control Posting control in Axapta, set up on the "Chart of Accounts". The posting control is handled in multiple layers in Axapta, where the basic layer is defined in the Chart of acounts. Other layers are the posting profiles, journal control etc. In the Chart of accounts it is possible to specify what postings are allowed on the account. The restrictions are: 1. Currency 2. User 3. Posting type 4. Dimension 5. Debit/Credit 6. Blocked in Journal/Closed 7. Transaction accounts In restrictions 1-4, Axapta has an advanced way to specify and check the values. For each type of restriction; Currency, User etc. it can be specified if the information is: A. Optional = No check is made on this information, except that it must be a valid value. With regards to Currency this is not relevant, since currency is always at least mandatory. B. To be filled in (Mandatory) = The information must be filled in. This is relevant in dimensions. Users are allways filled in by the system. C. Table = The only valid value is the one specified in the Chart of accounts, in the specific field; Currency, User etc.. D. List = The only valid values are specified in a special list. The list is maintained through the button Validate list. The information Currency and Dimension is typically entered in the various functions, like journals, sales etc. In the journals the currency and dimension on the Chart of accounts is copied into the journal, when the account is selected in the account number field. This is just a help and the information can be changed. If you specify a list of currencies, and then specify one currency in the Chart of accounts, the specified currency is copied into the journals, and the list is used for posting control. Please note that the currency and dimension are not copied for the offset account in the journal. The User information is automatically generated by the system, and the posting control can be restricted to use selected acounts for selected users. The posting type is a type, that specifies the kind of posting. The posting type is automatically generated by the different posting functions in Axapta. The purpose of the posting type is to specify that only postings from a specific module (or modules) are allowed on an account. The advantage is to reduce irrelevant postings on accounts. Another advantage is that the posting type is used to limit the number of legal accounts to select from the look-up form on account numbers. To be able to specify the posting types, you need to know what posting types the different functions uses. Posting Taxes allways have the posting type "Tax." Journals have the posting type "LedgerJournal", except if it is an intercompany posting, then the posting type is "Intercompany". In restrictions 5-7, the check routine is simple. If a debit/credit restriction is defined, you cannot post an amount that does not follow the rule. If you specify that only credit amounts are allowed, you can only post credit amounts. If you need to post a

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 2

positive amount, then this must be posted as a correction to a credit amount ( = -amount in the credit column in the journal) The account can be generally blocked from beeing posted on in the journals. This allows only other modules to post on the accounts. The account can also be closed from posting from all modules. Only postings on transaction accounts are possible. Header and sum accounts are not transaction accounts, and this is part of the posting control as well.

Article posted under: Financial Series, Country Issues.

Discussion based on this article: Help

View: All Disc:#8282 Subj: (Multiple) Art: Posting control

8282.1 (No header specified) (iderman, 17 Oct 2003 16:43:14 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: Jun 26 2000 (Read by 975 users)

Quick & Dirty COM Connector status check The enclosed VBScript program will easily determine if the COM connector has been properly installed on the user's system. Connectly installing the COM connector is a prerequisite for using any of the Web features in Axapta. Sometimes you will find it useful to determine whether or not the COM connector is properly registered with the system or not. The enclosed VBscript snippet will allow you to do that. Error recovery is not gracious. The script will simply fail if the com connector is not installed. If the com connector is installed, a message box containing the version number and build time and date will appear. Use the Axapta Configuration utility or the regsvr32 tool to register the COM connector object with the operating system. The script is attached.

Download files: comversion.vbs [0K]

Article posted under: Axapta COM Connector.

Discussion based on this article: Help

View: All Disc:#3900 Subj: (Multiple) Art: Quick & Dirty COM Connector status check

3900.1 Adding a file in Document Handling problem (JamesWeir, 06 May 2002 16:51:33 CET) 3900.2 Possible ? (holger, 10 May 2002 12:16:17 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back | Start a discussion based on this article The information in this article applies to: Damgaard Axapta v2.1 Published: Aug 29 2000 (Read by 369 users)

Need to know the exact version of your database backend? ODBC driver version? Some times developers need to log or know the version numbers on various database entities, including the database and the ODBC layer. This article presents a small piece of X++ to retrieve such information.

All the version numbers - and a lot of other interesting information - can be retrieved from the ODBC layer. Casual users may open the "Status"-form on the Administrator|Database menu to see or print a list of all accessible ODBC informations. Developers may examine the underlying X++ code in the form. For those just interested in version numbers, the code-snippet below may be useful: static void databaseVersionNumbers() { #define.SQL_DBMS_NAME(17) #define.SQL_DBMS_VER(18) #define.SQL_DATABASE_NAME(16) #define.SQL_DRIVER_ODBC_VER(77) #define.SQL_DRIVER_VER(7) #define.SQL_ODBC_VER(10) Connection mainConnection = new Connection(); ; setPrefix("Information about database and ODBC version numbers."); info(strFmt("Name of the database product: '%1", mainConnection.odbcGetInfoStr(#SQL_DBMS_NAME))); info(strFmt("Name of the database: '%1", mainConnection.odbcGetInfoStr(#SQL_DATABASE_NAME))); info(strFmt("Database version number: '%1", mainConnection.odbcGetInfoStr(#SQL_DBMS_VER))); info(strFmt("ODBC driver version: '%1", mainConnection.odbcGetInfoStr(#SQL_DRIVER_VER))); info(strFmt("ODBC Driver Manager version: '%1", mainConnection.odbcGetInfoStr(#SQL_DRIVER_ODBC_VER))); info(strFmt("ODBC API version: '%1", mainConnection.odbcGetInfoStr(#SQL_ODBC_VER))); }

This sample applies to all Axapta versions. The above X++ code is attached for easy download.

Download files: databaseVersionNumbers.xpo [1K]

Article posted under: Implementation, Databases (Ax), Test Subject. © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back The information in this article applies to: (None) Published: Jul 11 2000 (Read by 202 users)

Appropriations and Liquidity Read about using appropriations in Axapta. Appropriations are the estimated future ledger transactions, based on information already registered in the system. Liquidity is a subset of appropriations, specifying the future demands on liquidity per currency per date. Liquidity uses the calculated appropriation, but selects only transaction on liquidity accounts. Read more about Appropriations and Liquidity by downloading the file.

Download files: Appropriations.doc [120K]

Article posted under: Financial Series.

Discussion based on this article: Help

View: All Disc:#3957 Subj: (Multiple) Art: Appropriations and Liquidity

3957.1 Assumptions in appropriations? (i91juhal, 14 May 2002 23:17:49 CET) 3957.2 First Conclusion (dmit2604, 06 Dec 2002 14:44:25 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: (None) Published: Jul 11 2000 (Read by 736 users)

Axapta Object Server and Network Address Translation might cause trouble Using AOS with Network Address Translation (NAT), Masquarading or other ip/port remapping will not always work. When setting up the AOS on a network using translative firewall technology (NAT device or the like), will provide problems for the AOS environment in the following cases. 1.

Server placed behind NAT will advertise it's existence to clients using it's real network address and not the one know to external sites. This makes it impossible to connect to the AOS. This can currently only be resolved by assigning the machine running AOS a real, official IP address by which is is also known to the and accessible for the client. Axapta client version 2.11 will support new connection schemes that also might help making this setup work.

2.

Clients accessing an AOS from behind NAT device will in many cases fail due to trouble for the NAT device when routing AOS replies to connect requests back to the client. This is due to the fact that this communication is based on udp packages not passed correctly by the firewall/NAT device. Some devices will make it work but many will not. This issue is targeted by a special connect mode of the Axapta 2.11 client circumventing the use of udp packages. This allows clients to connect through connections not even supporting routing of udp packages. The client will by it's configuration have enough information to create the needed tcp socket directly to the AOS of choice.

The two scenarios above will result in error message like "No servers found" when starting or after choosing the server messages like "Cannot connect to server" could occur.

Article posted under: Technology (Ax), Implementation, Axapta Object Server.

Discussion based on this article: Help

View: All Disc:#478 Subj: (Multiple) Art: Axapta Object Server and Network Address Translation might cause trouble

478.1 Axapta 2.11 client configuration to circumvent NAT problem (liberator, 03 Jan 2001 18:58:29 CET)

478.2 Axapta 2.5: Use the -aos=: command line option (jsh, 08 Jan 2001 16:33:32 CET) 478.3 -aos=: should be -aos=host:port (jsh, 08 Jan 2001 16:35:58 CET) 478.4 Thanks. (liberator, 13 Feb 2001 14:37:28 CET) 478.5 better solution (kkrabbes, 09 Mar 2001 07:43:37 CET) 478.6 ...will not circumvent the NAT problem (jsh, 13 Mar 2001 16:21:09 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 14

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back | Start a discussion based on this article The information in this article applies to: (None) Published: Jul 12 2000 (Read by 1 users)

Users Guide for US solution for EDI integration

This article describes the basics concerning usage of the EDI interface for use with Axapta on the North American mark

Technical Information

US local solution for EDI - User Guide Ref. No: TI0001-01 Introduction

This chapter describes some of the considerations you need to do when implementing the EDI module. Before starting implementation it is very important to realize that the EDI module will most likely have to be modified for the specific c Even though EDI (and ANSI X12) is a standard, it is normal for customers to have specific requirements. In order to m file layouts to meet the customers needs you will have to do some programming. Please set aside the appropriate time implementation and programming. A typical situation where a customer needs to send and receive invoices and orders typically require a week of implementation. If the customer requires advance ship notice (and does not use the WMS m some additional modifications will probably have to be done to the Axapta standard, as it does not have the concept of lading that is closely related to advance ship notice. Implementation time for this will have to be added to the total implementation time needed. All this is assuming a person with good knowledge of the translator that will be used is p during implementation The Axapta EDI module is based on transferring information from and to external flat ASCII files.

External File Format

The format of inbound external files can either be comma separated or fixed positional files depending on setting in the parameters. The file layout can only be changed through changes to the application code. The format of outbound files can either be comma separated or fixed positional depending on setting in parameters. The first three fields in the external files must always be, 1.

Identification string (e.g. “HEADER”)

2.

Document identification (e.g. “850”)

3.

EDI Partner identification (e.g. “Part1”)

After the fixed part a number of fields may occur depending of the programming for each document type. A file may co different documents.

Inbound files Example of inbound file (comma separated layout),

quote;HEADERquote;,quote;850quote;,quote;Part1quote;,”00”,”SA”,quote;100009quote;,””,””,””,quote;03/10/99quot quote;LINEquote;,quote;850quote;,quote;Part1quote;,quote;ESB005quote;,quote;1quote;,quote;20quote;,quote;quote;,quote;14.50quote;,quote;quote;,quote;quote; quote;LINEquote;,quote;850quote;,quote;Part1quote;,quote;ESB005quote;,quote;1quote;,quote;10quote;,quote;quote;,quote;14.50quote;,quote;quote;,quote;quote; quote;TOTALquote;,quote;850quote;,quote;Part1quote;,quote;290quote; quote;TOTALquote;,quote;850quote;,quote;Part1quote;,quote;145quote; quote;HEADERquote;,quote;850quote;,quote;Part1quote;,”00”,”SA”,quote;100009quote;,””,””,””,quote;03/10/99quot quote;LINEquote;,quote;850quote;,quote;Part1quote;,quote;ESB005quote;,quote;1quote;,quote;20quote;,quote;quote;,quote;14.50quote;,quote;quote;,quote;quote;

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 14

quote;LINEquote;,quote;850quote;,quote;Part1quote;,quote;ESB005quote;,quote;1quote;,quote;10quote;,quote;quote;,quote;14.50quote;,quote;quote;,quote;quote; quote;TOTALquote;,quote;850quote;,quote;Part1quote;,quote;290quote; quote;TOTALquote;,quote;850quote;,quote;Part1quote;,quote;145quote; Memo lines

For inbound documents it is possible to import memo lines and save these on the documents in the pending documents However the memo lines are always related to the header, line or total record read immediately before the memo lines creation of e.g. Sales Orders, Memo lines will be saved on the specific sales order as notes in the document handling sy Example, quote;HEADERquote;,quote;850quote;,quote;Part1quote;,quote;4000quote;,quote;03/10/99quote; quote;MEMOquote;,”850”,quote;Part1quote;,quote;This is a memo text that will be saved on the header recordquote; quote;LINEquote;,quote;850quote;,quote;Part1quote;,quote;2730010quote;,quote;300quote;,quote;3.4quote; quote;MEMOquote;,”850”,quote;Part1quote;,quote; This is a memo text that will be saved on the line recordquote; quote;TOTALquote;,quote;850quote;,quote;Part1quote;,quote;12345.34quote; quote;TOTALquote;,quote;850quote;,quote;Part1quote;,quote;5678,90quote; Ship to lines For inbound Sales Order documents it is possible to have ship to location information for each sales order line.

AXAPTA will import the ship to location for each document line. And store that information related to the line. When sa are created in AXAPTA each ship to location for an item will trigger creation of a new sales order. This is because AXAP can have one ship to location (or delivery address) per sales order.

The format of the SHIPTO line information MUST contain the location as the fourth field and the quantity as the fifth fie “SHIP”,quote;850quote;,quote;Part1quote;,”LOCA”,”14” “SHIP”,quote;850quote;,quote;Part1quote;,”LOCB”,”34” Example,

quote;HEADERquote;,quote;850quote;,quote;Part1quote;,”00”,”SA”,quote;100009quote;,””,””,””,quote;03/10/99quot quote;LINEquote;,quote;850quote;,quote;Part1quote;,quote;ESB005quote;,quote;1quote;,quote;48quote;,quote;quote;,quote;3.4quote;,quote;quote;,quote;quote; “SHIP”,quote;850quote;,quote;Part1quote;,”LOCA”,”14” “SHIP”,quote;850quote;,quote;Part1quote;,”LOCB”,”34” quote;TOTALquote;,quote;850quote;,quote;Part1quote;,quote;5678,90”

Which in AXAPTA eventually will be created as two sales orders, one to location A with a quantity of 14 and one to loca with a quantity of 34. Please note that ship to location codes must exist in the customer’s alternative addresses!

Outbound files

Outbound files may either be comma separated (as for inbound files) or fixed formatted according to the coding. This i in the EDI parameters. For fixed file formatting the external file is formatted according to the file layouts specified in th following. When using comma separated formatting, the sequence of the fields in a file is the same as in the fixed form

External file location Different strategies for importing and exporting files can be applied.

Inbound files 1.

Inbound files may be read manually by entering the file name.

2.

Inbound files may be read automatically by using the inbound directory entered in the EDI parameters. This assum the “Prompt for filename” is NOT checked. ALL FILES in the inbound directory will be attempted imported. After imp individual inbound files are saved as backup files and placed in the backup directory (entered in the EDI parameter then deleted from the inbound directory.

Outbound files

For outbound files the file name and directory is entered when initiating the export. If the export is set recurring mode it is therefore important that the outbound file is always read and deleted (manually or by the Sterling translator) before the export is activated again. This is because the export ALWAYS OVERWRITES any existing files wit same name.

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 3 von 14

If the export is initiated manually a new file name can of course be entered each time. After an export file has been created a backup of the file is saved in the backup directory.

EDI parameters Identification strings

The identification fields relate to the content of the external files with the EDI documents. In the fields you enter the s that identify the header, line, total (possibly the total records of each document), memo, ship to and system. ALL lines file MUST always contain the identification strings

Date format This is the date format that will be used when analyzing inbound dates.

Prompt for file name

If marked the user is expected to enter the file name each time an export is initiated. If the export is set to run in recu batch mode, the export will be written to the same file each time.

Path This is the location of the inbound files.

Backup path

This is where inbound and outbound files are saved as backups. Backup file names will be the original names plus date of generation.

Delete file

This setting determines whether external input files should be deleted when they have been imported. This should be u together with the prompt for file name option.

Field separator

In this field you may specify which character in the external file that separates each field in a single line, e.g. a comma character “,” or a tilde ”~”.

Field delimiter

In this field you may specify the character that delimits each field in a single line. It could be blank or a double quote c “””.

Print invoice

This field determines whether a sales order invoice should be printed if it also has been shipped via EDI. Invoice copies printed whether or not this switch is set.

DUNS This number is used for sending some documents, e.g. the advanced ship notice.

Fixed file This allows to choose either fixed or comma separated output file formats.

Use packing slip

This is used if the company does not use the WSM module, which normally is used for generating Advance Ship Notice. case the packing slip can be used as a basis for the ASN. However certain things must be considered regarding the use packing slip as they do not in the standard version of AXAPTA contain quite the same information as in Advance Ship N Programming may be required.

Set-up of partners

Each partner used in the EDI module must be set up. A partner is a vendor and/or a customer. For each partner, inform such as address, contact info can be entered. There must always be entered either a vendor account and/or a custome

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 4 von 14

For each partner (which is also a customer) it is also possible to enter related customer accounts. Consider for instance situation where invoices always are billed to a corporate account (which is the EDI partner) but the sales is done to rel accounts (for instance separate stores). In this case it is possible to relate all of the separate stores and their identifica the single partner.

Document types

For each partner you also decide the document types you are exchanging with the partner (sales orders, invoices etc.)

Item conversion For each partner a conversion table between internal and external item numbers may be maintained. When inbound files are received the following is applied, The value in the item number field in the inbound file is searched in the item table 1.

If not found the value in the external item number field in the inbound file is searched in the item table.

2.

If not found the value in the item number field in the inbound file is perceived as an external item number and conv an internal item number via the conversion table. Then the new value is searched in the item

3.

If still not found the value in the external item number field in the inbound file is perceived as an external item num converted to an internal item number via the conversion table. Then the new value is searched in the item table

Initializing partners

When the partner has been setup in the EDI module, the customer or vendor must be enabled for EDI. All relevant docu updated after this will be enabled for transfer via EDI. The initializing of the customer and/or vendor is done in the cus and/or vendor table by setting the “EDI enabled” to “Yes”.

Setup of document types

Relevant document types must be created in the document type setup. The following document types are currently sup 1.

Inbound sales orders

2.

Inbound purchase invoices

3.

Outbound purchase orders

4.

Outbound sales invoices

5.

Outbound advance ship notices (packing slips)

Specific setup such as price and quantity handling may be setup. For each document type the following must furthermore be set up,

EDI standard number

It is important to enter the EDI standard number for each document type, as it is this number that is used to identify th different documents in the inbound files, as well as applying the number in the output files.

Header, Line and Total setup

This is where you set up the layout of the records with header, line or total information for each document type. For ea document type the available fields in Axapta is presented in the left list box. The field setup of the external file is repre the right list box. By clicking the left/right button (or double-clicking different fields) these are transferred back and fo between the left and right list box.

Test

If this flag is marked a test flag will be set in the system header in the outbound files. This can be used in the translato identify the document as a test document mode. Everything in AXAPTA will be updated as normal, i.e. a document expo test mode will NOT be exported later even though the test flag was set.

Partner

For each document type it is possible to setup which partners have the document activated and also different settings price and quantity handling can be chosen. If there is a specific setting you wish to activate for a partner you can do th otherwise the setting must be “default”, and the setting general for the document type will then be used.

Number sequences

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 5 von 14

One number sequence for EDI must be setup for a unique document number. This can be done using the standard num sequence wizard. The number sequence must be setup with reference to EDI document number. The document number should be marked as continuous with cleanup

User guide General

The AXAPTA EDI module is designed to be able to read inbound files containing information about EDI type documents sales orders, purchase invoices etc. Likewise it is able to generate outbound files containing information about EDI typ documents such as purchase orders, sales invoices etc.

The EDI module thus always reads or writes information through external flat ASCII files (comma separated). It is nec have an EDI translator, such as Sterling, to eventually send/receive true EDI documents to EDI partners. This guide expects the EDI module to be set up correctly. Please read abound setup in the “EDI implementation guide

EDI documents, whether inbound or outbound are always stored in an EDI document pending table before further proc This table thus acts as a temporary storage, where status can be viewed as well as log and data information. When a d has bee fully exported or imported/updated it is marked as done. When documents are all done, they may be transferred to an archive. Records in the EDI Documents pending table are never deleted. Processing documents may either be done from EDI/Periodic or directly from the ready EDI documents form.

Processing inbound files Process inbound documents the following way, 1.

Start import of external flat file. Documents will be inserted into the pending documents table with status documents not able to be processed further (perhaps caused to missing setup information) will be marked as excep may be examined in the exception documents overview form.

2.

Either you must start updating of sales orders or updating of purchase invoices.

Processing outbound files Process outbound invoices the following way, 1.

Start one of the following, Create sales order invoices Create purchase orders Create advance ship notices When starting one of these, all relevant and EDI enabled documents for customer/vendor also enabled for EDI will processed and updated in the EDI pending documents table ready for export.

2.

Start export of the EDI documents to an external file. You will be prompted for a file name and the export will begin the export has been done, the export file is saved and copied to a backup directory (entered in the EDI parameter s

Handling exceptions

Whenever a situation occurs that a document for any reason cannot be processed it will be marked as an exception. Th documents may be viewed in the exception documents form. Exception documents may be marked as ready for anothe further processing, or - if it is not possible to complete – they may be archived directly.

Archiving Documents that are done may be archived by initiating the archive process found under EDI/Periodic.

Canceling

Outbound documents that have been created and which are ready for export may be cancelled. Also inbound document imported from a file may be cancelled before further processing.

When outbound documents are created and inbound documents are imported all documents in that specific batch can b cancelled. This is done under EDI/Periodic/Canceling inbound/outbound by entering the appropriate batch number. Th can be seen on any of the documents in the batch.

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 6 von 14

Re-exporting lost files

If an external export file for some reason have been lost it is possible to make a re-export by entering the batch numbe documents in the batch. This will create the export file again.

Batch mode

All the above-mentioned described processes may be initiated in batch, and thus also be set to run in a recurring mode every night.

Document file layouts The following is samples of setup for file layouts for the different document types. Modifying the application logic can change the file formats. Information is exported in the following sequence, System header information and fields 1-3 is information inserted during export to the external file.

Outbound files may either be exported in a comma-separated format or a fixed file format. This is determined with a fie EDI parameter setup.

System header Field

Variable name

Value

Type

Startpos

Length

1

Record type

“S”

AN

1

10

2

Partner ID

From the EDI partner table

AN

11

10

3

Standard

“X”

AN

21

1

4

Version

“00410”

AN

22

6

5

Transaction

EDI document number from document type setup, e.g. “810”

AN

28

10

6

Test/Production flag

“T” or “P”. Setup on document type or partner specific setup

AN

38

1

Outbound Sales Order Invoice – 810 Header Field

Variable name

Value

Type

Startpos

Length

1

Record type

“H”

AN

1

10

2

Document type

“810”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Invoice number

AN

31

20

5

Invoice date

DT

51

10

6

PO number (from original PO - 850)

AN

61

22

7

PO date

From Sales order created date

DT

83

10

8

Terms basis date code

‘3’

AN

93

1

9

Terms discount percent

From Cash disc. Table

R2

94

5

10

Terms discount days due

From Cash disc. Table

R0

99

10

11

Terms net days

From Cash disc. Table

R0

109

10

12

Our account number

From customer table, our account AN number

119

20

13

Customer name

AN

139

30

14

Address 1

169

30

15

Address 2

199

30

16

Zip code

229

10

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 7 von 14

17

City

239

30

18

State

269

30

19

Country

299

30

20

Ship-to location

From either address or customer table

AN

329

20

21

Department

From customer table

AN

349

10

22

Remit to name

From Company information name AN

359

30

23

Remit to DUNS

From EDI parameters

AN

389

10

24

Date shipped

Creation date of the first packing DT slip update for that Order. AXAPTA allows several Packing slip updates of the same order as well as invoices. If date shipped on invoice is to be valid only one packing slip and one invoice should be updated. If sales order has not been packing slip updated this date is set to the invoice date.

399

10

Detail Field

Variable name

Value

Type

Startpos

Length

1

Record type

“L”

AN

1

10

2

Document type

“810”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Line number

From customer invoice transaction

N0

31

10

5

Quantity invoiced

From customer invoice transaction

N0

41

10

6

Unit of measure

From customer invoice transaction

AN

51

10

7

Unit price

From customer invoice transaction

R2

61

10

8

Buyers item number

From customer invoice transaction

AN

71

20

9

Vendor item number

From customer invoice transaction

AN

91

20

10

UPC item number

From Barcode field on Inventory table

AN

111

48

11

Item description

From customer invoice transaction

AN

159

20

Total Variable name

Value

1

Record type

2

Field

Type

Startpos

Length

“F”

AN

1

10

Document type

“810”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Invoice ID

From the invoice journal

AN

31

20

5

Amount of invoice

From the invoice journal

R2

51

18

6

Amount terms based on

R2

69

18

R2

87

AN

105

10

7

Total discount amount

Total calculated invoice amount

18

8

Transportation method

9

Standard Carrier Alpha Code

From the Delivery mode table

AN

115

10

10

Carriers reference number

From invoice journal Delivery Tracking field

AN

125

15

11

Bill of lading number

The Packing slip Id for the first packing slip for that sales order. AXAPTA allows several packing

AN

140

10

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 8 von 14

slips per sales order. If this is to be the correct number only one packing slip and one invoice should be updated for the sales order 12

Total misc. charges

Sum of all freight, charges etc. taken from invoice journal

R2

150

18

13

Number of units shipped

Sum of all quantities in invoice journal lines. All invoice lines should be of same unit.

R0

168

10

14

Unit of basis for measurement code

Unit taken from first invoice line.

AN

178

10

15

Weight

Sum of weight all lines

R2

188

10

16

Unit of basis for measurement code

Hard coded to “LB” (pounds)

AN

198

2

17

Number of line items

Count of invoice lines

R0

200

10

Outbound Advance Ship Notice, packing slip – 856

Advance Ship Notices may either be created from Bill of ladings and Shipments updated in the Warehouse managemen or from packing slips update through sales orders. This is determined in the EDI parameters. If the warehouse manage not used, no Bill of lading information exists, and the individual customers will therefore have to consider modifying th order module to include bill of lading functionality.

This below format describes information taken from the packing slips, information from packing slips may be substitut information from the bill of lading number if the WMS is used as a basis (see next file layout description Header Field

Variable name

Value

Type

Startpos

Length

1

Record type

“H”

AN

1

10

2

Document type

“856”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Vendor shipment number Packing slip id

AN

31

20

5

SCAC code

From delivery mode table

AN

51

10

6

Bill of lading number

Currently set to the packing slip Id

AN

61

20

7

Shipment date

Created date from packing slip journal

DT

81

10

8

Estimated delivery date

From packing slip journal

DT

91

10

9

Ship to location code

From packing slip journal

AN

101

20

Detail information, Order level Field

Variable name

Value

Type

Startpos

Length

1

Record type

“L”

AN

1

10

2

Document type

“856”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

5

Level code

‘O’

AN

31

1

6

Purchase order number

Buyers PO number

AN

32

22

7

Purchase order date

DT

54

10

8

Total number of Ship units in PO

R0

64

10

9

Buyers name

AN

74

30

10

Buyers location

AN

104

20

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 9 von 14

Detail information, Packing level This is not implemented in standard AXAPTA EDI if you are NOT using the WMS module! Field

Variable name

Value

Type

Startpos

Length

1

Record type

“L”

AN

1

10

2

Document type

“856”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

5

Level code

“P” = Pack (carton) level

AN

31

1

6

UCC code

AN

32

10

7

# Units for carton

AN

42

10

8

Unit of measurement

AN

52

10

Detail information, Item level Field

Variable name

Value

Type

Startpos

Length

1

Record type

“L”

AN

1

10

2

Document type

“856”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

5

Level code

‘I’

AN

31

1

6

Item Id

From WMS order transaction

AN

32

20

7

Buyers item Id

From sales line – external item id

AN

52

20

8

UPC number

From sales line – barcode field

AN

72

48

9

Quantity

From WMS order transaction

R0

120

10

10

Unit of measurement From sales line

AN

130

10

Total Field

Variable name

Value

Type

Startpos

Length

1

Record type

“T”

AN

1

10

2

Document type

“856”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Total number of line items

R0

31

10

Outbound Advance Ship Notice, Bill of Lading – 856

Advance Ship Notices may either be created from bill of ladings and shipments updated in the Warehouse management or from packing slips update through sales orders. This is determined in the EDI parameters. If the warehouse manage not used, no Bill of lading information exists, and the individual customers will therefore have to consider modifying th order module to include bill of lading functionality. This below format describes information taken from the bill of ladings. Header Field

Variable name

Value

Type

Startpos

Length

1

Record type

“H”

AN

1

10

2

Document type

“856”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Vendor shipment number Shipment Id

AN

31

20

5

SCAC code

AN

51

10

6

Bill of lading number

AN

61

20

7

Shipment date

DT

81

10

From delivery mode table

Creation date of the BOL

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 10 von 14

8

Estimated delivery date

Delivery date for the WMS order transaction

DT

91

10

9

Ship to location code

Sales order ship to location

AN

101

20

Detail information, Order level Field

Variable name

Value

Type

Startpos

Length

1

Record type

“L”

AN

1

10

2

Document type

“856”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

5

Level code

‘O’

AN

31

1

6

Purchase order number

Buyers PO number

AN

32

22

7

Purchase order date

DT

54

10

8

Total number of Ship units in PO

R0

64

10

9

Buyers name

AN

74

30

10

Buyers location

AN

104

20

Detail information, Packing level This is not implemented in standard AXAPTA EDI if you are NOT using the WMS module! Field

Variable name

Value

Type

Startpos

Length

1

Record type

“L”

AN

1

10

2

Document type

“856”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

5

Level code

“P” = Pack (carton) level

AN

31

1

6

UCC code

AN

32

10

7

# Units for carton

AN

42

10

8

Unit of measurement

AN

52

10

Detail information, Item level Field

Variable name

Value

Type

Startpos

Length

1

Record type

“L”

AN

1

10

2

Document type

“856”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

5

Level code

‘I’

AN

31

1

6

Item Id

From packing slip transaction

AN

32

20

7

Buyers item Id

From packing slip transaction – external item id

AN

52

20

8

UPC number

From packing slip transaction – barcode field

AN

72

48

9

Quantity

From packing slip transaction

R0

120

10

10

Unit of measurement From packing slip transaction

AN

130

10

Total Field

Variable name

Value

Type

Startpos

Length

1

Record type

“T”

AN

1

10

2

Document type

“856”

AN

11

10

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 11 von 14

3

Partner ID

From the EDI partner table

4

Total number of line items

AN

21

10

R0

31

10

Outbound Purchase Order - 850 Header Field

Variable name

Value

Type

Startpos

Length

1

Record type

“H”

AN

1

10

2

Document type

“850”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Purchase order number

AN

31

10

5

PO date

DT

41

10

6

Requested ship date

DT

51

10

Delivery date

Detail Field

Variable name

Value

Type

Startpos

Length

1

Record type

“L”

AN

1

10

2

Document type

“850”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Line number

R0

31

10

5

Quantity ordered

R0

41

10

6

Unit of measure code

AN

51

10

7

Unit price

R2

61

10

8

Item Id

AN

71

20

9

Vendors item number

AN

91

20

10

UPC item number

AN

111

48

Barcode

Total Field

Variable name

Value

Type

Startpos

Length

1

Record type

“T”

AN

1

10

2

Document type

“850”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Total number of line items

R0

31

10

Inbound Sales Order – 850 Header Field

Variable name

Value

Type

Startpos

Length

1

Record type

“H”

AN

1

10

2

Document type

“850”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Transaction set code

00 = original

AN

31

2

AN

33

2

01 = cancelled 05 = revised 5

Purchase order type

SA = standalone

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 12 von 14

NS = New store (customer) 6

Customer PO number

AN

35

22

7

PO date

DT

57

8

8

Requested ship date

DT

65

8

9

Cancel after date

10

Delivery date

DT

73

8

DT

81

8

11

Ship to location

AN

89

20

12

Bill to location

AN

109

20

13

Department

AN

129

10

NOT USED

Must arrive date

Detail Field

Variable name

Value

Type

Startpos

Length

1

Record type

“L”

AN

1

10

2

Document type

“850”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Item identification number

AN

31

20

5

Line number

R0

51

10

6

Quantity ordered

R2

61

10

7

Unit of measure code

AN

71

10

8

Unit price

R2

81

10

9

Eternal Item Id

AN

91

20

10

UPC item number

AN

111

48

From the barcode field

Ship to No user setup is available for setup of ship to location. The format is fixed. Field

Variable name

Value

Type

Startpos

Length

1

Record type

“S”

AN

1

10

2

Document type

“850”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Ship to location

Location code must match alt. Address on customer

AN

31

10

5

Quantity

R0

41

10

Total Field

Variable name

Value

Type

Startpos

Length

1

Record type

“T”

AN

1

10

2

Document type

“850”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Total number of line items

R0

31

10

Inbound Purchase Invoice - 810 Header Field

Variable name

Value

Type

Startpos

Length

1

Record type

“H”

AN

1

10

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 13 von 14

2

Document type

“810”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Purchase order number

AN

31

10

Detail Field

Variable name

Value

Type

Startpos

Length

1

Record type

“L”

AN

1

10

2

Document type

“810”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

PO number

AN

31

10

5

Line number

R0

41

10

6

Quantity ordered

R0

51

10

7

Unit of measure code

AN

61

10

8

Unit price

R2

71

10

9

Item Id

AN

81

20

10

Vendors item number

AN

101

20

Total Field

Variable name

Value

Type

Startpos

Length

1

Record type

“T”

AN

1

10

2

Document type

“810”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Total invoice amount

Must match the invoice amount calculated by AXAPTA

R2

31

10

Inbound Remittance Advice - 820 Header Field

Variable name

Value

Type

Startpos

Length

1

Record type

“H”

AN

1

10

2

Document type

“820”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Amount

Payment amount

R2

31

18

5

Credit/debit flag

‘C’ if credit

AN

49

1

6

Date

Payment date

DT

50

8

7

Reference

Payment reference

AN

58

30

Detail Field

Variable name

Value

Type

Startpos

Length

1

Record type

“L”

AN

1

10

2

Document type

“820”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Invoice number

AN

31

20

5

Amount

Payment amount

R2

51

18

6

Invoice date

Transaction date

DT

69

8

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 14 von 14

Total Field

Variable name

Value

Type

Startpos

Length

1

Record type

“T”

AN

1

10

2

Document type

“820”

AN

11

10

3

Partner ID

From the EDI partner table

AN

21

10

4

Total invoice amount

R2

31

10

Article posted under: Navision Axapta. © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back | Start a discussion based on this article The information in this article applies to: (None) Published: Jul 12 2000 (Read by 270 users)

Guide to the EDI local solution for the North American market This article describes the functionality in the EDI module developed for use in the North American market as well as how to implement it and install it including details of the technical implementation of the module.

Technical Information EDI for the North American market Ref. No: TI0001-01

Introduction A local solution for Damgaard Axapta in the US/North American market has been developed by Damgaard Inc. to support the need for exchanging EDI documents. The solutions is developed in Axapta and is based on integration with a EDI translator that actually sends and receives the EDI messages. Current liive installs uses the Sterling translator, but the EDI module may be used with other translators as well as it is based on flat ASCII files as the measn of exchaning information. The module handles the following type of documents,
Invoices
Purchase/Sales orders
Remittance advices (payments)
Advance ship notice (bill of lading)

Attachment The attached document describes variuos aspects of the EDI module in details.

Contact If you are interested in further information or obtaining the EDI module, please contact Damgaard Inc., Atlanta directly at +1 770 541 1099.

Download files: EDI - Documentation.Doc [347K]

Article posted under: USA. © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back | Start a discussion based on this article The information in this article applies to: (None) Published: Jul 12 2000 (Read by 126 users)

Guide to the AbraSuite payroll local solution integration module for the North A This article describes the usage and installation of the AbraSuite integration module developed by Damgaard Inc. as a local solution for the US/North American market.

Technical Information AbraSuite payroll integration Ref. No: TI0002-01

Introduction As standard Damgaard Axapta for the US/North American market does not have a payroll module, Damgaard Inc. has developed an integration with one of the most popular payroll packages available on the US market, AbraSuite from Best Software. The integration module solves the following needs,
Transferring financial information from the payroll package into Damgaard Axapta general ledger
Transferring pay check information from the payrol package into Damgaard Axapta bank management
Synchronizing employee information from the payroll package to Damgaard Axaptas employee information

Attachments Please find specifics on the functionality as well as installation of the integration module in the attached file.

Contact If you need further information or is interested in obtaining the local solution, please contact Damgaard Inc., Atlanta directly at +1 770 541 1099.

Download files: AbraSuite Integration.doc [57K]

Article posted under: USA. © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back The information in this article applies to: (None) Published: Jul 18 2000 (Read by 506 users)

How do I make a consolidation Read about how to consolidate companies step by step. The following is a description of the minimum required tasks to make a consolidation. It is described as the on-line consolidation. 1. Create a special consolidation company You may use a virtual company, for some basic data like currencies, Chart of accounts etc., but it is not necessary. In the consolidation company you need to specify the following: A: That it is a consolidation company. Mark the company as a consolidation company under General Ledger/Ledger/Setup/Parameters. B: Relevant currencies and exchange rates. Define the currencies you need under General Ledger/Ledger/Currency/Exchange rates. C: Define the company's standard currency under General/Company information. Now the company is ready 2. Specify what to consolidate Go to General Ledger/Ledger/Periodic/Consolidate/Consolidation On-line. Specify what accounts (interval), and period to consolidate. Specify that you want the current transactions to be consolidated. On the Companies tab page, specify what companies to consolidate, and how large a share of their transactions to be used in the consolidated company. The share is typically the percentage of the shares you own of that company. 3. Run the consolidation Run the consolidation by clicking the OK button. All transactions from the companies are transferred to the consolidated company, and the Chart of accounts is created from the companies Chart of accounts. 4. Use the financial statement to print reports the usual way.

Article posted under: Financial Series.

Discussion based on this article: Help

View: All Disc:#7219 Subj: (Multiple) Art: How do I make a consolidation

7219.1 Consolidating all sides of the transaction (cathyd, 21 Jun 2003 03:38:06 CET) 7219.2 Only with a modification (AWI, 24 Jun 2003 15:46:24 CET) 7219.3 We are trying another way (cathyd, 27 Jun 2003 00:41:19 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back The information in this article applies to: (None) Published: Jul 20 2000 (Read by 372 users)

How to get the AOS to auto-start on your laptop when it doesn't This article explains how you can get the AOS to auto-start correctly on your laptop for version 2.1 if you are experiencing problems.

Technical Information Auto-start of AOS Ref. No: TI0001-02

Introduction This article contains a hint on how to make sure the Axapta Object Server auto-starts correctly on a PC/Laptop during reboot.

Problem The AOS can be set to auto-start after the machine has been rebooted. However , as the AOS is depending on the SQL server to be started, you can sometimes experience that the AOS does not start. The problem is that the SQL server (which can also be set to auto-start after re-boot) does not start before the auto-start of the AOS is attempted, and thus the start of AOS fails as there are no SQL server available.

Solution The attached registry fix contains a few statements, that makes sure that the AOS is not started before the SQL server is running and thus solves the problem.

The registry fix is imported by running the attached file.

Download files: Axapta.reg [0K]

Article posted under: Axapta Object Server.

Discussion based on this article: Help

View: All Disc:#367 Subj: (Multiple) Art: How to get the AOS to auto-start on your laptop when it doesn't

367.1 AOS not starting (jfournier, 06 Dec 2000 03:57:45 CET) 367.2 Tried the old one? (jsh, 07 Dec 2000 20:47:55 CET) 367.3 The old one does not work. (jfournier, 07 Dec 2000 22:16:08 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back | Start a discussion based on this article The information in this article applies to: (None) Published: Jul 20 2000 (Read by 333 users)

Confusion on the use of tablebuffers in X++ There has been some confusion surrounding the use of databuffers in X++. Please refer to the examples below for a clarification on the subject

The examples are based on two buffers declared as: zipCode buffer1; zipCode buffer2; Assigning by reference: buffer1 = buffer2; Buffer1 becomes a reference to buffer 2. Referencing buffer1 will have the exact same effect as referencing buffer2. The following example will print an X on the screen.: buffer1 = buffer2; buffer2.city = "X"; print buffer1.city; pause; Reinitializing with data: buffer1 = buffer2.data(); Buffer1 is reinitialized to the initial state of the tablebuffer and all data are transferred from buffer2. The example below will insert a record in the zipCode table despite the fact that we start out by setting tmp on buffer1. Stateinformation as lockSelect, current company and a running select statement will be reset on the tablebuffer. buffer1.setTmp(); select * from buffer2 where buffer2.zipCode == '4100' buffer1 = buffer2.data(); buffer1.zipCode = "CopyOf" + buffer1.Zipcode; buffer1.insert();buffer1.data(buffer2.data()); Transferring data only: buffer1.data(buffer2.data()) All data are transferred from buffer2 to buffer1. The effect is exactly the same as setting all fields in buffer1 equal to all fields in buffer2. No state information changes on buffer1. To make the above example insert records into a temporary copy of the zipcode table we need to change the code buffer1 = buffer2.data() to buffer1.date(buffer2.data()).

Article posted under: Databases (Ax). © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back | Start a discussion based on this article The information in this article applies to: (None) Published: Aug 01 2000 (Read by 425 users)

Where to place Damgaard Axapta application files The Damgaard Axapta Application files needs to be placed on a disk set that provides sufficient speed and security. A separate file server is not needed in most standard installations. By the Damgaard Axapta application we mean the set of files under Damgaard Axapta, where you find the the directories "appl", "bin", "share", "log". What type of disk set should be used: Place the application on a mirrored set of disks, that is RAID 1. To get an explanation on RAID (Redundant Array of Independent Disks), see the very good introduction on http://www.acnc.com look for raid.edu. If one disk in the mirrored disk set breaks, the application can still be accessed, while the broken disk is replaced. Even though the application in itself do not require a lot of disk activity, it should not be placed together with other disk heavy activities. Together in this sense means either same disk set or same RAID controller channel. In bigger installation even using the same RAID controller can be a problem. Examples of heavy disk activities include most database files (except program), NT (Windows 2000) swap files. Looking at the two different database systems supported by Damgaard Axapta the following files should not be placed together with the application:
MS SQL: System and temporary databases. Log, and data for user databases.
Oracle: Any type of tablespace, including RBS, Index, data, temporary. Redolog.

What type of computer should the disk set be placed on: If an Damgaard Axapta Object Server (AOS) is present place the disk set on this machine. If more AOS'es are present place the application on one of them. Put a copy of the application on one of the other AOS'es. This copy should be refreshed, whenever modifications to the application are carried out. If the number of AOS'es become large (>5) a dedicated file server could be an option that should considered. If an AOS is not present and the number of users are low ( 0] - valid Recid's may be negative as well... Testing if a database buffer is empty can be done using the Recid column. But a little care should be taken. This article explains how. One way to determine if a select returned a record, is to test the RecId column. Some programmers including experienced XAL programmers - does this by testing if the column is greater than zero: if (myTable.Recid>0)

// then blah, blah,...

Still, for large amounts of data, Recid values may exceed the upper limit of a signed 32-bit long. For such high values, the Recid's in Axapta appear as negative number, thus making the above X++ construction error prone. Instead use if (myTable.Recid) // then blah, blah,... or if (myTable.Recid != 0) // then blah, blah,... One exception for this rule is, when the Recid column has been used for an aggregation such as count: select count(Recid) from myTable; if (myTable.Recid > 0) // then blah, blah,... since the number of records is obviously not negative.

Article posted under: Databases (Ax), Best Practices, How to ....

Discussion based on this article: Help

View: All Disc:#2159 Subj: (Multiple) Art: Do not test for [Recid > 0] - valid Recid's may be negative as well...

2159.1 (No header specified) (Michel, 31 Aug 2001 06:46:46 CET) 2159.2 Is this REALLY how is solved ????? (t_seberg, 09 Oct 2001 16:01:28 CET) 2159.3 Is this REALLY how is solved ????? (t_seberg, 09 Oct 2001 16:08:55 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back | Start a discussion based on this article The information in this article applies to: (None) Published: Sep 12 2001 (Read by 0 users)

Navision Axapta – behind the scenes! Navision Axapta – behind the scenes! Navision TechNet has now reached almost 4,400 registered users and congratulations are in order! We would like take this opportunity to thank you for contributing to the success of Technet, and also for your Read more... Type your article here. Remember to specify the article type, and to select one or more topics that this article should be shown under.

Download files: Navision Product Division.doc [210K]

Article posted under: General. © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back The information in this article applies to: Damgaard Axapta v2.5 Published: Sep 19 2001 (Read by 655 users)

Axapta 2.5 and SQL Server 2000 Benchmark In January 2001, Navision, Compaq, and Microsoft staff joined forces and met at the Compaq Benchmark Center in Nice, France. The purpose of this meeting was to find the upper limit of Axapta and SQL Server 2000 performance using some of the most powerful hardware available today. SQL Server 2000 Enterprise Edition provided a throughput of 143.377 Sales Order Lines per hour and ran 1.900 Axapta Standard Users, with an average response time of 0.775 seconds. This document describes how the SQL Server 2000 Benchmark was performed.

Download files: Nice2Have08.doc [476K]

Article posted under: Databases (Ax), MS SQL.

Discussion based on this article: Help

View: All Disc:#2408 Subj: (Multiple) Art: Axapta 2.5 and SQL Server 2000 Benchmark

2408.1 Great! What about ORACLE on UNIX?... (min2sia, 08 Oct 2001 12:50:21 CET) 2408.1 3600 ASU (ebb, 08 Oct 2001 23:22:56 CET) 2408.2 ebb, please repost (Tommy, 10 Oct 2001 03:19:17 CET) 2408.3 3600 ASU (ebb, 10 Oct 2001 10:13:05 CET) 2408.4 Are those two tests comparable? (min2sia, 10 Oct 2001 12:49:08 CET) 2408.5 No they are not (birgirra, 24 Oct 2001 02:17:04 CET) 2408.6 Not meant to either ! (jkj, 08 Nov 2001 20:27:09 CET) 2408.7 Thoughts on Ledgerbalance and concurrency (birgirra, 15 Nov 2001 01:09:41 CET) 2408.8 Sum & Balances (jkj, 29 Nov 2001 23:41:16 CET) 2408.9 Feil (Espen Kaasa, 07 May 2002 11:19:47 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back | Start a discussion based on this article The information in this article applies to: Damgaard Axapta v2.5 Published: Sep 21 2001 (Read by 685 users)

Deploying application changes in a multi-AOS environment Currently in Navision Axapta 2.5, the development of Axapta applications are only supported within an environment using one AOS, so that the AOS can coordinate any changes that are made to the application. Problems occur within a multiple AOS environment due to the fact that the increased number of AOS' means that some will not be aware of changes made by another AOS, and consequently, an AOS might cache copies of outdated application objects. This Technical Information paper, describes how it's possible to cope with application applying changes in such a multi-AOS environment with Axapta 2.5 Enterprise.

Download files: TI Deploying Application Changes in a multi-AOS environment.doc [96K]

Article posted under: Axapta Object Server. © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back | Start a discussion based on this article The information in this article applies to: (None) Published: Sep 24 2001 (Read by 396 users)

Generation of 0 recids Under certain circumstances recid's with a value of 0 could be returned by the kernel in an AOS environment. The error occurs when one client is importing data while another client is using the system for normal daily tasks as by example invoicing. When the error occurs Oracle would return an error similar to: "ORA-02290: CHECK-constraint AXDB.SYS_C001197101) violated", MS-SQL Server would return an error similar to: "[Microsoft] [ODBC SQL Server Driver][SQL Server]INSERT statement conflicted with COLUMN CHECK constraint CK__X30018X__RECID__14ED4033'. The conflict occurred in database 'AXDB', table 'address', co". A simple workaround can be implemented by inserting the line "isSimple=TRUE" into line 25 of the class/method sysDataImport/importData. While solving the problem it will however cause the import of data to be somewhat slower. The error is expected to be corrected in Axapta 2.5 SP3 eliminating the necesety of above mentioned workaround.

Article posted under: Databases (Ax). © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

Back The information in this article applies to: (None) Published: Sep 25 2001 (Read by 398 users)

Enhancing security in your AOS environment A number of additional security options are available in Navision Axapta 2.5 to ensure a robust environment. This article shows describes some of them. (this information is taken from the Technical Information paper ASP Guidelines available on the Navision Axapta 2.5 CD)

Restrict administrative access The Control Panel used to control the AOS installation is enabled to run from a remote machine. This means that it is possible to start, stop and configure AOS instances from another machine running the Control Panel. This is done using a tcp connection to the Axapta Server Manager on the aocp port (typical 2712 if not changed in etc/services). Any hosting environment should disallow external access using tcp to this port. Another level of protection can be reached by disallowing remote administration. This means that only the control panel running on the local machine can control the AOS instances running at that machine. To disable remote administration, modify the registry key for the Axapta Object Server in the following way. Locate the Axapta Object Server registry entry: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesAxapta Object Server To this entry add a DWORD entry named DisableRemoteAdmin with a non-zero value. A value of zero will enable remote administration; a non-zero value will disable remote administration.

Restrict AOS Advertising In a standard AOS setup, the Server Manager can be queried for running AOS instances. This is done to allow clients to look for instances within a given range of names. In a hosting environment, it may be preferred to disallow this to avoid speculative clients in probing for other instances without knowing the names. To disable the advertising, modify the system registry according to the instructions below. Locate the Axapta Object Server registry entry: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesAxapta Object Server To this entry add a DWORD entry named DisableAdvertising with a non-zero value. A value of zero will enable remote Server Advertising; a non-zero value will disable Server Advertising.

Article posted under: Axapta Object Server.

Discussion based on this article: Help

View: All Disc:#3910 Subj: (Multiple) Art: Enhancing security in your AOS environment

3910.1 How to get axapta server manager name (pradeep, 07 May 2002 16:05:34 CET) 3910.2 Please be a little more specific (jsh, 10 Jun 2002 12:30:02 CET)

NOTE: Please read the rules for discussions on TechNet in the help link above.

© Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 1

WARNING: Last transaction had the following error. - Cannot edit a record in table EISNews (EISNews). The record has never been selected. Please correct if possible and try again. Back | Start a discussion based on this article The information in this article applies to: Damgaard Axapta v2.5 Published: Sep 25 2001 (Read by 0 users)

Using DTDs in Axapta This article shows how to use a DTD in an XML document There have been a lot of questions about using DTDs in XML documents, and reading them from Axapta. Strictly speaking, this has nothing at all to do with Axapta, but is the province of the MS XML parser. The subject matter is described in numerous XML books. Please be advised, that DTDs are fine for compatibility, but that schemas are far more expressive and should be preferred to DTDs. We present a job loading a document with an internal (i.e. contained in the document) DTD. static void Job364(Args _args) { // Create an XML spec using an (internal) DTD. If you need an external // DTD, use an external DOCTYPE specification. str s = '\n' + '\n' + ' \n' + ' \n' + ' \n' + ' \n' + ']>\n' + '\n' + '\n' + ' [email protected]\n' + ' [email protected]\n' + ' [email protected]\n' + ' DTD Test\n' + ' It is quite possible to use DTDs in Axapta.\n' + '\n'; xmlDocument doc = new XMLDocument(); doc.async(FALSE); if (doc.loadXML(s)) { print "Got it"; } else { print doc.parseError().reason(); } pause; }

Article posted under: XML. © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 2

Back | Start a discussion based on this article The information in this article applies to: Damgaard Axapta v2.5 Published: Oct 10 2001 (Read by 0 users)

Some facts and behaivor of object caching technice in a 3-tier enviroment. The intencion of this article is not to give a exhaustive examination of the cacing teching in a 3-iter enviroment, but to give some teknisk indsigt in this matter. There stille exist questions and ? som denne artikel ikke giver svaret på. Anyway.....good cashing 14-11-2001. JOM. Some facts and behaivor of the Axapta Object Caching technice in a 3-tier enviroment. Fact. Only 3-tier clients read/write the AOC file. The 'mecanisem' for deciding wheather an object is loaded from the AOS or from the AOC file on the disk is decided through the follwing 'algoritme'. During startup of the 3-tier client the AOC file is loaded into memory at the client. At this time the AOC file has fulfilled its purpose and is used no more. First, a global flag is check. This flag is indicating wheather the application file, has been changed in relation to the AOC file on the disk. If nothing has been changed, then there is no reason to compare the object versions on the AOS against the version in the AOC cash, and therefor no checking is nessary. If the object exist in the AOC cash, go ahead and use it. (If no AOC file for the specified user exist, "Username-", then the kernel looks for the 'Master.Aoc' file, and use this file during startup. If no AOC file for the specific user exist during startup, then the kernel will write an AOC file when the user logs out of Axapta ) When a client request an application object, then a lookup in the AOC cash is carryed out. Next a request is sent to the AOS to figure out wheather the same object with the same versions number exist on the AOS. IF the version number is the same, then the object is loaded from the AOC cach. The object is then flaged 'USE' in the AOC cash memory for further request. IF the version number is different then the application version on the AOS, then the application on the AOS is loaded. The application object in the AOC cash memory is flaged 'DO NOT USE', for further request. Next time the same application object is requested in the same client session, the procedure above is repeated, but now the application object in the AOC cash memory is flaggede USE/DO NOT USE. When the client terminates, then the AOC cash memory is written to the AOC file on the disk, and the AOC file does now contain the different application objects, which the user have loaded during the session + the appliktins objects already contained in the AOC file + other stuff. At the moment Axapta uses around 2Mb for the applcations objects part. NOTE that the check for the objects version number is only udført /done the first time the obj. is requested. (Performance) The reason for this implementation is that Navision a/s development consider the applicationen rather static, meaning that in a live production enviroment you dont expect updates and changes to applications during work hour or all along the day. Development ought to take place in an development enviroment Another enviroment should be use for testing purpose. When the developed and testet application need to be updatede to the production envirmoment, this can be handled easy and executed in few seconds even when running AOS. (application directory switching technic via 0the Axconfig tool or by importing.) The above described is also the reason for that Navison a/s recommends or more presice say that when developing you have to do the development in either a 3-tier enviroment or a 2-tier enviroment. DO NOT MIX those enviroments! ANYWAY when this has been said, an article on technet.navision.com, ( ????? ), explains how you could 'flush' the client/server object cash and in this way reload new appl objects ;-) 2) max størrelse af AOC filen? Man kan sikkert i et The intencion of this article is not to give a exhaustive examination of the cacing teching in a 3-iter enviroment, but to give some teknisk indsigt in this matter. There stille exist questions and ? som denne artikel ikke giver svaret på. Anyway.....good cashing

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 2 von 2

When runnning in a 3-tier enviroment the descision around ......

Article posted under: . © Copyright 2001 Navision A/S. All Rights Reserved. Click here for terms of use.

(Back to normal viewing)

http://technet.navision.com/workspace.asp?MenuFunctionName=EISNewsArticle&M... 22.04.2005

Navision TechNet

Seite 1 von 2

Back The information in this article applies to: Damgaard Axapta v2.5 Published: Oct 03 2001 (Read by 635 users)

Problems with Axapta running Oracle installed on a non-Windows platform? Possible problems regarding startup of Axapta client running against Oracle installed on a non-Windows platform. On some non-Windows platforms Navision Axapta has experienced problems at startup time. (True64, some Linux versions) Scenario: 1) You have installed the Oracle database on a non-Windows platform and made it ready for use for the Axapta application, meaning that tablespaces and an 'Axapta' database user has been created. 2) You install Axapta, startup Axapta, and follow the steps described in the Axapta install wizard without problems. 3) The first time you startup the Axapta client, after successfully installed and initiated Axapta against the Oracle Database, the Axapta client crashes before you are presented for the login box in Axapta. 4) Now it is not possibly at all, to startup the Axapta client. Workaround: Please note that you only need this (workaround) if you experience the problems described above. The problem only exists on some non-Windows platforms. (True64, some Linux versions) The workaround for Axatpa25 SP1/SP2 are the following: REMARK: The char backslach has been replaced with the char '/' for technical reasons in this article. In Class/SqlDatabaseInit/upgradeSystemVariables void upgradeSystemVariables() { int sysVarId; res = stmt.executeQuery('SELECT VALUE FROM SQLSYSTEMVARIABLES WHERE PARM=/'SYSVARID/''; if (res.next()) { //sysVarId = res.getInt(1);

//Please remove or comment this line

sysVarId = str2Num(res.getString(1));//Please insert this line res = stmt.executeQuery('SELECT VALUE FROM SQLSYSTEMVARIABLES WHERE PARM=/'DBID/''; if(res.next()) { //dbid = res.getInt(1);

//Please remove or comment this line

dbId = str2Num(res.getString(1));

//Please insert this line

if(sysVarId