In that case you have to perform following steps:

1. Change EDT properties
2. Clear row of table AifSchemaStore for service which is using that EDT (for example AxdSalesOrder)
3. Clear row (ex. SalesOrder) in table AidDocumentSchemaTable
4. Clean AIF Service folder (if you have it – Web Service)
5. Click Generate in AIF Services
6. Browse Endpoints Data Action policy enable/disable something of mentioned service
7. View Schema in Endpoint for service operation (ex. SalesSalesOrderService.create)

Karel F

/*
 * Code Sample Disclaimer:
 * Microsoft provides programming examples for illustration only, 
 * without warranty either expressed or implied, including, but not limited to, 
 * the implied warranties of merchantability or fitness for a particular purpose. 
 * This mail message assumes that you are familiar with the programming  
 * language that is being demonstrated and the tools that are used to create and debug procedures.
 */

DECLARE @_tableName nvarchar(40)
DECLARE @_companyId nvarchar(4)

SET @_companyId = N'<company_id>';  -- replace <company_id> with required company 

DECLARE curSqlDictionary CURSOR FOR
SELECT A.SQLNAME
FROM SQLDICTIONARY A
INNER JOIN SQLDICTIONARY X ON X.TABLEID = A.TABLEID AND X.FIELDID = 61448
WHERE A.FIELDID = 0
	AND A.FLAGS = 0

OPEN curSqlDictionary

FETCH NEXT FROM curSqlDictionary INTO @_tableName

WHILE @@FETCH_STATUS = 0
BEGIN
	DECLARE @_sql nvarchar(4000)
	SET @_sql = N'DELETE FROM ' + QUOTENAME(@_tableName) + N' WHERE DATAAREAID = @_dataAreaId'
	
	EXEC sp_executesql @_sql, N'@_dataAreaId nvarchar(4)', @_dataAreaId = @_companyId  
	
	FETCH NEXT FROM curSqlDictionary INTO @_tableName
END

CLOSE curSqlDictionary
DEALLOCATE curSqlDictionary

Martin F

In case it is something else, or you want to monitor other files, you can use the following procedure.

An typical error message which will pop up looks like this:

Error [Pathname]

Error Code 33 = The process cannot access the file because another process has locked a portion of the file.

After you confirm with “yes” to retry the access to the file, everything runs fine again.

To avoid this Situation, there is a well known tool which helps also in this situation, to find out what process causes the lock.

Please download the Process Monitor Tool from here:

https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

Configure the Process Monitor as follows and it will log every access to the application files, from a non AOS process.

You will need to configure two filters:

Please go to Filter -> Filter… add the following filters:

1. Path ends with .aod include

2. Process Name is AX32Serv.exe Exclude

Please check the following option:  Filter –> Drop Filtered Events.

Otherwise the log file can get really big, when process monitor runs for longer period of time.

Martin Ch.

The target table 'SYSDATABASELOG' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause.. The SQL statement was:

INSERT INTO SYSDATABASELOG (DATA,USERNAME,DESCRIPTION,LOGTYPE,TABLE_,LOGRECID,CREATEDBY,CREATEDTRANSACTIONID, DATAAREAID,RECVERSION,RECID) OUTPUT INSERTED.CREATEDDATETIME VALUES (?,?,?,?,?,?,?,?,?,?,?)

To solve this issue you need to drop the onSYSDATABASELOGinsert trigger by executing this statement in SQL Server Management Studio:

USE <ax_database_name>;
GO

DROP TRIGGER [onSYSDATABASELOGinsert];
GO

You may also need to modify the default constraint for CreatedDateTime field to replace the default value ‘1900-01-01 00:00:00.000’ coming from AX 4.0 with ‘dateadd(millisecond, -datepart(millisecond,getutcdate()),getutcdate())’. To do this you can execute following code:

ALTER TABLE dbo.SYSDATABASELOG
	DROP CONSTRAINT <constraint_name>
GO
ALTER TABLE dbo.SYSDATABASELOG ADD CONSTRAINT
	<constraint_name> DEFAULT dateadd(millisecond, -datepart(millisecond,getutcdate()),getutcdate()) FOR CREATEDDATETIME
GO

Martin F

Could not find ‘server name’ in sys.sysservers

This is because Demand Planner uses fully qualified object names in some stored procedures and functions, what results in original server name to be used.

Follow these steps to change the server name in existing functions and stored procedures:

