Tag Archives: error

DIXF – Error when viewing target mapping

An issue comes up today when a client could not open “View target mapping”. This is R2 CU7. The stack trace error is shown like below

“Field ‘Position’ in table ‘DMFTargetXMLToEntityMap’ has not been explicitly selected“

It works for some entities but fails for some entities




After looking at stack trace I was able to find an issue with the select statement in table DMFEntity.generateXML() method. Position field was used but it was not part of Group by of the select statement; therefore, an exception was raised for missing field.

AOT > Table > DMFEntity > generateXML

I added ‘Position’ field to the select statement
while select mapping
group by MethodName, Position
where mapping.Entity      == _entity.EntityName
&& mapping.MappingType == DMFMappingType::Function
exists join sourceXMLFields
where sourceXMLFields.Entity == _entity.EntityName
&& sourceXMLFields.DefinitionGroup == _defGroup
&& mapping.EntityField == sourceXMLFields.EntityField


I’m now able to view the mapping. I found same issue with R3 CU8 and I haven’t tested with R3 CU9 yet.


Leave a comment

Posted by on June 15, 2015 in Development


Tags: , , , , , ,

DIXF – {CR}{LF} vs {LF}

A client was doing an DIXF Import for a Purchase Order Line entity and kept getting this error.

“The field “VendGroup” is not present in source”



This happened when i tried to preview data or to promote data from csv to staging. What happened was the DIXF framework stores header of csv file to a container and validates these header fields against source that user already defined during mapping.

Container[25] = “VendGroup”
Entity Field.FeldName = “VendGroup”

These 2 should be equal; however, it failed


I was thinking there should be a special character that is coming from the csv file which regular text editor can’t see. i used Notepad++ to verify the header and there is {CR}{LF} right behind “VendGroup”


{CR} Carriage Return;  {LF} Line feed


I started looking at “Source data format” of the entity and realized it was using “{LF}” as row delimiter. That explained why the method confind could not match the string because of special character {CR}

Container[25] = “VendGroup{CR}”
Entity Field.FeldName = “VendGroup”


Changing row delimiter from {LF} to {CR}{LF} fixed my problem.

1 Comment

Posted by on September 9, 2014 in Development


Tags: , , , ,

An error occurred invoking the Report Definition Customization Extension (RDCE).

I ran across this SSRS report past few weeks and had a hard time to solve the issue. I could deploy and view all the report but one report. It kept giving me this error

  • An error occurred invoking the Report Definition Customization Extension (RDCE). (rsRdceInvalidCacheOptionError)
    • Fatal exception performing AXRDCE transformation step. The report cannot be rendered. Please contact your system administrator.

By goggling, all of searching lead me to this page or this page

I thought i found the answer, but it deviated me even further from the solution.

The following didn’t work:

– Adding report to the “Report Deployment Settings” – the same error was thrown when deploying the report

– SSRS restart

– Deleting AUC and regenerating WCF config.

– Stop/Start Reporting Services

– Delete the report and redeploy

– Create a new config file

– Clear user usage

– Monitor event viewer

– Monitor database

– Use SSRS diagnostic tool to gather information about enviroment

Basically, I tried everything i can to get this to work but no matter what I tried the issue still persisted

One thing to keep in mind report, query  has never been modified. I decided to take different approach by looking at the report itself from VS perspective. I started seeing lights at the end of the tunnel. Recompiling the report in VS, i collected additional information. When I looked at data source, I found out the report was using a query. Looking at the query and tracking all of its datasources, I found out one of the table was missing an index. I removed the bad index field from the index, and reran the report and it worked like a charm



Leave a comment

Posted by on April 30, 2014 in Development


Tags: , , , , ,

Make sure disk space is available before generating CIL.

I was trying to generate a full CIL and kept getting this error

The CIL generator found errors and could not save the new assembly.”

I took the follow steps in order to attempt to fix the issue

1> Restart AOS

2> Regenerate full CIL

I kept getting the same error again. and errors in few other classes. After I compiled the classes individually, the errors went away but when i generated CIL, it came back again. It was really frustrated. I decided something else must have caused this. This time i took different approach

1> Stop AOS

2> Delete all of the source in the C:\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\bin\XppIL directory

3> Start AOS

4> Perform a full compile and this time i got an additional message “There is not enough space on the disk”


After verifying the hard drive, indeed there isn’t enough space in C drive


Problem was solved after i freed up more space


Tags: , , ,

A CLR error occurred while invoking the scheduling engine

I came across this issue recently


The issue in this was caused by the AOS Server configuration option “Enable the hot-swapping of assemblies for each development session” being enabled on the server.

In our development environment, we enable the hot-swap feature of the Application Object Server (AOS) to use updated assembly DLL files without having to repeatedly stop and restart the AOS. Restarting the AOS terminates the connections from other developer clients, which can be an inconvenience.

This option should NOT be activated on production environments. Disabling the option resolved the issue



Tags: , , , , ,

AX2012 R2 – SSRS Report error: #Error text —

In AX 2012 R2, if you will see any errors like this one #Error in SSRS reports randomly,  that means you have to do one of the 2 following solutions:


Solution #1:

In AX 2012, the service account that is setup in the “BC Proxy account” have always to be used for the SSRS execution account, and SSRS services account.

As a workaround or troubleshooting step, you can add the BCP account to AX with Sys Admin rights, and the report should print properly. This however, is not a long term solution and is a workaround that you can utilize short term until you get the following hotfix installed that should correct the issue:



 Solution 2:

Apply this hotfix

KB Article Number (s) : 2844965  
Language: All (Global)  
Platform: i386  

Leave a comment

Posted by on November 10, 2013 in Development


Tags: , , ,

%d bloggers like this: