Kan meerdere records in Table list (SqlDictionary) niet toevoegen. Tabel: 118, 4.
De SQL-database heeft een fout gegenereerd:

It roughly translates to:

Cannot insert multiple records in Table list (SQLDictionary). Tabel 118, 4. The SQL-Database has issued an error:

Thanks to my colleague Kenny, we quickly figured out that the problem was that the disk was full on the SQL server where the data and log files were stored. SQL server also logged an error in the event viewer on the SQL server saying that the disk was full.

Lessons learned:

• Errors in AX don’t always point in the right direction
• Check the event viewer on your servers
• Be carefull with low disk space

Here’s a trick I learned from a colleague:
With the class UserConnection, you can make sure a transaction isn’t rolled back even if the transaction it is in is rolled back.

Consider the following example:

The record will not be inserted, because an error is thrown that causes an implicit ttsabort (so the tranaction is rolled back), right?

Well, you can counter this behavior by using the UserConnection class:

You will see that the CustTable record will be inserted in the example above.

This can be useful if you really want a record to be inserted, for example when doing logging (like in batch processes, or when debugging).
When you don’t use a UserConnection, your logging will be rolled back together with other transaction.

User ‘Admin’ is not authorized to delete a record in table ‘DEL_PBATRANSLATECONSISTOF). Request den[ied].
Cannot edit a record in Translation table (DEL_PBATranslateConsistOf). Access Denied: You do not have sufficient authorization to modify data in database.

This week was the n-th time someone has come to me with this problem, so it’s time to blog about it :-).

The error you receive is odd, because user in question has enough rights to edit any table (administrator).
This error occurs when you don’t have the Product Builder (PBA) license key enabled.

There are two possible solutions to this problem:

• Either activate the license key for Product Builder under Administration – Setup – System – License information (if you have the PBA license key), and after synchronizing the Data Dictionary, you should be able to delete the company account
• Or if you don’t have the PBA license key, go to the AOT – Data Dictionary – Tables – DEL_PBATranslateConsistOf, and clear the security key property.

Some time ago, I talked about executing direct sql statements, and now I want to share some sql statements that I used to manage linked server connections.

What follows are 4 sql statements that allow you to add en remove linked servers on a database at runtime.

Some assumptions:
- There is a str variable named “query” that will contain the query
- there is a parm method on the class that return the sql server (“server” or “server\instance”)
- there is a parm method that returns a username
- there is a parm method that returns a password

Check if linked server exist
First check if the linked server doesn’t exist yet, or you will get an error when you try to add one that already exists.

Add linked server
When the linked server doesn’t exist, add it.

Add linked server login
Optionally, you can add a login that will be used to connect to the linked server.

Remove linked server
Optionally, you can remove the linked server.

Today I want to talk about executing SQL statements in X++ on both the AX database and external databases. This is something probably every AX developer will have to do at some point.

You’ll want to do this for many reasons; to execute stored procedures, to improve performance, to get data from an external database, and so on.

I will provide samples for two classes:
- Connection (Execute SQL statement on current AX database)
- ODBCConnection (Execute SQL statement on external database)

I will not cover the ADO connection (CCADOConnection class), because it doesn’t work when you run it on server (or in batch), and I don’t like that. If you do, try to convince me ;-).

Executing direct SQL on the current AX database

When you execute a SQL statement, there are two options:
- either you did a select and you expect a result to be returned
- or you did insert/update/delete and you don’t expect a result.

The first sample is for a SQL statement that returns a result:

Note: this is a main method, put it in a class. Also note that it has to run on server.

Now if you do an update/delete/insert, you will want to do something like this:

You can find more info about the executeQuery() and executeUpdate() methods on msdn:
Statement Class

Executing direct SQL on an external database using ODBC

Again, we have to differentiate between queries that return a result and those that don’t.

The following code sample retrieves records from an external database and processes the result:

As you can see, the code is pretty similar. The main difference is that we are using ODBC classes, including the LoginProperty class.

In this example, I use a DSN (Data Source Name) that I configured on the AOS server. The DSN contains a reference to the server and database you want to connect to, and also what user credentials should be used to connect to the database. This is a lot safer than storing them in AX.
If you don’t know how to create a DSN, there are plenty of tutorials on the web.

To update/delete/update, the code is more or less the same:

If you feel that something is missing in these examples, just ask.

I have a dilemma, and would like your opinions.
The situation is that I want to add fields to an existing table (say InventTable)

What would you prefer:

So the question is, should I add new fields to the table (option one), or should I create a new table with the fields and link to it. (option 2)

Normally, option 1 is the standard way of adding extra fields to a table, but option 2 has a few advantages:

• You don’t need to modify the existing table
• You’ll have less trouble with these fields when you have to upgrade AX
• It will be easier to deploy your modifications in an AX environment that already contains modifications to the table

There are also a few disadvantages I can think of:

• You have to join 2 tables to get the data from the new fields
• You can’t add the new fields to fields groups on the main table (InventTable in this example)
• On forms, you will have to add a new data source, or add display fields

I would certainly go for option 1 when doing customizations for a customer, but would consider option 2 for product development. I’m in doubt. How about you?

I’ve seen people write huge SQL statements, and even jobs that create these SQL statements to remove these duplicates from a table, but there’s actually a easy way to do this in AX.

Say you have a table KLFTestDuplicates that contains duplicates, then simple run the following job to remove them.

Remember: this is useful when developing and testing, but it will remove data from you database, so use it with caution.

Administration – Setup – System – Checklists – Upgrade checklist.

It shows you:
- Database server
- Database name
- Application folder
- Layers in the application

Upgrade Checklist