1. Open SQL Server Management Studio and expand Databases

2. Right-click the Demand Planner database and select Tasks –> Generate Scripts

3. Click Next on the welcome screen

4. Select the Demand Planner database on Select Database screen and click Next.
Do not check the “Script all objects in the selected database” check box!

5. On the Choose Screen Options screen change value for Script Drop to True and click Next

6. On the Select Object Types screen select Stored procedures, Functions and Views and click Next

7. On the Choose Stored Procedures screen click Select All and then Next. Repeat this also to select all functions and views

8. On the Output Option screen keep the default selection and click Finish

9. On the summary page click Finish

10. In the query window press CTRL+H to open Find and replace window and type name of the original server into Find what field and name of the new server into Replace with field and click Replace All.

11. Press F5 to execute the script when all occurrences are replaced.

Now you should be able to synchronize Demand Planner.

Martin F

Cannot edit a record in Table1 (Table1).
An update conflict occurred due to another user process deleting the record or changing one or more fields in the record.

 1: static void updateTable1(Args _args)
 2: {
 3:    Table1 tbl;
 4:    ;
 5:
 6:    ttsbegin;
 7:    select firstonly forupdate tbl;
 8:
 9:    if (tbl.RecId)
10:    {
11:        tbl.InfoText = "Reset";
12:        tbl.update();
13:    }
14:    else
15:    {
16:        tbl.InfoText = "Reset";
17:        tbl.IntField = 1;
18:        tbl.insert();
19:    }
20:    ttscommit;
21:
22:    tbl.clear();
23:
24:    select firstonly RecId, InfoText from tbl;
25:
26:    ttsbegin;
27:    tbl.selectForUpdate(true);
28:    tbl.InfoText = "Table1 - field select";
29:    tbl.update();
30:    ttscommit;
31: }

The reason for this is that each time the table is updated the field RecVersion is updated with a random number that is saved by kernel. That why when you try to update the record, kernel cannot update record partly, what results in update conflict.

There are two ways to avoid this issue:

1. Add RecVersion field into the selection

24:    select firstonly RecId, InfoText, RecVersion from tbl;

2. Use selectforupdate keyword

24:    select firstonly forupdate RecId, InfoText from tbl;

Martin F

An exception occurred when calling Function in Library name DLL library

This happens only if the code calling the DLL function is running on server. The reason for this is that the DLLFunction class is not supported on x64.

Martin F

Unable to import
Trying to import Table MFATable_test1 with ID 50003
ID already held by Table MFATable1

To rename the object you need to follow these steps:

• Right click the object in AOT and select Rename (without checking out the object)
• Type a new name of the object. New object with the new name will be created
• Select Tools –> Development tools –> Version control in AX menu and click Pending objects
• Check in both objects

To update all objects that reference the renamed object, you need to check out all objects that refer to the object you want to rename. When you rename an object, two copies of the object are created: one with the old name and one with the new name. When you check in these objects (for delete and add, respectively), the system integrates both objects to maintain the history.

Martin F

System.Runtime.InteropServices.SEHException: External component has thrown an exception.
at AxCore_CallStatic(Char* , Char* , tagVARIANT* , Int32 , tagVARIANT* )
at Microsoft.Dynamics.BusinessConnectorNet.Axapta.CallStaticClassMethod(String className, String methodName, Object[] paramList)
at Microsoft.Dynamics.BusinessConnectorNet.Axapta.CallStaticClassMethod(String className, String methodName)
at BusinessLogic.DocumentationManager.GetXml() in D:\Development\AX\BC.NET Sample Test\BusinessLogic\DocumentationManager.cs:line 13
at ConsoleTest.Program.Main() in D:\Development\AX\BC.NET Sample Test\Console Test\Program.cs:line 15

To avoid this issue you need to install SP1 for AX 2009 (you need to have access to Partnersource).

Martin F

{
    str     document = "C:\\test.doc";
    COM     wordApplication;
    COM     wordDocuments;
    COM     wordDoc;
    ;

    // Create instance of Word application
    wordApplication = new COM("Word.Application");

    // Get documents property
    wordDocuments = wordApplication.Documents();

    // Open document
    wordDoc = wordDocuments.Open(document);

    // Activate the document - this is necessary to print it
    wordDoc.Activate();

    // Print the document
    wordDoc.PrintOut();

    // Close document
    wordDoc.Close();

    // Close Word application
    wordApplication.Quit();
}

Martin F